Manual Testing class - 11

Smoke Testing : It is a Kind Of Quick Test Conducted On Diployed Build To Determine Does 
The Application Is Eligible To Continue Test Or Not.

   Smoke Testing Is Also Called Build Acceptance Testing (BAT) And Also Build Verification 
Testing (BVT)

Sanity Testing : A Quick Test Conducted At Production Environment To Determine Does The 
Application Is Testable By End User or Not For UAT.

Patch : After Smoke Testing If The Application is Failed Then Developer Will Modify The Application
 , That is Not A New Build , It is Called Patch.

Formal Testing : Testing Conducted On The Application By Fallowing Systematic Procedures Is
 Called Formal Testing.

Retesting : Testing a Functionality Redundantly Or Testing A Functionality Again And Again Is 

Called Retesting . Retesting Is Also Called Confirmation Testing .

 

Retesting Comes In Fallowing Scenarios :

1)      Testing A Functionality With Multiple Inputs.

2)      Testing A Functionality After Bug Fixing .

3)      Retesting Starts Right From The 1^st  Build

Regression Testing: Re-Running Or Re-Executing The Selective TC For The Dependent
 Functionality On Modified Build Is Called Regression Testing.

                             Regression Testing Is helpful To Determine the Side Effects Because
 Of The New Functionality Added In The Modified Build .

Note:

1)     Regression Testing Also a Part Of Re Testing

2)     Re Testing Starts From 1^st  Build

3)     Regression Testing Starts From Modified Build.

Informal Testing Or Adhock Testing : If You Test A Application With Out Fallowing Any Procedures
 ( As You Wish ) Then It Is Called Informal Testing.

Informal Testing is Helpful To Determine Tricky ( Zigzag ) Defects From Application And Also To 
Conduct Testing If Their Is No Time To Develop TC

------------------------------

 

Special Testing Tags In Functional System Testing :

1)      Exploratory Testing : Exploring The Application And Adding Or Modifying TC For Better Testing
 Is Called  Exploratory Testing.

Exploratory Testing Is Applicable If The Existing TC are Not Helping In Finding Good Defects.

2)      Error Guessing : With The Prior Knowledge And Experience The Testers May Guess The Error 
In Application Which Is Called Error Guessing .

3)      Mutation Testing : It is a Process Of Wantedly Injecting The Defects In Order To Confirming 
Does The Testers Are Properly Testing A Application Or Not.

4)      Monkey Testing ( Or ) Rattle Testing : Testing The Application With Zigzag Procedure Is Called
 Monkey Testing ( Or ) Rattle Testing.

5)       End To End Testing :

It Is A Process Of Verifying Overall Functionalities And Their Data Integration Right From The 
Beginning To The End.

------------------

Non Functional System Testing Types :

After completion of functional testing successfully, the testing team is concentrating on
 non-functional testing. During non-functional testing, the testing team is concentrating 
on customer expectations or software characteristics.

1)     UI Testing : Verifying The User interfaces Of The Application To Confirm Does The
 Application Looking Professionally Or Not Is Called UI Testing.

Check List For UI Testing   :

1)     Check For Availability Of Objects.

2)     Check Spelling Of Objects109

3)     Check Alignments Of Objects.

4)     Check For Consistence in BgColor , Fore Color,Font Type, size………

2)     Usability Testing : Verifying How Well The End User Is Able To Understand The System and 
Use It Is Called Usability Testing. In Other Words Verifying The User-Friendliness Is Called 
Usability Testing.

3)     Security Testing :Verifying Does All Security Conditions Are Properly Implemented Or Not 
Is Called Security Testing.

Check List For Security Testing   :

1)     Check For Access Control (Authorization ) :

Verifying Does The System Is Having A Provision Of Defining Users And Setting 
Permission Is Called Authorization Testing

2)     Check For Authentication :

Verifying Does The System Is Able To Identify The Registered Users And Weather 
It Is Displaying The Right Info To Right User Is Called Authentication Testing .

3)     Check Does Critical Info Such As Unm , Pwd And Credit Card Numbers Are Getting 
Encrypted Or Not.

4)     Check  Direct URL Access.

5)     Check For Session Expiry .

6)     Check The Browser Navigation ( Back Or Forward Navigation After Session Out ).

4)     Performance Testing : Verifying Or Analyzing Various Efficiency Characteristics as A System
 Such As Response Time , Load , Resource Consumption …..

5)     Compatibility Testing : Verifying Does The Application Is Compatible With Different HW And
 SW Environments Such As OS Compatibility , Browser Compatibility Is Called Compatibility 
Testing .

6)     Recovery Testing : Verifying Does The System Is having A Provision Of Back Up And Restore 
Options Or Not , And Also Verifying How Does The System Is Handling Unexpected Situations 
Such As Power failures & System failures .

7)     Installation Testing : Verifying Are We Able To Install The Application Successfully Or Not 
As Per The Guidelines Provided In Installation Document.

8)     Un Installation Testing : Verifying Are We Able To Un Install The Application Successfully 
Or Not is Called Un Installation Testing .

9)     Globalization Testing : Verifying Does The System Is Having A Provision Of Setting Multiple 
Regional  Settings Like Multiple Languages , Date And Time Format And Currency … If It Is 
Designed For Global Users Then It is Passed in Globalization Testing .

10)   Localization Testing : Verifying Does The System Is Having A Provision Of Setting Multiple
 Regional  Settings Like Multiple Languages , Date And Time Format And Currency … If It Is
 Designed For Particular Locality Of Users Then It is Passed in Localization Testing .

          

----------------------------------------------

Functional Testing: It’s a mandatory testing level, during this Test the testing team is validating
 a software build functionality in terms of below factors with respect to customer requirements.

   1. Behavioral / GUI:The changes in properties of Objects OR controls in a software is called 
behavioral or GUI.

   2. Input Domain: Whether the Objects are taking correct type and size of inputs or not?

   3. Error Handling: Whether our software is preventing wrong operations or not?

   4. Manipulations: Whether our software is generating correct output or not?

   5. Database Validity: Whether our software front end screens operations are correctly impacting on database of the software or not?

   6. Sanitation: Finding extra operations in a software with respect to customer requirements.

The above factors checking on a software is called as functional testing. During this checking
 the testers are using black box testing techniques or closed box testing techniques.