This is a 5-day collaborative project where QAs will work in groups of 4 to simulate a real-world software development environment. Teams will follow Scrum methodology, adopting its key ceremonies to reflect agile workflows.
-
Sprint Planning
Duration: 2 hours (Day 1)
Objective: Understand project requirements, analyze scope, and assign tasks. -
Daily Scrum
Duration: 10 minutes daily
Objective: Share progress, upcoming tasks, and blockers. -
Sprint Review
Duration: 1 hour (Day 5)
Objective: Present work, discuss challenges, and gather peer feedback.
| Day | Stage | Goals & Deliverables |
|---|---|---|
| Day 1 | Learn about Requirements → Analysis | - Document explaining how each API is triggered from the UI - Trello board setup with tasks - Postman workspace created and shared - List of questions or ambiguities |
| Day 2 | Design | Design positive and negative test cases for each API using Excel |
| Day 3 | Implementation (Create API requests and environment variables) | Create a Postman collection with organized folders and requests covering all test cases |
| Day 4 | Implementation (Create assertions for each request) | Add assertions for each request and run the collection to ensure zero failures |
| Day 5 | Presentation | 20-minute team presentation covering all deliverables |
- App: Contact List App
- API Documentation: Contact List Documentation
- Team 1: Focus on Contacts APIs
- Team 2: Focus on Users APIs
- Trello
- Postman
- Microsoft Excel
- GitHub
- Create a new Postman workspace and invite all team members.
- Set up a new Trello board:
- Create a card for each API
- Assign tasks clearly
- Ensure Postman Collection:
- Is well-structured and organized
- Includes requests for all relevant API endpoints
- Contains tests in the "Tests" tab (JavaScript assertions) (Scripts)
- Use environment variables throughout the collection (e.g., base URLs, tokens)
- Deploy the work on GitHub
-
Positive Test Case:
Example: Send a POST request with all required fields in the JSON body. -
Negative Test Case:
Example: Send a POST request with missing required fields and verify the proper error response. -
Explore the UI of the app to identify and cover more relevant test scenarios. [Verify Mapping between GUI and API]