Презентация на тему "State transition testing technique training"

Содержание

• 
  Слайд 1

  State Transition Testing Technique Training

  KaterynaDribas

• 
  Слайд 2

  Agenda

  1. Practice Third lesson: 1.1. Example; 1.2. Notifications; 1.3. Test cases. 3. Summary. 5. The end. 4. Home Task.

• 
  Слайд 3

  Practice

• 
  Слайд 4

  Example

  Customer selects a mark of the chocolate (e.g. ‘KitKat’). Chocolate vending machine (CVM) Enters money.

• 
  Слайд 5
  

  If amount of money is ok, then CVM will start selection of chocolate. If ‘KitKat’ chocolate is available, then customer will get ‘KitKat’ in a minute. If not enough money is entered, then CVM will ask to enter more. Not enough! Please select In a 10 seconds menu returns to main menu.

• 
  Слайд 6
  

  If there is no selected mark of the chocolate, then customer will get proper message. In a 10 seconds menu returns to main menu. The CVM doesn’t give the change. No chocolate! His money back.

• 
  Слайд 7

  Example

  Type of choco-late Valida-tion sum Check selected chocola-te Start Give choco-late Enter money Select type of chocolate Enough money, with or w/o change Chocolate exists In 10 seconds Customer selects ‘KitKat’, and enters money. If entered money is enough, the CVM will start selection of chocolate. If ‘KitKat’ is available, then customer will get it in a minute. In a 10 seconds menu returns to main menu.

• 
  Слайд 8
  

  Type of choco- late Valida-tion sum Check selected chocola-te Start Give choco- late Enter money Select type of chocolate Enough money, with or w/o change Chocolate exists In 10 seconds Wait for enough money Enter money Not enough money If entered money is not enough, the CVM will ask to enter more. If there is no ‘KitKat’ then customer will get proper message and his money back. In a 10 seconds menu returns to main menu. The CVM doesn’t give the change. Money back Chocolate doesn’t exist In 10 seconds

• 
  Слайд 9

  Example : Notification 1

  In examples we should discover how much times user has to enter money to get enough pay. Type of choco- late Valida-tion sum Check selected chocola-te Start Give choco- late Enter money Select type of chocolate Enough money, with or w/o change Chocolate exists In 10 seconds Wait for enough money Enter money Not enough money Money back Chocolate doesn’t exist In 10 seconds Valida-tion sum Wait for enough money Enter money Not enough money

• 
  Слайд 10

  Example : Notification 1

  Let’s take that ‘KitKat’ costs 10.00 UAH. Verify behavior of system, when entered sum is equal the chocolate cost. What is the minimum number of cases we should make for sum validation? 1st TEST CASE Enter 10 UAH

• 
  Слайд 11
  

  Enter 20 UAH. 2nd TEST CASE Verify behavior of system, when entered sum is more the chocolate cost.

• 
  Слайд 12
  

  Enter whole sum by 1 cop. 3rd TEST CASE Verify behavior of system, when entered sum by 1 cop is equal the chocolate cost. …

• 
  Слайд 13
  

  Every bank notes and coins. 4th TEST CASE Verify behavior of system, when every bank note and coin were entered until get the chocolate cost ,

• 
  Слайд 14

  Example: Notification 1

  There are many way to verify validation of entered sum. This issue should be clarified with BA. We should find the cases when it has sense.

• 
  Слайд 15

  Example : Notification 2

  In examples is not clear how many times user can repeat the ope- ration of selecting chocolate until he selects existing chocolate. Type of choco- late Valida-tion sum Check selected chocola-te Start Give choco- late Enter money Select type of chocolate Enough money, with or w/o change Chocolate exists In 10 seconds Wait for enough money Enter money Not enough money Money back Chocolate doesn’t exist In 10 seconds Previous steps Check selected chocola-te Start Money back Chocolate doesn’t exist In 10 seconds Previous steps

• 
  Слайд 16

  Example: Notification 2

  If the number of types chocolate is 10? Or 30? Or more??

• 
  Слайд 17

  Example 2: Notification 2

  There are many way to verify validation of entered sum. This issue should be clarified with BA. We should find the cases when it has sense.

• 
  Слайд 18

  Example: Causes

  Budget constraints Defect location identification Test coverage (higher or good enough for project) It depends on: Time constraints Business need Cost of mistake

• 
  Слайд 19
  

  - Test coverage (higher or good enough for project); - Cost of mistake. - Time constraints; - Budget constraints; - Defect location identification; - Business need;

• 
  Слайд 20

  Example: Test Cases. 1st flow

  In first test case would be the normal situation: the enough sum of mo-ney is entered the first time; selected mark of chocolate exists in CVM. Type of chocola-te Valida-tion sum Check selected chocola-te Wait for enough money Start Enter money Enter money Select type of chocolate Not enough money Money back Give chocola-te Enough money, with or w/o change Chocolate exists In 10 seconds In 10 seconds Chocolate doesn’t exist Enter money Select type of chocolate Enough money, with or w/o change Chocolate exists In 10 seconds Start Type of chocola-te Valida-tion sum Check selected chocola-te Give chocola-te

• 
  Слайд 21

  Example: Coverage. 1st flow

  Type of chocola-te Valida-tion sum Check selected chocola-te Wait for enough money Start Enter money Enter money Select type of chocolate Not enough money Money back Give chocola-te Enough money, with or w/o change Chocolate exists In 10 seconds Chocolate doesn’t exist Type of chocola-te Valida-tion sum Check selected chocola-te Start Enter money Select type of chocolate Give chocola-te Enough money, with or w/o change Chocolate exists In 10 seconds In 10 seconds

• 
  Слайд 22

  Example 2: Test Cases. 2nd flow

  In second test case not enough sum is entered the first time, but the sum is getting enough the second time. And ‘Kit Kat’ doesn’t exist in CVM. Type of chocola-te Valida-tion sum Check selected chocola-te Wait for enough money Start Enter money Enter money Select type of chocolate Not enough money Money back Give chocola-te Enough money, with or w/o change Chocolate exists In 10 seconds In 10 seconds Chocolate doesn’t exist Type of chocola-te Valida-tion sum Check selected chocola-te Wait for enough money Start Money back Select type of chocolate Enter money Not enough money Enter money Enough money, with or w/o change Chocolate doesn’t exist In 10 seconds

• 
  Слайд 23

  Example: Coverage. 1st, 2nd flows

  Type of chocola-te Valida-tion sum Check selected chocola-te Wait for enough money Start Enter money Enter money Select type of chocolate Not enough money Money back Give chocola-te Enough money, with or w/o change Chocolate exists In 10 seconds Chocolate doesn’t exist Type of chocola-te Valida-tion sum Check selected chocola-te Start Enter money Select type of chocolate Give chocola-te Enough money, with or w/o change Chocolate exists In 10 seconds In 10 seconds Wait for enough money Enter money Not enough money Moneyback Chocolate doesn’t exist In 10 seconds

• 
  Слайд 24

  Example: Notification 3

  But we may want to verify that all combi-nations of states and transitions still work correctly. We have covered all states and transitions. These flows are used to create main test cases.

• 
  Слайд 25
  

  Additional test cases may make you feel that you are on firm ground. There’s probability that they discover defects previous cases don't find. Let’s consider additional combinations of states.

• 
  Слайд 26

  Example: Test Cases. 3rd flow

  A third test case. The enough sum of money is entered the first time, and selected mark of chocolate doesn’t exist in CVM. Type of chocola-te Valida-tion sum Check selected chocola-te Wait for enough money Start Enter money Enter money Select type of chocolate Not enough money Money back Give chocola-te Enough money, with or w/o change Chocolate exists In 10 seconds In 10 seconds Chocolate doesn’t exist Enter money Select type of chocolate Enough money, with or w/o change Chocolate doesn’t exist In 10 seconds Start Type of chocola-te Valida-tion sum Check selected chocola-te Money back

• 
  Слайд 27

  Example: Coverage. 3rd flow

  Type of chocola-te Valida-tion sum Check selected chocola-te Wait for enough money Start Enter money Enter money Select type of chocolate Not enough money Money back Give chocola-te Enough money, with or w/o change Chocolate exists In 10 seconds Chocolate doesn’t exist Type of chocola-te Valida-tion sum Check selected chocola-te Start Enter money Select type of chocolate Enough money, with or w/o change In 10 seconds Moneyback Chocolate doesn’t exist In 10 seconds

• 
  Слайд 28

  Example: Test Cases. 4st flow

  A fourth test case. Sum of money is getting enough the second time. And selected mark of chocolate exists in CVM. Type of chocola-te Valida-tion sum Check selected chocola-te Wait for enough money Start Enter money Enter money Select type of chocolate Not enough money Money back Give chocola-te Enough money, with or w/o change Chocolate exists In 10 seconds In 10 seconds Chocolate doesn’t exist Type of chocola-te Valida-tion sum Check selected chocola-te Wait for enough money Start Give chocola-te Select type of chocolate Enter money Not enough money Enter money Enough money, with or w/o change Chocolate exists In 10 seconds

• 
  Слайд 29

  Example: Coverage. 3rd, 4st flows

  Type of chocola-te Valida-tion sum Check selected chocola-te Wait for enough money Start Enter money Enter money Select type of chocolate Not enough money Money back Give chocola-te Enough money, with or w/o change Chocolate exists In 10 seconds Chocolate doesn’t exist Type of chocola-te Valida-tion sum Check selected chocola-te Start Enter money Select type of chocolate Give chocola-te Enough money, with or w/o change Chocolate exists In 10 seconds In 10 seconds Wait for enough money Enter money Not enough money Moneyback Chocolate doesn’t exist In 10 seconds

• 
  Слайд 30

  Example: Notification 3

  We have considered additional combinations. We have covered all states and transitions. &

• 
  Слайд 31
  

  Summary Capture requirements So State Transition testing technique is a tool to: and describe the design of the application. And document them.

• 
  Слайд 32
  

  Summary Describe how the states of the appli- -cation may vary. State3 State4 State2 State1 Action1 Start5 Action4 Action5 Action2 Action3 Determine all the events that occur during the application.

• 
  Слайд 33

  Summary

  Let’s summarize the steps of the technique. Consider and prioritize according to require-ments all ways which cover whole functionality. Determine all states. Identify all transitions. Create a test case for each way, that covers main functionality. Create additional test cases that cover remaining functionality (if it is needed).

• 
  Слайд 34

  Home Task

  For creating appointment provider selects the date and enters his Short Name (SN). If provider is not busy on selected date he selects an operatory (Op) and a free time from list. After this appointment is created. If the SN was entered incorrectly the warning message appears and SN should be entered again. If provider is busy at selected date the appropriate message appears and provider has to enter the SN and select the date again.

• 
  Слайд 35

  Home Task

  Please, build state transition diagram. Show flows needed for covering all functional. 1 2

• 
  Слайд 36

  The end

  The end of the third lesson. THANK YOU!