Sprint Duration: 1 week
- URL: DemoWebShop Project
The goal of this project is to create and manage an automation test project, incorporating the provided user stories. The project includes team collaboration, code management, and testing processes.
- Understand the provided user stories and create tasks for each story.
- Open the tasks in Jira and discuss them during sprint meetings.
- Prioritize the tasks in sprint meetings (Refinement / Sprint Planning) and assign story points.
- Create a sprint backlog based on the number of team members and the tasks to be completed.
- Write test scenarios using Jira Xray or Zephyr plugin.
- Each scenario should include:
- Scenario name
- Description
- Steps
- Expected results
- Refine the test scenarios during daily standup meetings.
- Set up a GitHub repository for the test code.
- The Team Lead will create the master branch and set up branch protection rules.
- Team members clone the master branch locally, create a new branch under their own name, and develop test code in their branch to avoid conflicts.
- We will use an already developed web environment for testing:
- Each team member initiates a pull request to merge their changes into the master branch.
- The Team Lead reviews the pull requests and may ask for corrections if necessary.
- Code review is performed on each pull request, and once approved, the changes are merged into the master branch by the Team Lead.
- Before any coding begins, each member should:
- Check the remote GitHub repository for the latest updates.
- Update their local master branch.
- Merge the updated master into their own branch to avoid conflicts.
Note: This step is critical to avoid an increase in conflicts.
- Conduct a sprint retrospective to assess what went well and what can be improved.
- Optionally, complex or incomplete user stories can be transferred to the next sprint.
- Share the GitHub repository link and Jira board screenshots in communication channels like Discord.
- Tag mentors and teachers when sharing updates.
- Team members can request help from the Team Lead or use communication channels for assistance.
- If needed, create "Knowledge Transfer" (KT) requests via Discord or other platforms and tag team members and mentors for help. Mentors will provide guidance and share knowledge.
Below are the user stories from DemoWebShop and their corresponding acceptance criteria:
-
US_201: Register User
- As a user, I should be able to register to the web store to shop and access features.
- Acceptance Criteria:
- Register button on the homepage.
- Registration fields for Name, Surname, Gender, Email, Password, and Confirmation.
- Successful registration and confirmation message.
- Password must be at least 6 characters long.
-
US_202: Negative | Register User
- As a user, I want to receive an error when trying to register with an existing email address.
- Acceptance Criteria:
- Error message "The Specified Email Already Exists" should be displayed.
-
US_203: Logout
- As a user, I should be able to logout to ensure a safer shopping experience.
- Acceptance Criteria:
- User should be redirected to the login page after successful logout.
-
US_204: Login
- As a user, I should be able to log in to manage my account and shop.
- Acceptance Criteria:
- Login button should be available on the homepage.
- Successful login with valid email and password.
-
US_205: Negative | Login
- As a user, I want to test various negative login scenarios.
- Acceptance Criteria:
- Error messages for empty fields, invalid emails, and passwords.
-
US_206: Ordering
- As a user, I should be able to order products using a credit card.
- Acceptance Criteria:
- Add product to cart, select shipping options, and proceed with payment.
- Verify the total price and complete the order.
-
US_207: Survey Response
- As a user, I should be able to answer surveys and see results after logging in.
- Acceptance Criteria:
- Survey should be visible on the homepage.
- User can submit an answer and view survey results.
-
US_208: Negative | Using Coupons and Gift Cards
- As a user, I want to see an error when I try to use an invalid coupon or gift card.
- Acceptance Criteria:
- Error messages should be displayed for non-existent coupons and gift cards.
-
US_209: Download the Order History
- As a user, I should be able to view and download my order history.
- Acceptance Criteria:
- Access order details and download invoices.
- The browser (Chrome, Safari, or Firefox) should be installed and initiated.
- Internet access must be provided in the test environment.
- The user account must be successfully created and verified for login and ordering functionalities.
- Credit card details for testing (Visa: 4242 4242 4242 4242, Expiry: 01/32, CVC: 123) should be used for payment.
- Negative scenarios are critical for ensuring stability and reliability by simulating unexpected use cases or errors. These scenarios help improve the overall user experience by preventing potential issues.
- Always consider and plan for negative scenarios when preparing test cases.
The basic technologies and tools to be used in this project include:
- Java - Programming language
- Selenium - Web browser automation
- Apache POI - Library for reading and writing Excel files
- Git & GitHub - Version control Systems
- JIRA & Zephyr-Squad - Test management Tools
- Abylmyrat - Project Team Lead & QA Automation Engineer
- Furkan Akalin - QA Automation Engineer
- Yasemin Yıldırır - QA Automation Engineer
- Gulmeiram Kongurbayeva - QA Automation Engineer
- Yeldar Zulyarov - QA Automation Engineer
- Burak Bilgiç - QA Automation Engineer
- Mahir Özçelik - QA Automation Engineer