cd0b795ac8
Extract customer creation/cleanup
...
This also ensures that cleanup always runs after all integration tests
MAILPOET-5145
2023-04-07 12:11:12 -05:00
c75bc388c9
Remove unnecessary cleanup code
...
MAILPOET-5145
2023-04-07 12:11:12 -05:00
e4029a607a
Adopt logging test to warning instead of error
...
[MAILPOET-4639]
2023-01-09 15:23:48 +01:00
2200411455
Add test case for logged error
...
[MAILPOET-4104]
2023-01-09 15:23:48 +01:00
b0ab2f404f
Add logging errors to the log table
...
[MAILPOET-4104]
2023-01-09 15:23:48 +01:00
82aeb89854
Use strict types in tests
...
[MAILPOET-2688]
2022-11-29 15:04:09 +01:00
6bf36d4211
Make sure the subscriber_segment table is truncated
...
This is necessary while
https://mailpoet.atlassian.net/browse/MAILPOET-4580 . Without this
change, leaving entries in wp_mailpoet_subscriber_segment has the
potential to interfere with other tests as it happened in the test added
for the ticket MAILPOET-4365:
https://app.circleci.com/pipelines/github/mailpoet/mailpoet/11041/workflows/8cca6607-2e24-4529-a8ad-cf9a0c663180/jobs/191334/tests#failed-test-0
See MAILPOET-4580 for more details.
[MAILPOET-4365]
2022-09-19 13:35:39 +02:00
fc1f3e6dc2
Inline generateToken for clarity
...
The only thing Security::generateToken was providing was a default value
for the $action, which created a pattern of using the same $action
everywhere, which may not be the best way to go.
Since it was essentially a wrapper for WP's built-in nonce functions,
it seemed clearer to use those functions directly to be more explicit
about how we're handling tokens.
[MAILPOET-2030]
2022-04-11 10:29:35 +02:00
9f790efbf0
Move plugin files to a subfolder
...
[MAILPOET-3988]
2022-01-18 15:30:22 +01:00
