Thursday, 17 October 2013

Bug Life Cycle

Picture




1. New
    When the bug is identified and logged in bug tracking tool for the first time, its state will be "NEW".

2. Open / Closed
    After a QA has posted a bug, the QA lead validates the bug. If bug is valid then he changes the state as "OPEN" and if the bug is invalid then the lead changes its state to "CLOSED".

3. Assign
    After QA lead changes the state as "OPEN", he assigns the bug to corresponding developer or developer team lead and the bug status is changed to "ASSIGN".

4. Rejected:
    If the developer feels that the bug is not valid or it has some technical limitations and cannot be fixed, he rejects the bug. He changes the state of bug to "REJECTED".

5. Duplicate:
    If the bug is logged is repeated twice or the two bugs reported has alike results and steps to reproduce, then one bug status is changed to "DUPLICATE".   

6. Deferred:
    If the development team lead decides to fix the bug in next release due to lack of time or the priority of the bug is low then he changes the state to "DEFERRED", which is later changes to "ASSIGN" when the bug is taken in consideration to be fixed.

7. InTest
    Once the developer fixes the bug, he assigns the bug to the testing team for next round of testing. Before that he changes the state of bug to "IN TEST". It specifies that the bug has been fixed and is released to testing team.

8. Verified
    Once the bug is fixed and the status is changed to "IN TEST", the tester tests the bug. If the bug is not reproducible in the software, he changes the status to "VERIFIED".

9. Reopened
    Once the bug is fixed and the status is changed to "IN TEST", the tester tests the bug. If the bug is reproducible in the software, he changes the status to "REOPENED".

10. Closed
    After the bug status is changes to "REJECTED" or "DUPLICATE" or "VERIFIED" the QA Lead verifies the comments added by the development or Testing team. When he is satisfied with the comments he changes the state to "CLOSED".

Note: There are different process and methodologies followed in various organizations. The above content is as per my experience in industry so far.

Sunday, 13 October 2013

Non Functional Testing


Non functional testing tests the characteristics of the software like how fast the response is, or what time does the software takes to perform any operation.


Following testing should consider in non functional testing types:

    * Availability Testing
    * Baseline testing
    * Compatibility testing
    * Compliance testing
    * Configuration Testing
    * Documentation testing
    * Endurance testing
    * Ergonomics Testing
    * Interoperability Testing
    * Installation Testing
    * Load testing
    * Localization testing and Internationalization testing
    * Maintainability Testing
    * Operational Readiness Testing
    * Performance testing
    * Recovery testing
    * Reliability Testing
    * Resilience testing
    * Security testing
    * Scalability testing
    * Stress testing
    * Usability testing
    * Volume testing


Security testing

The Security Testing , we test like:-


1. copy and paste link, it should not be open the respective page, it should allow to view first login page of the website.
2. max. allow of wrong password should be 3 times and many like that.......



Difference between Unit testing and functional testing


Unit testing:

Unit testing means It tested single peace of code or module which was changed by deverloper.

This test is conducted or white box test engineer.white-box test engineer should have internal skills

Functionality Testing:

Functionality testing Means it tested all the module and functionality is working or not according to the customer requirement . this is called Functionality testing 

Difference between Usability & User Interface testing


User Interface testing

1) verify the perticular module communicating properly among another as per the specification. Its mainly used for user interface of GUI application.
2) User Interface Testing comes under  "Functional Testing".

Usability Testing 

1) verifies is there any pain to use particular option for the user .
2) Usability Testing is part of System Testing.

Examples:

User Interface Testing:  Verifying the colors, graphics, allignments, sizes of Screens or forms

Usability Testing: Let us take one drop down which has 500 values in it. While using it it is very hard to select particular record out of 500 values in that drop down. So instead of using drop down field , as a tester we need to ask developer to use text box like in google site. If you enter first 3 or 4 letters autocatically it displays all the values which has these letters as first three letters.

Difference between Regression testing and Re-Testing

Regression Testing:


Regression testing means to re-execute the pass test cases again of older version of build on the modified version of build. to ensure that there is no any side effect of this change on another module or other part of the application.

Testing conducted to ensure application doesn't break post progression testing.

Re-Testing



Re-Testing: After a defect is detected and fixed, the software should be retested to confirm that the original defect has been successfully removed. This is called Confirmation Testing or Re-Testing

Regression testing:  Testing your software application when it undergoes a code change to ensure that the new code has not affected other parts of the software.


Re-Testing : The defect logged by tester while testing application and same fixed by developer. In Retesting we check same defect whether fixed or not using steps to reproduce mentioned in the defect.

Regression testing : we check same defect fixes are not impacted other unchanged part of the application, not breaking the functionality working previously and break due to fixing defect.

TEST EXECUTION


Level 0- Sanity, Smoke testing
Level 1- Real time testing
Level 2- Retesting and Regression testing
Level 3-Final testing
Objective of sanity and smoke testing is same as we can proceed for real time testing means all functional and non functional testing(system testing) based on priority. if bug is occured and reported then after modification we have to re execute the fail test cases(retesting, may be pass now) and pass test cases(Regression to ensure no side effect on another part).

Difference between Smoke Testing and sanity testing :


1) Smoke : this is done to verify to check if we are in a position to start Testing:

1. Able to  Access to the Applications

2. Login to the application

3. Click on links to verify that we are not getting any errors/page crashes.


Sanity:

This is performed to check if the application performing the required functions correctly

like adding A+B should be C,  all the major links are working perfectly as per the requirement.that means if your scientific calculator gives the result of 2 + 2 =5! Then, there is no point testing the advanced functionalities like sin 30 + cos 50.


2) Smoke testing and sanity testing is performed after software build and before any functional testing, Regression testing and any other testing executed on the software build.


3) Smoke test is testing whether the build is working fine or not

whereas the Sanity is testing whether major functionalities are working fine or not before test execution...


4) Smoke can be done by testers and developers and Sanity by Testers.


5) Example for Smoke testing:
Taking a test ride to test the basic features (functionalities) of the bike can be compared to Smoke testing a product

Example for Sanity testing:
Testing the bike performance in detail after bringing it home can be compared to Sanity testing a product

Saturday, 12 October 2013

Functional Testing Type

What is Functional Testing?

Functional Testing is the type of testing done against the business requirements of application. It is a black box type of testing.


It involves the complete integration system to evaluate the system’s compliance with its specified requirements. Based on the functional specification document this type of testing is to be carried out. In actual testing, testers need to verify a specific action or function of the code. For functional testing either manual testing or automation tools can be used but functionality testing would be easier using manual testing only. Prior to non Functional testing the Functional testing would be executed first.

Five steps need to be keeping in mind in the Functional testing:

   1. Preparation of test data based on the specifications of functions
   2. Business requirements are the inputs to functional testing
   3. Based on functional specifications find out of output of the functions
   4. The execution of test cases
   5. Observe the actual and expected outputs


In the types of functional testing following testing types should be cover:

    * Unit Testing
    * Smoke testing
    * Sanity testing
    * Integration Testing
    * Interface Testing
    * System Testing
    * Regression Testing
    * UAT