Are there some of you who are testing workflows that take multiple days to complete? As an example, a patient is admitted to the hospital on Monday and discharged on Tuesday.
How do you accomplish passing information from the day 1 script to the day 2 script? What issues have you run into? Which cool hacks have you achieved?
Right now, I have my test data sheet in the shared drive, and I will update whatever things need to be noted down for further tests or next day in the sheet, and script will fetch from the sheet. I have my Test_ID as a unique key like T001, T002, etc., and then required columns in sheet. I have written the script which will fetch the required data from the corresponding row or differently as per the needs.
I always use numbering to name the tests or test script files like below so this will be easy to handle data.
001_Create_and_verify_something
002_Check_something_else
The only thing is that EPF is not able to check or get files in the shared folder unless it is mapped like a drive. I would love if EPF handles this without mapping like \\someserver\somefolder as the IT team will delete custom mappings once I logoff, and need to map again before run.
Shan, please mention this to your Eggplant TC. You are not alone in looking for better ways to access network shares.
I would say most our scripts are multi day, meaning we have a Test01_Day1.script, Test01_Day2.script and so on. We have one json (Test01.json) that has a patientdata block (for the patient information) and a scriptdata block which keeps track of which day its on an other non patient
script info run type data. Most of our scripts all start the same where they call a handler to read in the json data. We verify the scriptdata information is valid (correct day) before its allowed to run. The test will update patientdata as it runs but the end of a script will do a final update as well as update the scriptdata block so they next day can validate its ready. Hopefully that made sense