Review Requirements and create Test Plan contains critical user scenarios and test cases:
Create a detailed test plan that outlines the scope of testing, objectives, test cases, and testing schedule. Determine what types of testing are needed, such as functional, usability, compatibility, and performance testing.
Provide estimations and timelines to the team. (ETL)
Functional Testing:
- Test the website's functionality to ensure that all features and functions work as expected. It is done in multiple stages.
- Exploratory testing
- Smoke Testing Obvious testing of the happy flow of the application. Should be done quickly.
- Integration testings Testing to assure the integration between all the modules.
- Detailed functional/negative included/e2e testing.
- Regression testing To assure the existing parts of the website has no buggy affects due the current build.
Usability Testing:
Evaluate the website's user interface (UI) and overall user experience (UX) to ensure it's intuitive and user-friendly.
Compatibility Testing:
Verify that the website functions correctly across various browsers (e.g., Chrome, Firefox, Safari, Edge) and on different devices (desktop, tablet, mobile). Pay attention to rendering issues and responsiveness. We can use Virtual environment to increase our test coverage such as Browserstack
Performance Testing: (On Demand and as per budget)
- Assess the website's performance to ensure it loads quickly and responds efficiently. This includes:
- Load testing to check how the site handles heavy traffic
- Speed and responsiveness testing using tools like Google PageSpeed Insights.
- Testing for broken links and images.
Security Testing: (On Demand and as per budget)
- Evaluate the website & apps for security vulnerabilities, including:
- Testing for sql injection, cross-site scripting (XSS), and other common security threats.
- Verifying the use of HTTPS for secure data transmission.
- Ensuring proper user authentication and authorisation
Content Testing:
Review all website content, including text, images, videos, and downloadable files, for accuracy and relevance.
Sanity and Regression Testing Cycle:
After fixing any issues discovered during previous testing phases, perform regression testing to ensure that new changes haven't introduced new problems.
Cross-Functional Testing:
Collaborate with other team members (developers, designers, product managers) to address any issues and make necessary adjustments.
Reporting Bugs:
Document any defects or issues found during testing, including detailed information on how to reproduce them. Use a bug tracking system to prioritize and track the resolution of these issues.
User Acceptance Testing (UAT):
Involve stakeholders or end-users in testing to get their feedback and ensure that the website meets their expectations.
Final Review:
Conduct a final review of the website to ensure that all identified issues have been resolved and that it meets the project's requirements and goals.
Deployment and Post-launch Monitoring:
Once the website is ready for launch, monitor its performance and functionality in a production/UAT environment to catch any unexpected issues.
Documentation:
Create documentation that outlines the testing process, test cases, and results for future reference.
Test Management tools: Test Rail, Test Link, Postman, Devtools, Charley.
Automation FrameWorks: Selenium, Cucumber, Pytest, Selen, Selenoid, Allure TestOps, AzureDevOps.
