Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Test Scenario: Batch Processing #101

Open
jkva opened this issue May 16, 2022 · 1 comment
Open

Test Scenario: Batch Processing #101

jkva opened this issue May 16, 2022 · 1 comment

Comments

@jkva
Copy link
Contributor

jkva commented May 16, 2022

When a plugin has a working configuration, batch processing becomes available. The plugin should:

  • process posts and pages;
    • in batches;
    • tracking progress using transients;
    • allow status updates and cancellation of a running job;
  • use an optional process batch size parameter;
  • process unpublished content based on a plugin setting; and
  • ideally not use a remote processor as tracked by Find Alternative for NodeJS Batch Processor #95.
@jkva jkva added this to the V2.0 milestone May 16, 2022
@Pen-a11y
Copy link
Contributor

Pen-a11y commented Jul 1, 2022

After running through each of the Test Scenarios for Batch Processing there are 2 of the scenarios that work fully and the rest will still need to be worked on for full functionality of the batch processor.
The following work correctly:

  • use an optional process batch size parameter
  • process unpublished content based on a plugin setting
  • process posts and pages;
    • in batches;

The following functionality doesn't work correctly:

  • process posts and pages;
    • tracking progress using transients: Currently, the tracking goes from 0% to 100%, and after testing with large numbers to import it does not seem to gradually increase the percentage while processing a batch.
    • allow status updates and cancellation of a running job: The cancellation of a running job works correctly, but the status update that is given is not very descriptive and when an error seems to occur the only message that is given is 'error'
      I think we should try to give a more descriptive error to the user, to tell the user what the issue could possibly be.
  • ideally not use a remote processor as tracked by Find Alternative for NodeJS Batch Processor #95.
    This issue has already been added earlier and will need to be addressed and talked about in there

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants