Final project for ITF Manual Testing Course

The scope of the final project for ITF Manual Testing Course is to use all gained knowledge throught the course and apply them in practice, using a live application.

Application under test: Autokarma.ro website

Tools used: JIRA, Zephyr Squad

Functional specifications

www.autokarma.ro is a website designed to provide information and services related to automotive repair and maintenance. The website aims to cater to both vehicle owners and automotive professionals by offering a user-friendly interface and a range of useful features.

Functional Requirements:

- User Registration and Authentication: Users can create accounts with a username and password. Users can log in and log out securely.

- User Profile Management: Users can update their profile information. Users can reset their password if they forget it.

- Search Functionality: Users can search for automotive products, services, and articles using keywords. Advanced search options, such as filters by category, brand, and price, are available.

- Product Listings: The website displays a list of automotive products with details, including price, availability, and product descriptions. Users can click on a product to view more information.

- Service Listings: The website displays a list of automotive services offered by registered service providers. Users can click on a service to view more information.

- Booking and Appointments: Users can book automotive services from service providers. Users can select their preferred date and time for the service. Users receive confirmation emails for their bookings.

- Blog and Articles: The website features a blog section with articles related to automotive tips, news, and guides. Users can comment on articles and share them on social media.

- User Reviews and Ratings: Users can leave reviews and ratings for products and services they have used. Reviews are displayed along with product or service listings.

- Shopping Cart and Checkout: Users can add products to their shopping cart. Users can proceed to checkout, enter shipping details, and make payments securely.

- Contact and Support: Users can contact the website administrators or support team through a contact form. Frequently Asked Questions (FAQs) are available.

- User Notifications: Users receive email notifications for account activities (e.g., registration, password reset) and booking confirmations. Users receive notifications for new articles and updates.

1 Testing section

1.1 Test Planning

The Test Plan is designed to describe all details of testing for the Users area from the Autokarma.ro website

The plan identifies the items to be tested, the features to be tested, the types of testing to be performed and the risks associated with the plan

1.1.1 Roles assigned to the project and persons allocated

• Adrian Sandu (QA engineer)

1.1.2 Entry criteria defined

• Initial project risks were detected and mitigated
• The requirement document should be available.
• Complete understanding of the application flow is required.

1.1.3 Exit criteria defined

All high-priority defects are fixed and retested

• Test coverage meets the predefined criteria
• All the test have been executed
• Acceptance criteria are met
• The product is stable and meets performance criteria

1.1.4 Test scope

• Tests in scope:

  • User registration
  • Login functionality
  • User profile management
  • Password reset
  • User dashboard
  • User account settings

• Tests not in scope:

  • Payment processing
  • Admin area
  • Performance testing
  • Stress testing
  • Regression testing

1.1.5 Risks detected

• Project risks:

  • Lack of experience of the QA engineer
  • Resource constraints: Short deadline of Zephyr Squad trial, unavailability of test environment.
  • Schedule delays: Bottlenecks or delays in testing phases.

• Product risks:

  • Compatibility issues with certain browsers: Internet Explorer, Opera browser
  • Layout issues: Website is not displayed properly with some browser resolutions

1.1.6 Evaluating entry criteria

The entry criteria defined in the Test Planning phase have been achieved, and the test process can continue.

1.2 Test Monitoring and Control

Test monitoring and control will be done by generating periodic reports that reflect the current status of the tests.

1.3 Test Analysis

The testing process will be executed based on the above requirements for the Dependents module. The following test conditions were found:

• Verify user registration process:

• Ensure that the registration form is accessible and loads correctly.
• Test all mandatory fields (e.g., name, email, password) for validation, ensuring they are required and correctly validated (e.g., email format, password strength).
• Verify that the registration form submission successfully creates a new user account.
• Verify if the system is sending registration link to the user.
• Verify if the link is working properly and the system register the user into the database.

• Validate login functionality:

• Confirm that the login page is accessible and loads without errors.
• Verify that registered users can log in successfully using their valid credentials.
• Test login with invalid credentials to ensure appropriate error messages are displayed.
• Check for security measures like account lockout after a certain number of failed login attempts.

• Test user profile section:

• Ensure that users can access and edit their profiles after logging in.
• Validate that changes made to the user's profile (e.g., name, email, profile picture) are saved correctly.
• Verify that profile updates are reflected and displayed accurately in the user dashboard and elsewhere in the application.

• Verify password reset functionality:

• Test the "Forgot Password" or "Reset Password" functionality.
• Verify that users receive password reset emails with valid reset links.
• Confirm that users can reset their passwords successfully by following the reset link.
• Ensure that the old password is invalidated upon resetting.

1.4 Test Design

Functional test cases were created in Zephyr Squad. Based on the analysis of the specifications, the test design techniques used for generating test cases are: Use case testing, boundry-value analysis, negative testing.

Test cases:

All the test cases exported into a xlsx can be downloaded from this testcases.xlsx

1.5 Test Implementation

• The following elements need to be ready before the test execution phase begins:

• Test environment setup
• Test data availability
• Test scripts and automation tools configured (JIRA, Zephyr Squad)

1.6 Test Execution

• Test cases are executed on the created test cycle. A summary of the test executions can be found in this example:

• Bugs have been created based on the failed tests. Bug titles:

  • Problems displaying header at different resolutions (Responsiveness bug)
  • The website no longer displays error details after generating verification code
  • The quantity field accept letters and special characters
  • Email validation rules don't work
  • Forgot password function is actually generate new password
  • Users can create accounts with less than 8 characters on password field

The complete bug reports generated from Jira can be downloaded here: Bugs.pdf

1.7 Test Completion

• Exit criteria was evaluated and passed

• The traceability matrix was generated and can be found here:

  

• Test execution chart was generated and can be found here:

• The final report shows that 14 tests were valid and 1 was failed.

1.7 Conclusion

I had the opportunity to explore the website of a company that had shone in the Romanian auto parts market for nearly three decades. With an impressive history and a solid reputation, this company represented a benchmark in the industry.

With my experience in software testing, I approached this website with a critical eye, ready to identify any issues that could affect its functionality or the user experience. Although the website seemed well-put-together at first glance, I knew that no software product is flawless, and the existence of potential problems was inevitable.

While I did not identify any major errors that would threatening the website's functionality or prevent users from ordering auto parts, I did uncover some minor issues and non-compliances.

All 13 test cases planned for execution were verified after testing. A total number of 6 bugs were found, and their priority is:

• High priority: 2 bugs found;
• Medium priority: 2 bugs found;
• Low priority: 2 bugs found.