Sometimes you may find that when you have stopped a recording, the data transfer step takes a very, very long time. The Recording Status screen shows this:
Upon investigation, you find that the job (/BTI/AUT_BTRAN_TRANS_MASS) that does the data transfer between the source system and the central system has failed.
Once you have investigated the reason for the failure and fixed it, you need to manually run the data transfer and (optionall7) change the status of the recording to complete. The steps below show you how to do this.
Note that all steps are performed on the Testimony Central System.
Step 1: Get the Test Plan ID
Your test plan name is shown in the Plan section of the screen.
In order to run the manual data extraction, you need to get the internal ID of the test plan.
Go to SE16 and browse the contents of table /BTI/AUT_C_TPLN. Here you can find your test plan and its unique id.
Step 2: Run the manual data extraction
Go to SE38 and execute program /BTI/AUT_BTRAN_TRANS_MASS.
Use Goto --> Variants --> Get to load the default variant. This will set the relevant technical settings for the run.
Now replace the field P_PLANID with the plan number you retrieved earlier.
Execute the program.
This program uses BTI’s Diffuser technology to start multiple parallel background jobs to retrieve the recorded data from the source system and store it in the central system. Upon executing the program you are taken to the Diffuser Minicube transaction from where you can monitor the progress of the run. Use the refresh button to update the status so you can see when the run has finished, as below.
Step 3: Verify that data has been transferred
To verify that the data has been transferred, go to the Standard / Filtered Recording screen for your test plan (depending on the type of recording you ran) to ensure that you can see the recorded data.
(Note that the “Not transferred” status on this screen means that the scripts have not yet been transferred to the repository; the data has, though, been transferred from the source system to the central system. Transferring data to the repository is done in a subsequent step in the Testimony Recording/Playback process.)
Step 4 (Optional): Changing the status of the recording
At this stage, your recording will still have a status of “Data transfer” as the manual data transfer process you’ve just executed is not “linked” to the recording itself.
There is no harm in leaving the recording in this status, but if you expect that you will want to perform further recordings in this test plan, you should change the status to Complete.
You do this by editing an entry in table /BTI/AUT_C_LSTA using SE16. Enter your test plan ID in the PLNID field to display the relevant row.
You will see that field AGNST is showing a status of “12”, which is the Data Transfer status. We need to change this to status “11” to show that the recording has completed.
Edit the row to make this change and save it in the database.
Once this has been done, the recording will show as Completed in the Recording Status header screen.
However, the individual recording run will still show as in Data transfer status in the detailed information for all recordings for this test plan.
To change this, we need to make a similar edit as before, this time to table /BTI/AUT_C_LSTH. As before, use SE16 and enter your plan number in the selection screen to show all individual recording runs for this plan. You will see that one of them still shows a status of “12” in field AGNST.
Edit this row to change this field to “11”.
Now the Recording Status screen shows all recordings as being complete.