Gurpreet N.

As a full stack developer, I have primarily focussed on performing a thorough unit testing at my end before publishing the test build for the QA team. Other than manual unit testing, I have also performed automation testing with the help of various tools such as Nunit, Selenium, Reactor, Jasmine, Mocha etc for different back end and front end development technologies, respectively. As a full stack automation developer, I have always ensure conducting following types of testing of my code - - Unit testing - System integration testing - Regression testing - Responsiveness testing - Load testing - Security breach testing - User acceptance testing My approach for testing and improving QA : a) Review of requirements - Gather all related documentation which is used throughout the whole project, and maintain an internal knowledge base b) Test Planning/Prepare Test Cases - Test processes should be well-planned, defined, and documented. Good documentation is the tool that builds efficient communication within the software team. So, effective planning entails creation of quality and test plans for a project. c) Try to spot possible regression as early as possible d) Report bugs effectively - The document must include not only the bugs scenarios but also provide solutions for them, i.e. describing the needed behaviour of a feature.This simplifies communication inside the team and helps keep a clear overview of the improvement process. Each issue gets a priority level from urgent to low, which the development team then resolves based on time and people available. e) Automate what can be automated - Automation can be fundamental for improving workflow and productivity. PS - I define main KPIs for QA depending upon the application's business domain for example, I develop manual unit test cases as well as I have worked with Automation QA tools that work around following KPIs - - Active Defects - Authored Tests - Automated Tests - Covered Requirements - Defects Fixed Per Day - Passed Requirements - Passed Tests - Rejected Defects - Reviewed Requirements - Severe Defects - Test Instances Executed - Tests Executed