Software Testing is a process to quantify the quality of software and maintain the quality throughout the life of the software.
Software Testing is oriented to “Detection.” It’s examining system or an application under controlled condition. It’s intentionally making things go wrong when they should not and things happen when they should not.
Organizations vary considerably in how they assign responsibility for QA and testing.
Sometimes they combine the responsibility of one group or individual. It is also common that project teams include a mix of tester and developers who work closely together, with overall QA processes monitored by project managers. It will depend on what best fits an organization’s size and business structure.
Many time people ask what software testing is? What happens in software testing? So let’s see.
Software testing is a process to find out difference between Expected Results and Actual Results.
Expected Results: – It is the results which are expected after executing the software. According to the requirements what a customer has asked for in the software.
Actual Results: – When we execute software the behavior of the software or how it reacts, what it gives you at the end of an operation are called as actual results.
The Purpose of Software Testing?
The software is tested and put through various tests to see whether it performs as per expectations. It is done to find out various bugs in the software.
It has to undergo various software testing methodologies such as Unit Testing / Component Testing, Integration Testing, System Testing, Acceptance Testing.
What is a Test Case?
“A Test Case is documented that describe an input, action, or event and an expected response, to determine if a feature of an application is working correctly. A test case should contain particulars such as test case identifier, test case name, objective, test condition/setup, input data requirements, steps, and expected results.” – Technotrice
Reporting or tracking process show personnel at various stages. For instance, the tester needs to know when to enable notification of appropriate personnel at the different stage.
For example, the tester needs to know when resetting is required.
Developers need to know when the bugs are found and how to get the information and reporting/summary capabilities are needed for managers.
It is any variant between expected result and the actual result.
Or Software is not fulfilling the expectation then it is a defect.
Defects are always visible on GUI (Graphical User Interface) to the tester.
It is human mistake done in coding a simple silly mistake may cause a server defects. It is visible to the developer only. An error results in defects.
When the software as a whole does not fulfill customer requirement or customer unsatisfactory is called as a failure. It is visible to client or end user. Defects lead to failure.
It clients are one who pays you for software development. He may also be the end user.
End User: – He is one who uses the software. He may also be a client.
Types of Defects:-
Wrong: – Software is doing what it is not supposed to do. It is not doing what it is meant to do.
Both the points are specified in requirement.
Missing: – It is not specified to do, but it should do accordingly.
Extra: – It is not specified in the requirement and also doesn’t require but doing so.
You should also take a look at: