What is Software Testing? It is processes quantify the quality of software and maintain the quality throughout the life of software. Software Testing is a 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’re the combine responsibility of one group or individual. Also common are project teams that 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 organizations size and business structure.
Software testing is a process to find out difference between Expected Results and Actual Results.
Expected Results: – We get Expected results from the requirement or it is what the customer needs as his requirement.
Actual Results: – when we execute software the behavior of the software or how it reacts or what it is giving you at the end of an operation is called as actually results.
What’s a Test Case?
A Test Case is documents 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.
Note that: – The process of developing test cases can help find problems in the requirements’ or design of an application, since it requires completely thinking through the operation of the application. For this reason, it useful to prepare test cases early in the development cycle if possible.
What should be done after a bug is found?
The bug needs to be communicated and assigned to developers that can fix it. After the problem is resolved, fixes should be retested, and determinations made regarding requirements for regression testing to check that fix didn’t create problem elsewhere. If a problem tracking system is in place, it should encapsulate these processes. A verity of commercial problem – tracking / management software tools are available (see the tools sections for web recourse with listing of such tools.)
The following are items to consider in the tracking process.
1) Complete information such that developers can understand the bug, get an idea of its severity, and reproduce it if necessary.
2) Bug identifier
3) Current budge status
4) The application name or identifier and version
5) The function, module, feature, object, screen. Etc where the bug occurred.
6) Environment specifies , system , platform, relevant hardware specifies
7) Test case name/ number identifier
8) One line bug description
9) Full bug description
10) Description of steps needed to reproduce the bug if not covered by a test case or if the developers doesn’t have easy access to the test case
11) Name and / or description of file / data / message etc used in test
12) File experts / error message/ log file experts/screen shots/ test tools log that would be helpful in finding the causes of the problem
13) Severity estimate ( a5-level range such as 1 – 5 or critical – to – low is common)
14) Was the bug reproducible?
15) Tester name
16) Test date
17) Bug reporting date
18) Name of developer / group /organization the problem is assigned to
19) Description of problem cause
20) Description of fix
21) Code section / file / module / class method that was fixed
22) Date of fix
23) Application version that contains the fix
24) Tester responsible for retest
25) Reset date
26) Reset results
27) Regression testing requirement
28) Tester responsible for regression tests
29) Regression testing result
Reporting or tracking process show personal at various stages. For instance tester need to know when enable notification of appropriate personal at various stage. For instance tester need to know when resetting is needed developers need to know when bug are found and how to get the need information and reporting / summary capabilities are needed for managers.
Defects:-
It is any variants between expected result and actually result it is a defects.
Or Software is not fulfilling the expectation then it is a defects.
Defects are always visible on GUI (Graphical User Interface) to the tester.
Image may be NSFW.
Clik here to view.
Error:-
It is human mistake done in coding a simple silly mistake may cause a server defects. It is visible to developer only. Error results defects.
Failure :-
When the software as a whole do not fulfill customer requirement or customer unsatisfactory is called as failure. It is visible to client or end user. Defects lead to failure.
Clients:-
It clients is one who pays you for software development. He may also be the end user.
End User: – He is one who actually 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 supposed 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.
Source: http://www.technotrice.com/what-is-software-testing/