91. What is test strategy? List the four components of a good test strategy?
A test strategy is a statement of the overall approach to testing, identifying what levels of testing are to be applied and the method, techniques and tool to be used.
a) Critical success factor
b) Risk analysis
c) Assumptions
d) Methodology to be followed
92. Explain unit testing, integration testing, System testing, acceptance testing?
Unit testing:
Testing Individual Programs, modules, or components to demonstrate that the work package executes per specification, and validate the design and technical quality of the application. The focus is on ensuring that he detailed logic within the component is accurate and reliable according to pre-determined specifications. Testing stubs or drivers may be used to simulate behavior of interfacing models.
Integration testing:
This test begins after two or more programs or application components have been successfully unit tested. It is conducted by the development team to validate the technical quality or design of the application. It is the first level of testing which formally integrates a set of programs that communicate among themselves via messages or files (a client and its server(s), a string of batch programs, or a set of on-line modules within a dialog or conversation.)
System testing:
During this event, the entire system is tested to verify that all functional, information, structural and quality requirements have been met. A Predetermined combination of tests is designed that, when executed successfully, satisfy management that the system meets specifications. System testing verifies the functional quality of the system in addition to all external interfaces, manual procedures, restart and recovery, and human-computer interfaces. It also verifies that interfaces between the application and the open environment work correctly, that JCL functions correctly, and that the application functions appropriately with the Database Management System, Operations Environment, and any communications system.
Acceptance testing
Main objective acceptance testing is ensure all the functionalities and requirement are implemented correctly or not. In Acceptance testing real time test data is used, usually acceptance testing is done by client or client’s representative. Here client will check the all the functionalities.
93. Difference between Load testing and Stress testing?
Stress testing is subjecting a system to an unreasonable load while denying it the resources (e.g., RAM, disc, mips, interrupts, etc.) needed to process that load. The idea is to stress a system to the breaking point in order to find bugs that will make that break potentially harmful. The system is not expected to process the overload without adequate resources, but to behave (e.g., fail) in a decent manner (e.g., not corrupting or losing data). Bugs and failure modes discovered under stress testing may or may not be repaired depending on the application, the failure mode, consequences, etc. The load (incoming transaction stream) in stress testing is often deliberately distorted so as to force the system into resource depletion.
Load testing is subjecting a system to a statistically representative (usually) load. The two main reasons for using such loads are in support of software reliability testing and in performance testing. The term "load testing" by itself is too vague and imprecise to warrant use. For example, do you mean representative load," "overload," "high load," etc. In performance testing, load is varied from a minimum (zero) to the maximum level the system can sustain without running out of resources or having, transactions suffer (application-specific) excessive delay.
Performance testing is basically the process of understanding how the application and its operating environment respond at various user load levels. In general, we want to measure the latency, throughput, and utilization of resources.
94. What is software configuration management? List the configuration items?
Configuration management / control are a systematic way of controlling the changes to the software items.
Items
* All types of plans (project, test etc.)
* S/w code
* Test scripts & test cases documents
* Defect log
* Test reports
* User documentation
95. Contents of the Test plan (IEEE829)
1.INTRODUCTION & Version No
2. SCOPE
3. TEST STRATEGY/ Objective
4. ENVIRONMENT REQUIREMENTS
5. TEST SCHEDULE
6. CONTROL PROCEDURES
7. FUNCTIONS TO BE TESTED
8. RESOURCES AND RESPONSIBILITIES
9. DELIVERABLES
10. SUSPENSION / EXIT CRITERIA
11. RESUMPTION CRITERIA
12. DEPENDENCIES
13. RISKS
14. TEST TOOLS AND AUTOMATION
15. DOCUMENTATION
16. APPROVALS/FORMAL SIGN OFF
96. Characteristics of Good Test Cases are?
a) A good test case has a high probability of finding errors. b) It is traceable to the requirements. c) It has all the characteristics of a good requirement. i.e., it is clear, correct and unambiguous. d) It should be repeatable Either you can log it as a defect and assign it to the functional designer or send an email or convey him about the issue or you can set the status as enhancement necessary for the new functionality detected which is not mentioned in the functional specification.
98. High severity, low priority bug
Suppose I am accessing yahoo mail and system crashes at 99th unsuccessful login attempt. This can be a high severity, low priority bug. A page is rarely accessed, or some activity is performed rarely but that thing outputs some important data incorrectly, or corrupts the data, this will be a bug of High severity low priority.
99. What is Test bed?
An Environment containing the Hardware, Software tools, instrumentation, simulators and other support elements needed to conduct a test
100. What is test data?
Test data is the mock employee information used while testing.
