Process-oriented and focused on preventing software defects, software quality assurance (QA) reaches beyond mere bug detection.
QA professionals should thoroughly assess project, quality, change, knowledge, risk, and incident management processes. Investigate project documentation.
To make sure that the introduced changes facilitate the delivery of high-quality software and the revamped QA process stays up-to-date with the organization's business processes and needs in the long term, QA teams need to continuously assess the QA process, plan and implement the required improvements.
QA professionals should thoroughly assess project, quality, change, knowledge, risk, and incident management processes. Investigate project documentation.
To make sure that the introduced changes facilitate the delivery of high-quality software and the revamped QA process stays up-to-date with the organization's business processes and needs in the long term, QA teams need to continuously assess the QA process, plan and implement the required improvements.
QA process stages
Software quality assurance should start as early in the software development life cycle as at the requirements gathering stage and comprise the following activities:
Requirements analysis
QA professionals are involved in the analysis and clarification of functional and non-functional software requirements and make sure the requirements are clear, consistent, complete, traceable, and testable. Thus, they prevent possible software defects and facilitate upcoming test design activities.
Test planning
QA professionals use the knowledge gained at the requirements analysis stage as a basis for test planning. A test plan should contain a test strategy and cover a testing scope, a project budget and deadlines, the types and levels of testing an application requires, bug tracking and reporting procedures, resources and their responsibilities, and other factors.
Test design
At this stage, QA specialists design test cases covering software requirements. Test cases outline conditions, test data (prepared at the test design stage as well), and test steps needed to validate particular functionality, and state an expected test result. In order to gain familiarity with an application and come up with an optimal approach to test design, test engineers may start test design activities with a certain amount of exploratory testing.
When test automation is in scope, test automation engineers create test automation scenarios at the test design stage as well. Also, the test environment is prepared for test case execution. The test environment should closely mimic the production environment in terms of hardware, software and network configurations, operating system settings, available databases, and other characteristics.
Test execution and defect reporting
Test execution starts at the unit level, when the development team performs unit testing. In its turn, the test team takes over at the API and UI levels. Manual test engineers execute the designed test cases, submitting found defects in a defect tracking system, while test automation engineers use a selenium framework to execute automated test scripts and generate test reports.
Retesting and regression testing
Once the found defects are fixed, test engineers retest functionality in question and perform regression testing to make sure that bug fixes neither broke the related functionality nor made it different from that specified in the requirements. Automate a regression test suit.
Release testing
Once the development team issues a release notification (containing the list of implemented features, fixed defects, known issues and limitations), the test team identifies software functionality that has been affected by the introduced changes and determines test suites required to cover the scope of the deployed build. The test team performs smoke testing to make sure the build is stable and, once it is successfully passed, executes the identified test suites, issuing a test result report when finished.
Automation Testing.
In Mindlinks, the QA team with equipped with knowledge of Selenium test scripts preparation and execution which are used in place.
Mindlinks QA team has built its inhouse Automation portal, where test scripts are grouped and executed either manually or scheduled based on scheduler feature available in the portal. Reports can be extracted based on the test execution status.
A summary of no of test cases execution details is available in the portal. Logs file are also available for developers to look out why the test case has failed, the same can be emailed also.
Client : STAPP.
Load Testing
In Mindlinks, QA team are experts in conducting the load testing using the Jmeter tool and Blazemeter. We can do functional and no-functional both testing by using the Jmeter tool.
It supports various protocols like HTTP, FTP, SOAP, JDBC, JMS, and LDAP. We can also use the tool for testing the performance of your database. QA team can perform performance testing and scalability of the application can be measured.
Client : Align today.
Security Testing
ZAP : ZAP full scan GitHub action provides free dynamic application security testing of your web applications
Team is expert in running the ZAP tool on web application to find out any data breach/security vulnerabilities in the web application. Traffic can be used to modify requests in order to exploit an application. Depending upon the severity of the data breach /security vulnerability, the same can be communicated to developer team to take a proper action.
Zapp testing can be used for REST API testing using JSON format.
Client :Fineos