:: Testing Tools Info ::

Beta Testing

2006-12-05T06:28:00.000-08:00

Its a type of user acceptance testing that is conducted in the client environment by the 3rd party test engineer / end user.

Disadvantages - If @ all any defects are identified in Beta testing there's no chance for rectifying them immediately.

Alpha Testing

2006-12-05T06:24:00.000-08:00

It is a type of testing ( User Acceptance Testing ) that is conducted in the company, by the test engineer just before the delievery.

Advantage Of Alpha Testing - If @ all any defects are identified in this testing there's a chance for rectifying then & there (immediate correction).

Re - Testing

2006-12-05T06:18:00.000-08:00

It is a type of testing in which the already tested functionalities are once again tested with different sets of values inorder to ensure that the defects are reproducable or / the functionality is functioning properly or not.

* Retesting is found in the 2nd stage.

Regression Testing

2006-12-03T21:41:00.000-08:00

It is a type of testing in which already tested functionality is once again tested.
This is usually done in 2 scenarios -->

(i) Whenever the defects are raised by the test engineer, rectified by the developer & released to the testing department as the next build, then the test eng will test the defect functionality as well as the related functionality which are already tested inorder to ensure that the functionality is working fine.

(ii) Whenever the new changes are proposed & incorporated in the module & released to the testing department, then the test eng will perform the testing on the already tested part inorder to ensure that this tested functionality remains unchanged.

* Therefore combination of both the scenarios is known as Regression Testing.
* Regression Testing is found in the 2nd stage.

Smoke Testing

2006-12-03T21:35:00.000-08:00

It is the initial test done / conducted by the test engineers soon after the build is released inorder to check the availability of all the objects & the usability of the application for further detailed testing.

In other words once the build is released to the testing department the initial testing conducted by the test eng inorder to check the usability to proceed to further detailed testing is known as "SANITY TESTING".

Types Of Testing

2006-12-03T21:27:00.000-08:00

01. Smoke Testing
02. Regression Testing
03. Re-Testing
04. Alpha Testing
05. Beta Testing
06. Static Testing
07. Dynamic Testing
08. Installation Testing
09. Compatibility Testing
10. Monkey Testing / Guerella Testing / Chimpanzee Testing
11. Usability Testing
12. Exploratory Testing / Artistic Testing
13. End To End Testing
14. Port Testing
15. Security Testing
16. Reliability Testing / Soak Testing
17. Mutation Testing
18. Ad-Hoc Testing

V - Model

2006-12-03T21:12:00.000-08:00

* V stands for verification & validation

* Also looks like 'V'

ABOUT V MODEL :

Defect Removal Efficiency (DRE)

A Defects found by the testing team (A)
-------
A + B Defects found by the customer (B)

PORT TESTING : After deployment the testing of application is known as "PORT".

Test Management Process is done by Test Director

Software efficiency -------> Testing -------> Quality Product

WEB SERVER : Providing web service to clients (its a software)
eg : Internet Information Services (IIS)

Fish Model

2006-12-03T21:06:00.000-08:00

* All the points covered in SDLC

* Each n' Every phase re-viewed & ensured

* Since verification & validation is involved in this process it i said to be expensive & best

* Time taken & Quality product

Spiral Model

2006-12-03T20:30:00.000-08:00

* Its is used for high risk based projects inorder to get High Quality filteration

* WA refers to Workaround

* Contraints are conditions

* Contingencies are solutions

* In Risk Root Analysis Time, Money & Solution are analysed

Spiral Model has 'n' no. of cycles

Evolutionary Model

2006-11-29T21:37:00.000-08:00

* Such kind of a model is made for fickle minded clients.

* Timelines & deadlines are not defined in this model.

* Clients requirement may vary from time to time & project to project. In this case the clients objectives / requirements are not clear & heance this kind of model can handle the most difficult clients needs.

Proto Type Diagram

2006-11-29T21:26:00.000-08:00

A Proto Type Diagram is a unclear & a rough sketch

Unclear Requirements SRS DOC Base Lined <-- Client Environment Confirmation

PROTOTYPE --> H/W Prototype --> Demo To The Client

--> S/W Prototype --> Demo To The Client

BRS Doc Base Lined <-- Requirements Are Defined

Software Development

2006-11-11T09:32:00.000-08:00

===========================================================
PHASE ACTIVITY OUTCOME
===========================================================

Initial ---------> Requirement Gathering --> BRS

Analysis --------> System Design ----------> SRS

Design ---------> S/W Design --------> TDD,GUI

Coding ---------> Implementation ---------> UTR, ITR

Testing --------> Black Box Testing --------> MTR , STR , UATR

Delivery & Maintainance ---------------> Delivery To Client

Environment

2006-11-10T20:46:00.000-08:00

It is a combination of 3 different layers. They are :
1. Presentation Layer
2. Business Layer / Core Layer
3. Database Layer

There are 4 types of environments :
1. Stand alone environment / One tier architechture
2. Client server environment / Two tier architechture
3. Web environment /Three tier architechture
4. Distributed environment /N-tier architechture also known as Multi tier architechture

If the presentation layer, business layer & the database layer present in a single tier then it is known as "One Tier Architechture / Stand alone environment"

Diagram :

Client Server Environment Contains 2 tiers. Clients will be residing in the 1st layer & the server will be residing in the 2nd tier. Presentation Layer & Business Layer will be present in the client tier & the database layer will be present in the servet tier.

Diagram :

Web Environment - In this architechture Presentation Layer resides in the client, Base Layer resides in the application server & the DBL resides in the database server.

Advantages - Business Logic can be easily updated.

Diagram :

Distributed Environment - It is the same web environment but if the Business layer if more or no. of users are more, 1 application server cannot bear the load. So the business layer is distributed among "N" no. of application servers.

Diagram :

Formula - "N" = No.of Application Servers + 2

Stub & Driver

2006-11-08T07:02:00.000-08:00

While integrating the modules in Top to Bottom approach if @ all any mandatory modules are missing, then that is replaced with a "Temporary Program" known as 'STUB'

While integrating the modules in the bottom up approach if @ all any mandatory modules are missing, then that is replaced with a "Temporary Program" known as 'DRIVER'

Levels Of Testing - Detailed Description

2006-11-01T08:37:00.000-08:00

If one performs testing on the smallest part of an application then that type of testing is known as "UNIT LEVEL TESTING". It is a white box testing and usually done by the developers. It's the first level of testing.

If one performs testing on a module then it is known as "MODULE LEVEL TESTING". It's a black box testing & usually done by the test engineers. It's the second level of testing.

When one of the modules are ready the developers will integrate the modules with the help of programs & test these programs whether they are (working) / functioning properly or not. It's a white box testing & done by the developers. They integrate the modules in 4 approaches -

1. Top to Bottom Approach
2. Bottom Up Approach
3. Sandwich Approach
4. Big Bang Approach

-> Big Bang Approach

Once all modules are ready @ a time all these modules are integrated. Then That approach is known as BIG BANG APPROACH

If one performs testing on an application once it is deployed into the environment, then it is known as 'SYSTEM LEVEL TESTING'. It's a black box testing done by test engineers.

If one performs the same system testing in the presence of user, then it is known as 'USER ACCEPTANCE TESTING' It's a black box testing, usually done by the test engineers.

Levels Of Testing

2006-10-31T04:22:00.000-08:00

There are 5 levels of testing -

Unit Level Testing
Module Level Testing
Integration Testing
System Testing / Application Testing
User Acceptance Testing (UAT)

Testing Methodology

2006-10-31T04:03:00.000-08:00

There are 3 methods of testing. They are :

BLACK BOX TESTING
WHITE BOX TESTING
GREY BOX TESTING

If one performs testing only on the Functional Part of an application without having the knowledge of the Structural Part then that method of testing is known as "BLACK BOX TESTING". It is done by Test Engineers.

If one performs testing on the Structural Part of the application, then that method of testing is known as "WHITE BOX TESTING". Usually developers perform this task.

If one performs testing on both the Functional Part as well as Structural Part of an application, then that method of testing is known as "GREY BOX TESTING".

(Note: Test eng with structural knowledge will perform grey box testing).

Unconventional & Conventional Testing

2006-10-31T03:50:00.000-08:00

Quality Assurance Managers test BRS. This comes under Unconventional test which is the Initial Phase of Testing.

Test Engineer is involved in Conventional Testing. This is in Testing Phase.

Q.Where exactly does testing come into picture?

If the interviewer asks such type of a question then the answer should be like this :

Ans. What sort of Testing are you expecting ? There are 2 sorts of testings -

1. Unconventional Testing &
2. Conventional Testing

Unconventional Testing is a sort of testing in which all the documents are tested right from the initial phase of the software development life cycle. It is done by the Quality Assurance people.

Conventional Testing is a sort of testing in which test engineers perform testing on the application in the Testing Phase of the s/w development life cycle.

Maintainance Process

2006-10-31T03:45:00.000-08:00

In maintainance process if at all any problem arises / occurs then that problem becomes a TASK. A corresponding role is assigned to accomplish that TASK based on the problem the ROLE will follow a process to solve the problem.

Delivery & Maintainance Phase

2006-10-31T03:35:00.000-08:00

Delivery -->

Input: Quality

Roles: Senior Test Eng / Deployment Eng / Installation Eng

Senior Test Eng / Deployment Eng / Installation Eng will install the application in the client's environment.

Output: Delivery of the product
Executing it in client's environment

Maintainance -->

Process, Task & Role can't be defined in maintainance phase.

Database executive / Corresponding executive plays role.

Process : Senior Test Eng / Deployment Eng / Installation Eng will install the software into the client's environment following the guidelines given in the "DEPLOYMENT DOCUMENT" by the Developer.

Test Case

2006-10-31T03:32:00.000-08:00

It is a checklist of all the different perceptions of a test engineer to test the specific functionality.

(Note: Perceptions in Test Case are based on Client's Requirements)

Testing Phase

2006-10-31T03:19:00.000-08:00

Now we have already seen a picture in the what is testing? topic . By this you might have understood partially. Here is the actuall procedure :

1. Business Requirements Review
2. If at all any doubts are raised in the BRS, a Review Report is prepared
3. Send the Review Repor to the author of the Requirements Document (i.e. Business Analyst ) for clarifications
4. After understanding the requirements clearly take the test case templates & prepare the test cases.
5. After the build is released execute the test cases.
6. If at all any defects are identified, isolate them
7. Report these isolated defects to the Development Department
8. Soon after the next build is released ensure that the product is defect free
9. "QUALITY PRODUCT"

Project & Product

2006-10-29T08:04:00.000-08:00

Companies are of 2 types -

Project Based Companies
Product Based Companies

PROJECT is something that is developed based on the customer specifications & used by that particular customer.

PRODUCT is something that is developed based on the company specifications & used by multiple clients.

CMMI, ISO, CODING STANDARDS

2006-10-29T07:46:00.000-08:00

CMMI : Capability Maturity Model

ISO : International Organizational Standards

CODING STANDARDS : Every organization will develop a set of coding standards to be followed by all development engineers. These standards specify how to name the variables, functions, methods, classes etc., how to name project files, what info has to be given at the top of each source code file such as copy right information, online documentation regarding functionality of the module etc.

Operational Characteristics In Detail

2006-10-29T07:36:00.000-08:00

Correctness
Usability / Learnability
Integrity
Efficiency
Reliability
Safety
Security
Maintainability
Testability
Flexibility
Scalability
Extensibility
Modularity
Portability
Reusability
Interoperability

Quality Triangle

2006-10-29T07:15:00.000-08:00

Test eng. needs to understand the quality requirements of the product to be tested using the "Quality Triangle". The testing has to be done to ensure that the software has the necessary quality attributes.

Software Quality Triangle is divided into -

Operational Characteristics
Transition Characteristics
Revision Characteristics

What is Quality ?

2006-10-29T07:02:00.000-08:00

Quality can be expressed in different ways. They are -

Customer Satisfaction is known as Quality
Where the application i said to be bug free or defect free.
Quality is defined in the customer's mind. It is the justification of all the requirements of a customer in a product.
It's also the absence of defects but also the presence of value ( value is nothing but product's userfriendlyness)
Requirement is the quality of the software

Where an application is achieving client requirements, client expectations, client specifications, with in the time & with in the cost. That exact meeting point is known as "Quality".

Defect, Density, Bug

2006-10-29T06:53:00.000-08:00

Defect - A software bug. A more formal word as compared to bug.
In general Deviation of a requirement is known as a "Defect".

Defect Density - No. of defects per 1000 lines of code.

Bug - A colloquial term used to indicate defect in software. Defect is a more formal & accurate word. We use the word bug & defect interchangeably.

Verification & Validation

2006-10-29T06:38:00.000-08:00

Definition of Verification : It is a process to ensure that the work products meet their (Client's) specifications. This is done throughout the Life Cycle of the project. After the product development is complete, testing is done to verify whether the product meets the customer requirements, product requirements, & product component requirements. Peer reviews play an important role in this process. If requirements are not met, corrective action is identified & implemented.

General meaning - It is to check whether the software conforms to the specifications.

Definition of Validation : It is a process to test whether the product meets the customer requirements in the intended environment. In validation, customer/ end users of the software are involved.

General meaning - To check whether the software meets the customer expectations.

What Is Testing ?

2006-10-29T04:19:00.000-08:00

“TESTING” is a check list of different perceptions of a test engineer in order to test the functionality. Verification & Validation of a software is also known as 'Software Testing'.

Testing is a process in which the defects are identified, isolated, subjected for rectification & ensure that the product is 'Defect Free' inorder to produce a Quality Product in the end & hence "Customer Satisfaction".

Purpose : To get quality software testing
Roles : Test Engineers

Testing is of 2 types :
-> Manual Testing
-> Automated Testing

TESTING INVOLVES 6 FACTORS :

1. Identifying
2. Isolating
3. Rectifying / (& Sending to developer)
4. Ensuring that the product is defect free
5. Delivery to Customer
6. Customer Satisfaction

How is testing done ?

Testing File -> It is a .exe
Developers -> Coding

Process of Preparation :

Testing Tools For Dummies & Experts !

2006-10-29T03:25:00.000-08:00

To Future Test Enggineers,

Welcome to the World Of Testing !!

Leave your comments on the blog. Your free to search / browse any info here.

Feel free to email us to share information regarding Testing Tools at testing.tools@yahoo.com & we will be glad to answer them.

Come, Learn & Experience.....

As a fresher you could be earning Rs.8,000 to Rs.16,000/- p.m.

For experienced pay packages are excellent 4lac,6lacs per annum.i.e. 30K to 50k p.m.