Test Strategy
Testing the presentation site for the Oportunități și Cariere Association involves the following steps to ensure the site functions correctly, offers an excellent user experience, and meets the association's objectives. The testing strategy includes:
1.1. Navigation
- Main menu testing: Verify that all menu links are functional and lead to the appropriate pages.
1.2. Interactive Features
- Search: Test the search function to ensure that the results are relevant.
- SPA Navigation: Verify that navigation elements lead to the selected section.
- Spelling and grammar: Review all content for spelling and grammar errors.
- Links: Check that all internal and external links are functional.
- Information update: Ensure that the presented information is up-to-date and relevant.
3.1. Design
- Visual consistency: Verify that the design is consistent across all pages.
- Correct display of elements: Ensure that all images and graphic elements load correctly.
3.2. Navigation
- Ease of use: Check if the site is easy to navigate and intuitive.
- Loading speed: Measure the loading time of pages and optimize where necessary.
- Testing on multiple devices: Verify performance on different devices (desktop, tablet, mobile).
- Browsers: Ensure the site works correctly on all major browsers (Chrome, Firefox, Safari, Edge).
- Devices: Test the homepage on different devices (Windows, Mac, iOS, Android).
- WCAG compliance: Check if the site meets the Web Content Accessibility Guidelines (WCAG).
- Screen reader use: Ensure the site is accessible to visually impaired users using screen readers.
The testing will focus on all critical functionalities of the presentation site to ensure an optimal user experience and meet the association's objectives. This includes testing navigation, interactive features, content, UX/UI, performance, compatibility and accessibility.
Testing will not include:
- Detailed testing of back-end functionalities that do not directly impact the end-user experience.
- Testing integration with external systems that are not essential for the presentation site's operation.
- Project requirements are finalized and approved.
- The testing environment is set up and accessible.
- Unit tests have been successfully completed by the development team.
- All planned tests have been executed.
- All critical and major defects have been resolved and re-tested.
- Regression tests have been conducted and passed successfully.
- The testing team and stakeholders have approved the testing results.
During Test Execution, the GitHub project named Test Cases will be used to capture all test results.
Should the test case fail, the status will be changed to “Failed”. Any divergence between expected and actual results will be regarded as an issue. The issue will be raised to the corresponding developer GitHub section and have its label set to “bug”, after describing it using the bug template.
| Status | Meaning |
|---|---|
| New | A bug has been identified. |
| Assign | A person is assigned to fix the bug. |
| Open | The bug is in the queue to be implemented or worked on. |
| Duplicate | The bug is investigated, and it's found to be the same as another bug. |
| Rejected | The bug is considered not important or not affecting the user’s experience. |
| Deferred | The bug is postponed and scheduled for fixing in a future release. |
| Fixed | The developer has fixed the bug. |
| Retesting | The fixed bug is being tested to ensure the issue is resolved. |
| Reopened | If the bug persists or reoccurs after being marked as fixed. |
| Closed | The bug is considered fixed, and the issue is closed. |
| Developers | Testers |
|---|---|
| Talida | Florin Nistor |
| Diana Dragoi | |
| Bogdan Dumitrache | |
| Georgiana Redenstein | |
| Melinte Camelia | |
| Bianca Jianu |
- Developer's local machine.
- Each developer should set up SOLR, API, and UI locally.
- site-ul Asociatiei Oportunitati si Cariere
- Validare de date
- GitHub Test Cases
- GitHub Issues
- A test strategy is an outline that describes the testing approach of the software development cycle. The purpose of a test strategy is to provide a rational deduction from organizational, high-level objectives to actual test activities to meet those objectives.
- A test plan is a document detailing the objectives, resources, and processes for a specific test session for a software or hardware product. The plan typically contains a detailed understanding of the eventual workflow.
- A test case contains the actions required to verify a specific feature or functionality in software testing. It details the description, preconditions, test steps in which are also known as the sequence of actions, expected outcomes, and post-conditions.
- A Test Report provides a comprehensive overview of the testing activities conducted during a specific phase of the software development lifecycle. It summarizes the test results, highlights key findings, and assesses the overall quality of the software.
- A Status Report offers a snapshot of the current state of a project, highlighting progress, challenges, and upcoming activities. It is a valuable communication tool for keeping stakeholders informed about project health.
- A Bug Report, also known as a Defect Report, details information about a discovered issue or bug in the software. It is essential for communication between testers and developers, providing clear and structured information about the defect.