By vishal gupta
This presentation is the property of its rightful owner.
Sponsored Links
1 / 13

Testing, Testing & Testing PowerPoint PPT Presentation


  • 85 Views
  • Uploaded on
  • Presentation posted in: General

- By Vishal Gupta. Testing, Testing & Testing. QA doesn't make software but makes it better. Myths Vs Facts. Myths : Developers require more skills in comparative to QA. Development needs more effort then testing. Facts:

Download Presentation

Testing, Testing & Testing

An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -

Presentation Transcript


By vishal gupta

- By Vishal Gupta

Testing, Testing & Testing

QA doesn't make software but makes it better


Myths vs facts

Myths Vs Facts

Myths :

  • Developers require more skills in comparative to QA.

  • Development needs more effort then testing.

    Facts:

  • Tester needs to think one step ahead then developers to breaks their code.

  • Testing is more creative than development because you need to be creative to become destructive :)


Software testing

Software Testing

  • Software Testing is a process of evaluating a system by manual or automatic means and verify that it satisfies specified requirements or identify differences between expected and actual results – From ALU slide


How to do testing and it s life cycle

How to do Testing and it's life cycle

  • Unit Testing

  • Sanity Testing

  • Functional Testing

  • Integration Testing

  • Regression Testing

  • Stress Testing

  • Load Testing

  • Performance Testing

  • Solution Testing

How to do testing??


1 st cycle unit and sanity testing

Basic Cleaning of Bugs

1st Cycle - Unit and Sanity Testing

Unit Testing: It covers testing on a specific part of code perform by developers.

Sanity Testing: It's very basic level testing done by QA after fixing some bug.


2 nd cycle functional integration and regression testing

2nd Cycle - Functional , Integration and Regression Testing

Functional Testing: Focus majorly on specific functionality of component.

Integration Testing: To check, how that functionality work after integrating with some other functionality.

Regression Testing: To check older functionality after integrating new functionality. 

Complete Mix Testing


3 rd cycle stress load and performance testing

3rd Cycle - Stress, Load and Performance testing

  • Performance Testing: It means how best something performs under a given benchmark.

    Load Testing: It is also performance testing but under various loads.

    Stress Testing: It is performance under stress conditions.


4 th cycle solution or end to end testing

4th Cycle- Solution or End to End Testing

  • It's done in a completely emulated customer setup, involving multiple products and most of the time multiple vendor products.

  • If it's done at the customer site then it's also called as pre-production testing.


How to plan and organize test case

How to Plan and Organize Test case

Project

Test plan

Functionality

Test cases


Faq in testing

FAQ in Testing

What is the use of Automation in Testing?

It reduce time in testing cycle.

Automation find Regression issue quickly.

Will you allow bugs in the product to be released to the customer?

Depend on PM on market scenario.

What is the cost of poor quality?

It prevents from doing further business with the customer

It is expensive to fix bugs after releases as whole life cycle needs to be repeated

Difference Between Verification and Validation.


Verification vs validation

Verification Vs Validation

  • Verification:

    • Are we building the product right?

    • The software should conform to its specification.

  • Validation:

    • Are we building the right product?

    • The software should do what the user really requires


Common tools for testing

Common tools for Testing

Siebel: Bug tracking tool from Oracle.

Rational Robot: Load testing tool from IBM.

Mercury winrunner: Performance testing tool from Hp

SIPP: For Sip protocol testing.

Ethereal: For sniffing packets.

Test complete: For GUI automation.


Thank you

Thank You


  • Login