You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Extend BasicOrchardFeaturesTestingUITestContextExtensions so it also tests Workflows and Audit Trail.
Do this similarly to how Media features are tested: a separate extension method just for Workflows, and one for Audit Trail (like TestMediaOperationsAsync()). Don't put all the code into the same class though.
No need to use page classes, just write the test also similar to TestMediaOperationsAsync().
For Workflows, test the following: Add workflow, add Event and Task, test that workflow runs. You can e.g. display a notification on login or a content item publish.
For Audit Trail, configure it to record events for a content type, test that content publishing for that type is correctly recorded.
github-actionsbot
changed the title
Basic Orchard features testing should include Workflows and Audit Trail
Basic Orchard features testing should include Workflows and Audit Trail (OSOE-847)
May 3, 2024
What do you think, should we also test the creation itself of the workflow, so clicking trough each step, creating the event and the task, or creating it from a recipe is enough? Then testing the workflow of course.
Because I think clicking it together could be problematic during the part where you have to connect the event with the task:
We need to test that the workflow editor also works, yes, that's why I mentioned adding an Event and a Task. Drag and drop is possible in Selenium, so that step should not be an issue either. See e.g. https://www.browserstack.com/guide/drag-and-drop-in-selenium for inspiration (this is Java, but the API is the same).
Extend
BasicOrchardFeaturesTestingUITestContextExtensions
so it also tests Workflows and Audit Trail.TestMediaOperationsAsync()
). Don't put all the code into the same class though.TestMediaOperationsAsync()
.Jira issue
The text was updated successfully, but these errors were encountered: