what are the levels of software testing

Hi frndz,

what are the levels of software testing?where are we implementing these testing levels in SDLC?

What levels r u talking about:confused:

From what I understand, levels could be,:D

1) smoke & sanity testing,
2) functionality & requirement testing,
3) regression & retesting,
4) integration & system testing,
5) user-interface & user acceptance testing.

I hope it answered ur question.:rolleyes:

[QUOTE=raajyeshaditthiya;12614]Hi frndz,

what are the levels of software testing?[/QUOTE]

Different level for software testing are:-

1)Unit level testing
2)Integration level testing
3)System testing
4)Acceptance testing :)

According to me there are four levels of testing. They are unit testing : to test the coding integration testing : to test the design system testing : to test the srs acceptance testing : to test the requirements phase.

Hi thr...
As per my knowledge
There are following levels of Software testing:
1. Unit Testing
2. Integration Testing
3. System testing
(performed on the entire system in the context of a Functional
Requirement Specification(s) (FRS) and/or a System Requirement
Specification (SRS).)
4. Alpha and Beta Testing.

[QUOTE=raajyeshaditthiya;12614]Hi frndz,

what are the levels of software testing?where are we implementing these testing levels in SDLC?[/QUOTE]

Hi,

As far i understood,there are 4 Testing levels and they are:
Unit testing,Integration testing,system teting and user acceptance testing(UAT).

Unit testing is done for individual units of the application
Integration testing is done to check the communication flow and data flow between the modules/units.
System testing is used to test the system as whole and its functionality
Acceptance testing is done at the time of delivery of the product by the customer.

Hi,

can any one tel me what are the entry level and exit level conditions for each level of testing?

Hi,

This can be defined in a Test plan for any.
as the levels of testing includes

[U]Unit Testing :[/U]

[U]Entry Criteria:[/U]

all the Unit level Test Cases are Reviewed and got approved
all the requirements and Tests for sanity/smoke are executed and passed
all the development code(described as per project plan) is developed and ready for testing
quality plan and Test plan are reviewed and approved

[U]Exit Criteria:[/U]

All the unit level test cases specified are executed and Passed

[U]Integration Testing:[/U]

[U]Entry Criteria:[/U]

All the unit level test cases specified are executed and Passed
All the Test specifications for Integration Testing are Reviewed and got approved.

[U]Exit Criteria:[/U]

All the Integration level test cases specified are executed and Passed
Validation Testing:

[U]Entry Criteria:[/U]

All the Integartion level test cases specified are executed and Passed
All the test specifications for Validation Tests are Reviewed and got approved

[U]Exit Criteria:[/U]

All the Validation level test cases specified are executed and Passed
--------------------------
Humpbackwhale

Certification preparation for hp quick test professional -hp0m16 course length : 3 days dates :- weekends course objectives this course teaches you to: the concepts of functional automation. Getting abreast with the qtp and learning how to implement it to do effective test automation. Understanding the advanced level features of qtp along with doing hands on with them. Prerequisites candidates should be well versed with the concepts of manual software testing intended audience quality assurance engineers, and new users of qtp who need to implement qtp and/or executives who will be involved in any part of testing. Course outline introduction to automation architecture of functional automation tools record and play modes of recording object repository(types) object repository manager(orm) and merging of or object identification actions parameterization checkpoints(standard, text, bitmap, database, xml from resource) output values(standard, text, text area, bitmap, database, xml from resource) synchronization points regular expression recovery scenarios function libraries define vb functions vb subroutines accessing data table at runtime using vbscript concept of descriptive programming. Single physical description object of physical descriptions. Framework - types of framework: 0,1,2,3. What you pay ? individual fees inclusive of all = rs 8000/- group discounts available = rs 7000/- per candidate in a group of more than 3 . Benefits :- • work shops conducted by istqb certified & hp-qtp 9.2 ( score - 98%) certified and an industry expert • study material and precise guidance • friendly but professional environment • sessions on only week ends (sat-sun) contact us :- sqc infotech k2 , first floor , central market above nokia hotspot ,lajpat nagar 2 . New delhi-24 ph :- 09910722113 / 011-46573287

Broadly software-testing levels are categorized into three levels. • unit testing • integration testing • system testing unit testing in this phase of testing, separate units of software system are tested. This is also known as component testing in which each module is tested alone to find any error in its source code. Programmer performs this testing as part of the development life cycle. The prerequisite for this phase is unit test plan, which should be written from low-level design document. Integration testing this testing is done to test the communication between different components of the software; all the modules that a program comprises are being bring together to test whether they are functioning in correct order with their counter part. Modules are typically integrated in a top-down, incremental fashion. For some projects integration testing can further be divided into two levels: – assembly integration testing. – system integration testing. During assembly testing, the integration of the software components is tested. During system integration testing, the communication with external systems is tested. Integration test plan should be written from high level design document. System testing this level of testing is done to test the functionality of software as a complete system. System testing is entirely different then integration testing. In integration testing interaction of component are tested while in system testing interaction of complete software with the system is tested.

The various levels of testing are:

Unit Testing (initial testing of a module) => Integration Testing(It test the various components and the communication between them in a controlled, isolated environment ) => System Testing (Verifies the proper functioning of the entire application including the interfaces between the applications) => User Acceptance Testing (It's the process of simulating the client environment to verify that the system meets the user requirements in order to determine the acceptability of the product by the user) => Operability Testing (Verifies that the application can operate in the production environment)

What is the difference b/w Assembly testing and Smoke testing?I know the definition:
Smoke testing: It verifies the major functionality at high level in order to determine if further testing is possible. And
Assembly Testing:In assembly testing, the integration of the software components is tested.

Actually this que was asked in an interview...so please can anyone differntiate it more?

What is the difference b/w Assembly testing and Smoke testing?I know the definition:
Smoke testing: It verifies the major functionality at high level in order to determine if further testing is possible. And
Assembly Testing:In assembly testing, the integration of the software components is tested.

Actually this que was asked in an interview...so please can anyone differntiate it more?[/QUOTE]

The Smoke test aims at the end-to-end testing of the whole application to test that the build does not breaks or fails on any page. This is done after every new build.

I think (not sure) Assembly Testing is Integration testing; it tests the interfaces between components, interactions, to different parts of the system are working properly and the communication between the components should happen in a controlled fashion.

Thank you sir....[QUOTE=Sohal;44191]The various levels of testing are:

Unit Testing (initial testing of a module) => Integration Testing(It test the various components and the communication between them in a controlled, isolated environment ) => System Testing (Verifies the proper functioning of the entire application including the interfaces between the applications) => User Acceptance Testing (It's the process of simulating the client environment to verify that the system meets the user requirements in order to determine the acceptability of the product by the user) => Operability Testing (Verifies that the application can operate in the production environment)[/QUOTE]

To enhance the quality of software testing, and to produce a more unified testing methodology applicable across several projects, the testing process could be abstracted to different levels. This classification into different levels introduces some parallelism in the testing process as multiple tests could be performed simultaneously. Although these levels are best suited for the waterfall model, (since the levels correspond directly to the different stages in the waterfall model) the level of abstraction still poses to be useful across other software development models. We shall be looking at:

1. Unit Level Testing
2. Integration Level Testing
3. System Level Testing
4. User Acceptance Level Testing

Brief Description of all Levels of testing :
[B]Unit Level Testing:[/B]
Unit Testing is primarily carried out by the developers themselves.
Deals functional correctness and the completeness of individual program units.
White box testing methods are employed
[B]Integration Level Testing.[/B]

Integration Testing:
Deals with testing when several program units are integrated.
Regression testing :
Change of behavior due to modification or addition is called ‘Regression’. Used to bring changes from worst to least.
Incremental Integration Testing :
Checks out for bugs which encounter when a module has been integrated to the existing.
Smoke Testing : It is the battery of test which checks the basic functionality of program. If fails then the program is not sent for further testing.
[B]System Level Testing:[/B]
System Testing -
Deals with testing the whole program system for its intended purpose.
Recovery testing :
System is forced to fail and is checked out how well the system recovers the failure.
Security Testing :
Checks the capability of system to defend itself from hostile attack on programs and data.
Load & Stress Testing :
The system is tested for max load and extreme stress points are figured out.
Performance Testing :
Used to determine the processing speed.
Installation Testing :
Installation & uninstallation is checked out in the target platform.
Acceptance Level Testing:
UAT ensures that the project satisfies the customer requirements.
Alpha Testing :
It is the test done by the client at the developer’s site.
Beta Testing :
This is the test done by the end-users at the client’s site.
Long Term Testing :
Checks out for faults occurrence in a long term usage of the product.
Compatibility Testing :
Determines how well the product is substantial to product transition.