#ATAGTR2020 Presentation - Workflow Testing: 10 Scenarios to be Covered by Testers for Better Implementation
•
0 likes•40 views
Rahul Pethani delivered a Lightning Talk on Workflow Testing: 10 Scenarios to be Covered by Testers for Better Implementation ATAGTR2020 was the 5th Edition of Global Testing Retreat. Rahul is a lead Business Analyst and PreSales Consultant at ContCentric, India. Rahul is always keen to reach to the depth of the subject to discover better processes to deliver a solution with better quality. The video recording of the session is now uploaded on the following link: https://youtu.be/v3pc2Jrp7MI To know more about #ATAGTR2020, please visit: https://gtr.agiletestingalliance.org/
Recommended
Recommended
More Related Content
Similar to #ATAGTR2020 Presentation - Workflow Testing: 10 Scenarios to be Covered by Testers for Better Implementation
Similar to #ATAGTR2020 Presentation - Workflow Testing: 10 Scenarios to be Covered by Testers for Better Implementation (20)
More from Agile Testing Alliance
More from Agile Testing Alliance (20)
Recently uploaded
Recently uploaded (20)
#ATAGTR2020 Presentation - Workflow Testing: 10 Scenarios to be Covered by Testers for Better Implementation
- 1. #ATAGTR2020 As a author of this presentation I/we own the copyright and confirm the originality of the content. I/we allow Agile testing alliance to use the content for social media marketing, publishing it on ATA Blog or ATA social medial channels(Provided due credit is given to me/us) #ATAGTR2020 As a author of this presentation I/we own the copyright and confirm the originality of the content. I/we allow Agile testing alliance to use the content for social media marketing, publishing it on ATA Blog or ATA social medial channels(Provided due credit is given to me/us) Workflow Testing: 10 Scenarios to be Covered by Testers for Better Implementation Rahul Pethani
- 2. #ATAGTR2020 As a author of this presentation I/we own the copyright and confirm the originality of the content. I/we allow Agile testing alliance to use the content for social media marketing, publishing it on ATA Blog or ATA social medial channels(Provided due credit is given to me/us) #ATAGTR2020 As a author of this presentation I/we own the copyright and confirm the originality of the content. I/we allow Agile testing alliance to use the content for social media marketing, publishing it on ATA Blog or ATA social medial channels(Provided due credit is given to me/us) About me! Rahul Pethani Sr. Business Analyst at ContCentric ECM, BPM, CMS, ERP
- 3. #ATAGTR2020 As a author of this presentation I/we own the copyright and confirm the originality of the content. I/we allow Agile testing alliance to use the content for social media marketing, publishing it on ATA Blog or ATA social medial channels(Provided due credit is given to me/us) #ATAGTR2020 As a author of this presentation I/we own the copyright and confirm the originality of the content. I/we allow Agile testing alliance to use the content for social media marketing, publishing it on ATA Blog or ATA social medial channels(Provided due credit is given to me/us) Why this topic? Widely Applicable Technology Agnostic
- 4. #ATAGTR2020 As a author of this presentation I/we own the copyright and confirm the originality of the content. I/we allow Agile testing alliance to use the content for social media marketing, publishing it on ATA Blog or ATA social medial channels(Provided due credit is given to me/us) #ATAGTR2020 As a author of this presentation I/we own the copyright and confirm the originality of the content. I/we allow Agile testing alliance to use the content for social media marketing, publishing it on ATA Blog or ATA social medial channels(Provided due credit is given to me/us) Let’s see what’s on the plate..
- 5. #ATAGTR2020 As a author of this presentation I/we own the copyright and confirm the originality of the content. I/we allow Agile testing alliance to use the content for social media marketing, publishing it on ATA Blog or ATA social medial channels(Provided due credit is given to me/us) #ATAGTR2020 As a author of this presentation I/we own the copyright and confirm the originality of the content. I/we allow Agile testing alliance to use the content for social media marketing, publishing it on ATA Blog or ATA social medial channels(Provided due credit is given to me/us) 1. Review and Approval Stages
- 6. #ATAGTR2020 As a author of this presentation I/we own the copyright and confirm the originality of the content. I/we allow Agile testing alliance to use the content for social media marketing, publishing it on ATA Blog or ATA social medial channels(Provided due credit is given to me/us) #ATAGTR2020 As a author of this presentation I/we own the copyright and confirm the originality of the content. I/we allow Agile testing alliance to use the content for social media marketing, publishing it on ATA Blog or ATA social medial channels(Provided due credit is given to me/us) 2. Decision Junctions
- 7. #ATAGTR2020 As a author of this presentation I/we own the copyright and confirm the originality of the content. I/we allow Agile testing alliance to use the content for social media marketing, publishing it on ATA Blog or ATA social medial channels(Provided due credit is given to me/us) #ATAGTR2020 As a author of this presentation I/we own the copyright and confirm the originality of the content. I/we allow Agile testing alliance to use the content for social media marketing, publishing it on ATA Blog or ATA social medial channels(Provided due credit is given to me/us) 3. User Roles & Permission at each Stage
- 8. #ATAGTR2020 As a author of this presentation I/we own the copyright and confirm the originality of the content. I/we allow Agile testing alliance to use the content for social media marketing, publishing it on ATA Blog or ATA social medial channels(Provided due credit is given to me/us) #ATAGTR2020 As a author of this presentation I/we own the copyright and confirm the originality of the content. I/we allow Agile testing alliance to use the content for social media marketing, publishing it on ATA Blog or ATA social medial channels(Provided due credit is given to me/us) 4. User’s Availability in the System
- 9. #ATAGTR2020 As a author of this presentation I/we own the copyright and confirm the originality of the content. I/we allow Agile testing alliance to use the content for social media marketing, publishing it on ATA Blog or ATA social medial channels(Provided due credit is given to me/us) #ATAGTR2020 As a author of this presentation I/we own the copyright and confirm the originality of the content. I/we allow Agile testing alliance to use the content for social media marketing, publishing it on ATA Blog or ATA social medial channels(Provided due credit is given to me/us) 5. Integrations
- 10. #ATAGTR2020 As a author of this presentation I/we own the copyright and confirm the originality of the content. I/we allow Agile testing alliance to use the content for social media marketing, publishing it on ATA Blog or ATA social medial channels(Provided due credit is given to me/us) #ATAGTR2020 As a author of this presentation I/we own the copyright and confirm the originality of the content. I/we allow Agile testing alliance to use the content for social media marketing, publishing it on ATA Blog or ATA social medial channels(Provided due credit is given to me/us) 6. Form Validations
- 11. #ATAGTR2020 As a author of this presentation I/we own the copyright and confirm the originality of the content. I/we allow Agile testing alliance to use the content for social media marketing, publishing it on ATA Blog or ATA social medial channels(Provided due credit is given to me/us) #ATAGTR2020 As a author of this presentation I/we own the copyright and confirm the originality of the content. I/we allow Agile testing alliance to use the content for social media marketing, publishing it on ATA Blog or ATA social medial channels(Provided due credit is given to me/us) 7. Behaviour at Rejections
- 12. #ATAGTR2020 As a author of this presentation I/we own the copyright and confirm the originality of the content. I/we allow Agile testing alliance to use the content for social media marketing, publishing it on ATA Blog or ATA social medial channels(Provided due credit is given to me/us) #ATAGTR2020 As a author of this presentation I/we own the copyright and confirm the originality of the content. I/we allow Agile testing alliance to use the content for social media marketing, publishing it on ATA Blog or ATA social medial channels(Provided due credit is given to me/us) 8. Notifications & Reminders
- 13. #ATAGTR2020 As a author of this presentation I/we own the copyright and confirm the originality of the content. I/we allow Agile testing alliance to use the content for social media marketing, publishing it on ATA Blog or ATA social medial channels(Provided due credit is given to me/us) #ATAGTR2020 As a author of this presentation I/we own the copyright and confirm the originality of the content. I/we allow Agile testing alliance to use the content for social media marketing, publishing it on ATA Blog or ATA social medial channels(Provided due credit is given to me/us) 9. Configurations
- 14. #ATAGTR2020 As a author of this presentation I/we own the copyright and confirm the originality of the content. I/we allow Agile testing alliance to use the content for social media marketing, publishing it on ATA Blog or ATA social medial channels(Provided due credit is given to me/us) #ATAGTR2020 As a author of this presentation I/we own the copyright and confirm the originality of the content. I/we allow Agile testing alliance to use the content for social media marketing, publishing it on ATA Blog or ATA social medial channels(Provided due credit is given to me/us) 10. Status Reports
- 15. #ATAGTR2020 As a author of this presentation I/we own the copyright and confirm the originality of the content. I/we allow Agile testing alliance to use the content for social media marketing, publishing it on ATA Blog or ATA social medial channels(Provided due credit is given to me/us) #ATAGTR2020 As a author of this presentation I/we own the copyright and confirm the originality of the content. I/we allow Agile testing alliance to use the content for social media marketing, publishing it on ATA Blog or ATA social medial channels(Provided due credit is given to me/us) Thank you! Happy Testing!
Editor's Notes
- Number of stages of a workflow to be documented in test cases End-to-end testing for all the possible stages.
- Identifying the stages wherever decision junctions prevail Testing all the cases where decisions will define further course of the workflow
- The user roles involved may not have similar permissions at all the stages of the workflow At EACH stage of the workflow, listing down the permissions of each of the role and testing them.
- What if the initiator leaves the system when the workflow is till in-flight? What if there is new user added at a defined role before workflow gets completed? For all the use-roles available in the system, preparing the cases with adding or removing the users in the system.
- Is data being fetched upon some action in the workflow? Is data being provided to external system upon a decision? What are the non-functional requirements related to integration? How long it should take to affect the integrated system? Prepare the cases on the scenarios mentioned above Is data being fetched upon some action in the workflow? Is data being provided to external system upon a decision? What are the non-functional requirements related to integration? How long it should take to affect the integrated system? Prepare the cases on the scenarios mentioned above
- This is common but important. List down the form fields and their validations. Include in the test scenarios.
- Testing negative flow by rejecting workflow at different stages. Is workflow being terminated or being re-assigned? If it is re-assigned then to who? To the initiator, or the predecessor?
- Do notifications involve all the data-points in the scope? Are all the users getting the notifications? Are reminders configurable or customized? Do they work as expected?
- The workflow tools may come with OOTB configuration functionality. In context of the requirement, are those configurations working? Are they impacting any of the to-be processes?
- With the update of each stage, does status report get updated? Are the filters and export options working as expected?