SOFTWARE QUALITY ASSURANCE
Hi QA community, Nowadays Software Quality Assurance stage is most important of the software development. There are thousands of software developing companies are using thousands of testing tools and technologies (both automation and manual testing purpose). If we want to improve effective and efficiency of software quality assurance side, we must identify what are the characteristics and concepts of the QA. As well as we should be applying those things practically in our work time.
I want to introduce something new concepts regarding of QUALITY ASSURANCE. That words grab with the characteristics, concepts and best practices of the Software Quality Assurance.
Q -> Quantifiable
How many test cases that we are testing regarding the scenario. Identify related test cases of company domain. How many test steps that we apply inside the test case.
Ex: 500 test cases, 100 scenarios , 50 test steps one test case.
U -> Usability
Efficiency and effectiveness of the software project. How easy to use something by testing? When we are doing some testing activities, all the stakeholders(customers, developers, BA, PM etc) can understand that activities less effort.That is another concept of QA field.
A -> Accuracy
The estate of being correct. If the one test case expected result should be 10. But the actual result is 15. So, This test case is not pass then test case is failed no accuracy.
L -> Literacy
Simply call ability to read and write.Quality engineers must be ensuring the meaning full scripting when their QA activities.That is best practice of the quality engineers. If the stakeholders can make sure understand the script we can assume customer satisfaction very high.
Ex : Put the comments above the code.
I -> Integrity
Software quality engineers are very honesty. Because they must ensure the software is bugs free or not. Then they have automatically generating the responsible do their work in integrity.
T -> Trace-ability
Trace-ability is the capability to trace something. In some cases, it is interpreted as the ability to verify the history, location, or application of an item by means of documented recorded identification.
Ex : Software quality engineers also using trace-ability matrices to review test cases locations other historical details as well.
Y -> Yardstick of value
A standard used to compare similar things in order to measure their value or success. QA managers, QA Leads are measure progress of the QA project.
Ex: Code reviews of the project.
A -> Accessibility
If we are developing the software system, it can be used for any person. Like disability people also can use that system. Software quality engineers want cater to system for disabled people.QA team should be able to understand this matter and give solution and fulfil the accessibility of software.
S -> Security
Software testing fulfil the security of the software. QA team should be improved validations of the system.QA Engineers are doing security testing parts as some required. Uncover vulnerabilities of the system and determine that its data and resources are protected from possible intruders.
S -> Sustainability
QA leads, architectures and managers also ensure future improvement of the software. They ensure the software system will usable for the long time period.Hard concept of the QA field.
U -> Understandably
All the QA team must be understand regarding about domain of the client. If they are unable to understand the domain of client’s environment and requirement,they won’t be able to build the successful project. Another part is understand of the QA concepts most probably manual and automation.
R -> Reportable
This is very important concept. All the test cases are execution and client and QA team members want to get reports as well. Because they can understand summery of the test suites. Client can identify what is the situation of the test relevant test cases.
A -> Applicable
Apply the relevant test scenario for the relevant test cases. QA engineers want to make a good concentration of the business requirement and domain then apply those correctly.
N -> Naming
Test cases writing must be clearly define. This is another best practice for the quality assurance. We are the quality engineers we must fulfill right and quality of the software product.
C -> Communication
This is the most important and best practice. That can be apply not only QA role but also other software development phases also communication very important. Quality engineers are always continuing best communication with stakeholders. (software engineers, clients, project managers, business analyst etc.)
E -> Executable
Run the test scripts inside the test suit. QA engineers have implemented the test automation framework and executed scripted test cases. After executing relevant test cases analyse the test results.
Ex: TestNG is a best execution engine for selenium test cases.