Estimation

Testing Efforts

Functional Testing (Testing for Stories)

Execute all written steps and check for their results on scenario(usac)

5 mins - for verification/functional testing per Scenario(per user type)

Includes functional testing

Exploratory testing - for unwritten scenario

Sanity Testing (Testing for Defect)

Similar with functional test, but this type of testing is specific for Defect Tickets

This is the functional testing for DEFECTS/BUGS

5 mins - for verification/functional testing per Scenario(per user type)

Smoke Testing (Optional)

Super Happy Path based on Story/Scenario

3 mins - for happy path verification per Scenario(per user type)

Spot Testing (No need to include)

This is for stories that are easy to execute such as navigation of pages and etc..

Quick examination such as functionality of buttons whether they work as intended

5 mins - only for quick checking of the feature

End-to-End Testing

(functional testing x total no. of Feature scenario)

eg. (5mins x 10) = 50mins

Total 25 minutes

Test Case Creation

4-5 Test Cases per hour on a good day

3-4 Test Cases per hour on a bad day

20 minutes TC creation per scenario

5 minutes for FC Testing

5 minutes for Sanity Testing

End to End depends but can be 5-10 minutes

40-45 no buffer period

50 minutes - 60 minutes with additional buffer period (Comfortable, including bad day)

Upon consulting with tito micz and knowledge understood to Tito Ram

Want to print your doc?
This is not the way.

Try clicking the ⋯ next to your doc name or using a keyboard shortcut (

CtrlP

) instead.