Basic Things About Software Testing

1) What is Error?
(i) The difference between the real value and the experimental value is called as Error.
(ii) Any programmatically mistakes in a software/product are called as Error.

2) What is Bug?
(i) The non-conference to requirement of a product is called as Bug.
(ii) Any Deviation from the expected result is called as Bug.
(iii) A persistent error in Hardware and Software is called as Bug.

3) What is Defect?
(i) The missing functionality of a product is called as Defect.
(ii) It occurs usually when a product is no longer works the way it used to.
(iii) Defect means, it is an error, flaw, mistake, failure, or fault in an application that prevents it from working as intended.
(iv) Faults in the production environment are called as Defects.

4) Write Different types of Defects?
These are the following types of Defects-:
(i) System Crash.
(ii) Application Crash.
(iii) Functional Major.
(iv) Functional.
(v) UI Defects.
(vi) Usability.
(vii) Functional Enhancement.
(viii) UI Enhancement.
(ix) Design Issue.
(x) Architecture.
(xi) Change Request.
(xii) Database.
(xiii) Documentation.

5) What is the Defect Source or why does software have Bugs?
Source of Defects:-
(i) Miscommunication.
(ii) Software Complexity.
(iii) Programming errors.
(iv) Changing requirements.
(v) Poorly Documented code.
(vi) Software Development tools.
(vii) Time Pressure.

(6) What is Testing?
(i) Testing is the process of executing a program with the intent of finding errors.
(ii) Testing is the process of uncovering errors in a program makes it a feasible task.
(iii) Testing is a destructive process of trying to find the errors in a program.
(iv) Testing is a set of activity that can be planned in advanced and conducted systematically.
(v) Testing is the infinite process of comparing the invisible to the ambiguous so as to avoid the unthinkable happening to the anonymous.
(vi) Testing is the Process which helps to identify the Correctness, Completeness and Quality of developing software.
(vii) Testing= Validation + Verification.
(viii) Testing is basically an activity designed for tracking Defects, Communicating the same to the concerned developers and then getting the fixed verified.

(7) What is Testing Life Cycle?
Testing Life Cycle means when new software is testing under it there are different stages are working. These are the following-:
(i) Requirements stage.
(ii) Test Plan.
(iii) Test Design.
(iv) Design Reviews.
(v) Code Reviews.
(vi) Test Case Preparation.
(vii) Test Execution.
(viii) Test Reports.
(ix) Bug Reporting.
(x) Reworking on Patches.
(xi) Release to Production.

(8) What is Bug Report and what is the purpose of it?
The Bug report is a document which explains the gap in the excepted result and the actual result and it also determine how to reproduce the scenario.

Purpose of Bug Report:- The main purpose of the Bug report is to enable the programmers to see the program failing in front of them.

(9) What is the Aim of a Bug Report?
The Bug report should be detailed enough to fail the program in front of the programmer itself. It should clearly distinguished between the excepted behavior and the actually behavior.

(10) What is Bug Tracking System?
(i) A bug tracking system is a software application that is designed to help quality assurance and programmers keep track of reported software bugs in their work. It may be regarded as a sort of issue tracking system
(ii) A bug tracking system for software defect tracking, and a general issue management application for helpdesk customer support and trouble ticketing.

(11) Write some important fields in a Bug Tracking System?
The important fields of a Bug Tracking Systems are in the following-:
(i) Bug Heading.
(ii) Status.
(iii) Description.
(iv) Type.
(v) Priority.
(vi) Severity.
(vii) System details like OS,Browsers etc.
(viii) Suggestion fix or expected behavior.
(ix) Attachments if any.

(12) What is Test Case?

(i) Test Case is a set of conditions under which a tester will determine if a requirement of an application is satisfied or not.

(ii) A test case is a noted/documented set of steps/activities that are carried out or executed on the software in order to confirm its functionality/behavior to certain set of inputs.