Absent Member.
Absent Member.
1353 views

How to pass test data between two manual tests?

Jump to solution

Hello,

I am currently deploying Silk Central on a project and we have some expectations on test data for UAT.

Problematic:

Two end users have to execute two different tests manually. The first user executes his test that generates a data (for instance an invoice number). The second user must use this data to execute his test (resuse of the invoice number).

If we use attachment functionality (file or link), the user must download the file locally, updates it with the output data and overwrites the first version of the file. This solution is not easy to manage and it won't be accepted by our end users because some are not used with computers and testing practices. It will be too complex and or too much time consuming for them.

If we use data-driven functionality, it provides input data and we cannot feed the source with output data.


Is there any easy to use solution to pass an output data of a manual test as an input data for another manual test?

Thanks for your help.

Christophe

0 Likes
2 Solutions

Accepted Solutions
Absent Member.
Absent Member.

Hi Christophe,

Would it be acceptable that the user who runs the first test, then sets a parameter in Silk Central for the second test based on the value they generate?

The reason for this then is the user, is able to read in the parameter created in Test A to Test B, using the parameter syntax:

${invoice}

This would be replaced at runtime for the user who is running Test B.

This step could be added to Test A to ensure the user is running this adds this in Silk Central to the Manual Test.

Any questions let me know.

Thanks,

Matthew

View solution in original post

0 Likes
Absent Member.
Absent Member.

Hi Matthew,

Thanks for your response. Unfortunately this solution won't be accepted.

We are going to use "Manual tests assigned to me" panel in Home to restrict user navigation in SCM (only for UAT). This because some end users are laborers and are not familiar/comfortable with computers.

And updating test parameters will be too much complex for them. They are used to use Excel files for UAT so it will be more constraining with all these actions. We won't to avoid this situation to build a good reputation of SCM.

Thanks again for your help.

Christophe

View solution in original post

0 Likes
2 Replies
Absent Member.
Absent Member.

Hi Christophe,

Would it be acceptable that the user who runs the first test, then sets a parameter in Silk Central for the second test based on the value they generate?

The reason for this then is the user, is able to read in the parameter created in Test A to Test B, using the parameter syntax:

${invoice}

This would be replaced at runtime for the user who is running Test B.

This step could be added to Test A to ensure the user is running this adds this in Silk Central to the Manual Test.

Any questions let me know.

Thanks,

Matthew

View solution in original post

0 Likes
Absent Member.
Absent Member.

Hi Matthew,

Thanks for your response. Unfortunately this solution won't be accepted.

We are going to use "Manual tests assigned to me" panel in Home to restrict user navigation in SCM (only for UAT). This because some end users are laborers and are not familiar/comfortable with computers.

And updating test parameters will be too much complex for them. They are used to use Excel files for UAT so it will be more constraining with all these actions. We won't to avoid this situation to build a good reputation of SCM.

Thanks again for your help.

Christophe

View solution in original post

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.