Friday, March 14, 2008

FAQ - Manual ( 81 to 90 )

81. What is the 'Software Life Cycle' ?


The life cycle begins when an application is first conceived and ends when it is no longer in use. It includes aspects such as initial concept, requirements analysis, functional design, internal design, documentation planning, test planning, coding, document preparation, integration, testing, maintenance, updates, retesting, and phase-out

Smoke testing: Smoke testing is done by developers before the build is released or by testers before accepting a build for further testing.

In software engineering, a smoke test generally consists of a collection of tests that can be applied to a newly created or repaired computer program. Sometimes the tests are performed by the automated system that builds the final software.

Acceptance testing: done a group of end-users or clients of the system to ensure the developed system meets their requirements do Acceptance testing.

Alpha testing: testing conducted by independent testing team at developer site

Beta testing: testing conducted by end user to more feedback faults or bugs to recover

System testing: testing conducted on a complete, integrated system to evaluate the system's compliance with its specified requirements. System testing falls within the scope of black box testing

Software testing: testing is process which help to identify correctness and completeness security and quality of developed computer software.

Unit testing: In computer programming, unit testing is a procedure used to validate that individual units of source code are working properly. A unit is the smallest testable part of an application.

82. What are the Suspension Criteria?

The testing process can go for suspension upon three criteria’s

1. Whenever a Critical Bug / Show Stopper with No Workaround

2. When the Hardware / Software Resources are not available at the time of testing

3. When the Manpower for testing is not allocated or available

 
83. What are the contents in Bugzilla?
 
       *          Bug Id (unique)
       *          Product name
       *          Component / Module
       *          Version
       *          Hardware
       *          OS
       *          Report Summary
       *          Environment
       *          Status
       *          Severity
       *          Reported by
       *          Assigned to
       *          QA contact
       *          Priority
       *          Keywords
       *          Description (which includes steps to reproduce,
Expected, Actual results & attachments if any)
 
 

84. What is verification & validation?

Verification is a static testing procedure. It involves verifying the requirements, detailed design documents, test plans, walkthroughs and inspections of various documents produced during the development and testing process. It is a preventive procedure.

Validation is dynamic testing procedure. Validation involves actual testing of the product as per the test plan (unit test, integration test, system test and acceptance test etc). It is a corrective procedure.

85. When do you think, it is appropriate to stop testing?

When the test manager is confident that the application will perform as expected in the production environment. This confidence is derived by analysis conducted on:

* Deadlines (release deadlines, testing deadlines, etc) are met

* Test cases completed with certain percentage passed

* Test budget depleted

* Coverage of code/functionality/requirements reaches a specified point

* Meantime between failures

* Risks associated with continuing to test

* Percentage of coverage achieved

* Number of open defects and their severity

* Risk associated with move to production

86. What are the benefits of Test Automation?

* Reliability

* Reusability

* Comprehensive

* Human investment is low

* Time consumption is low

* Accuracy is high


87. Difference between Static Testing and Dynamic Testing

Static testing could be termed as the Verification process where in the
work products or the plans or any documents made by or for testers are
tested (more so, verified).

Dynamic testing could be termed as the Validation process, where the actual testing of the application happens. All the testing phases (unit, integration and system) come under dynamic testing

88. What are the different types of S/W Process Models?

a) Waterfall Model.

b) V Model.

c) W Model.

d) Iterative / Spiral Model.

89. What are the different stages of STLC process?

* Test Analysis

* Preparing Test Plan

* Test case Design & Test case preparation

* Test Execution

* Test Log preparation

* Test Report

90. Difference between structural v/s functional testing?

* Structural analysis based test sets tend to uncover errors that occur during “coding” of the program. While functional analysis based test set tend to uncover error that occur in implementing requirement or design specification

* Functional testing ensures that the requirements are properly satisfied by the application system. The functions are those tasks that the system is design to accomplish.

* Functional testing is not concerned with how processing occurs, but rather with the results of processing

* Structural analysis used primarily during the coding phase.

No comments:

There was an error in this gadget