Thanks:  0
Likes:  0
Dislikes:  0

# Thread: Manual testing of alternate inputs or paths

1. ## Manual testing of alternate inputs or paths

We discussed about writing manual tests which describe the actions and results in separated steps.

e.g. (Number, action, result)
1, do first, 1st result
2, do second, 2nd result
...
20, do 20, 20 result

given situation 1: <font color="blue">alternate simple inputs </font>
21, fill 1 in field and press ok, result 1 is presented in outputfield

several tests are needed e.g. 1,2,3,4,5
how do I give a smart advice to enter these numbers without writing new 5 teststeps (21 for 1, 22 for 2, ... 25 for 5) ? (Question 1)

an approach is:
21, enter the sequentially the following testdata (1,2,3,4,5), produces the result (1,2,3,4,5)

when an error occurs the tester meight write "in step 21 data 2 has wrong output should 2 but was 21"

given situation 2: <font color="blue">alternate complex input</font>
test path behaviour

a given tree with two sequential inputs should be tested
+ 1 - 1 -&gt; output: 1
+ - 2 -&gt; output: 2
+ 2 - 1 -&gt; output: 2
+ - 2 -&gt; output: 3

how do I give a smart advice to enter these combinations of numbers without writing new 4 teststeps ? (Question 2)

given situation 3: <font color="blue">description of cancel/retry behaviour in teststeps</font>
are there concepts in describing tests not in one line but with branches and repeats as e.g.
first enter 5 and click ok , then you are in test step 12 again
second enter 9 and click ok, then you proceed with the following test steps

how do I manage such scenario without writing new testcases for each combination ? (Question 3)

2. ## Re: Manual testing of alternate inputs or paths

This totally depend on how we are writing the test cases.

First of all we need to identify the test cases with similar flow but different test data.

Take an example, we are writing test cases for an application which consists of differernt scenarios for different set of test data, here one of the approach could be separate test data from the test cases. If there is a test cases which requires 10 set of test data then instead of writing 10 different test cases we can write just one test case and attach the test data file (Test data file coulumns will list out all the variables for test cases, you can even put the expected result and test data result as a column in test data sheet) to the test case which needs to be updated with the test case execution again.

This is one of the approach can be followed.

#### Posting Permissions

• You may not post new threads
• You may not post replies
• You may not post attachments
• You may not edit your posts
•
Search Engine Optimisation provided by DragonByte SEO v2.0.36 (Pro) - vBulletin Mods & Addons Copyright © 2016 DragonByte Technologies Ltd.