Details
-
Testing
-
Status: Closed
-
Minor
-
Resolution: Discarded
-
None
-
None
-
None
Description
Create test automation to validate the critical test scenarios/cases of the related story.
The focus of this task is to implement the CRITICAL, HIGH, and MID tests of the related story, but if you believe that can and have time to implement the LOW and TRIVIAL test cases, please, create one more subtask to it, and go ahead!
Test Scenarios
Test Scenarios | Test Strategy | Kind of test | Is it covered by FrontEnd ? (JS-Unit) | Is it covered by BackEnd ? (unit or integration) | Could it be covered by POSHI? | testcase | Case Name |
---|---|---|---|---|---|---|---|
"Ready for publish process" slider is not visible for public content pages | Critical | Manual | No | No | Yes | ContentPagesWithStagingPageVersioning | PublishContentPageWithPageVariationToLive |
"Ready for publish process" slider is not visible for private content pages | High | Manual | No | No | Yes | ContentPagesWithStagingPageVersioning | PublishContentPageWithPageVariationToLive |
"Ready for publish process" slider is not visible for collection pages | Critical | Manual | No | No | Yes | CollectionPagesWithStagingPageVersioning | ActivateStagingPageVersioning |
"Ready for publish process" slider is visible for widget pages | Medium | Manual | No | No | Yes | PGStagingWithVersioning | AddPageWithPageVersioningEnabled |
Attachments
Issue Links
- duplicates
-
LPS-139867 Poshi Automation for Bug LPS-139864 Staging fail to start when we have a published collection page with a fragment on it
-
- Closed
-
- relates
-
LPS-139574 Remove "Ready for publish process" slider for content pages when pages variations is enabled
-
- Closed
-
1.
|
Create the Poshi automation | LPS-140005 |
|
Closed | Yang Cao |