slide1 n.
Download
Skip this Video
Loading SlideShow in 5 Seconds..
Marcio Corilov Test Analyst PowerPoint Presentation
Download Presentation
Marcio Corilov Test Analyst

Loading in 2 Seconds...

play fullscreen
1 / 28

Marcio Corilov Test Analyst - PowerPoint PPT Presentation


  • 117 Views
  • Uploaded on

Test Design. Marcio Corilov Test Analyst. Objectives. AGENDA. Lesson 1: Black-box testing design techniques. Black-box testing is testing based upon requirements. The internal logic structure is not considered;

loader
I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
capcha
Download Presentation

PowerPoint Slideshow about 'Marcio Corilov Test Analyst' - neola


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
slide1

Test Design

Marcio Corilov

Test Analyst

lesson 1 black box testing design techniques
Lesson 1: Black-box testing design techniques
  • Black-box testing is testing based upon requirements.
  • The internal logic structure is not considered;
  • You do not get inside the black box to examine internals, but rather you view it as input/output and the basic function.
slide6

Lesson 1: Test Case Design for FVT phase

  • Using basis-path testing to identify test cases for use cases;
  • Example, Bank customer withdraws money;
slide7

Lesson 1: Test Case Design for FVT phase

  • Using basis-path testing to identify test cases for use cases;
  • Example, Bank customer withdraws money;
slide8

Lesson 1: Test Case Design for FVT phase

  • Determine the basic flow;
  • Example, Bank customer withdraws money;
slide9

Lesson 1: Test Case Design for FVT phase

  • Determine the alternative flows;
  • Example, Bank customer withdraws money;
slide10

Lesson 1: Test Case Design for FVT phase

  • Determine the alternative flows;
  • Example, Bank customer withdraws money;
slide11

Test Case # Test Case Name

Withdraw amount lower than $500;

# 0001

Try to withdraw amount greater than maximum withdrawal allowed;

# 0002

Exceed the number of withdraws allowed in one day;

# 0003

Lesson 1: Test Case Design for FVT phase

  • Create the test cases for the use case;
  • Example, Bank customer withdraws money;
slide12

Lesson 1: Test Case Design for FVT phase

  • Example of a FVT test case:

Test Case #1 - Withdraw amount lower than $500;

slide13

Lesson 1: Test Case Design for FVT phase

  • Example of a FVT test case:

Test Case #2 - Try to withdraw amount greater than maximum withdrawal allowed;

slide14

Lesson 1: Test Case Design for FVT phase

  • Example of a FVT test case:

Test Case #3 - Exceed the number of withdraws allowed in one day;

slide16

Lesson 1: Test Case Design for SVT phase

  • Example of a SVT test case:

Test Case #4 - Exceed the number of withdraws allowed in one day;

slide18

Lesson 1: Test Case Design for BVT phase

  • Example of a BVT test case:

Test Case #5 – Check product standard installation (client server software);

slide20

Lesson 1: Test Case Design for Performance phase

  • Example of a Performance test case:

Test Case #6 - Withdraw amount lower than $500 (100 users simultaneously);

  • This type of test must be conducted using tools like Rational Performance Tester or Mercury Loadrunner;
slide22

Lesson 1: Guidelines for writing a Translation Verification Test Case

  • Translation tests verify the translation for context accuracy. These tests ensure that the function does not appear in English, that the translation is displayed correctly, and that the translation itself is correct;
  • Unlike regression testing, TVT testers test only the screens that have changed since the previous release;
  • Test only one screen in each test case, and put detailed step-by-step instructions on how to get to that screen;
  • Make each test stand-alone, meaning that you don't have to depend on the previous test to run this test;
  • Don't write a test case that verifies the function rather than the screens;
slide23

Lesson 1: Test Case Design for TVT phase

  • Example of a TVT test case:

Test Case #7 – Verify the screen of New Plug-in Project function of Eclypse;

slide25

Lesson 1: Test Case Design for Usability phase

  • Example of an Usability test case:

Test Case #8 – Verify the usability of New Plug-in Project function of Eclypse;

slide27

Lesson 1: Test Case Design for E2E phase

  • Example of a End-To-End test case:

Test Case #4 - Exceed the number of withdraws allowed in one day;