Testing covered under QA after understanding the business requirement

Performed Impact Analysis on the website just to make sure which areas will have effect on the Functional Changes/ UI Changes that were being changed. This was done using SRS before the changes were made.

Creating Test Case according to SRS.

Executing Test cases when the website is ready for QA.

Creating issues for Failed Test Cases.

Creating issues that are logged in the Database.

Monitoring processes to ensure they are effective.

Keeping adequate records.

Checking output for defects, with appropriate and corrective action where necessary.

Setting the Priority and Severity of issues and assigning to the Dev Team.

Once issues are resolved performed regression testing.

Once Issues are resolved sending back for UAT.

Once UAT is completed and it was Ready to Deployment.

Regularly reviewing individual processes and the quality system itself for effectiveness.

Post-Deployment testing is done as soon as the Code was released to Prod.

Worked within the teams from sprint 0 to find defects as early as possible.

Created testing strategies (formal or informal) and involve the entire team in the process.

Planed testing activities, carried out testing itself and interpreted testing results.

Allocate Time Appropriately for each process.

Automation Testing Implementation: Adopted to manage repetitive tasks, regression testing, and load testing, significantly boosting testing efficiency and reducing the likelihood of regression problems.

Tools for Automation Testing: Utilized tools such as Selenium for UI testing, JUnit for unit testing, and Apache JMeter for load testing.

CI/CD Pipeline Integration: Testing seamlessly integrated into Ragnar's CI/CD pipeline to ensure continuous quality assurance.

Automated Test Execution: Automated tests were executed with each code commit using tools like Jenkins and GitLab CI, ensuring rigorous testing of new features and updates before deployment.

Continuous Quality Assurance: Ensured that new features and updates underwent thorough testing, minimizing risks and improving overall software reliability.