Uploading Test Steps in Provar Manager

Now with the test case upload, we are also uploading the test steps. Now, suppose you want to upload a test case. For example, if you are uploading a “Break_with_while” test case. 

Note: A warning is displayed ”Uploading a test case will overwrite all the test steps in Provar Manager”. If other users have already created the test steps manually in Provar Manager and if you are going to upload your test case, that’s where this warning message will be helpful.

Above: Snapshot of warning message at the top that test steps will be overwritten. 

Previously, when you uploaded a test case, only the details (Details, System Information, etc., as shown below in the screenshot) were populated in Provar Manager.

The addition is in the Test Steps section. So, if you are uploading a test case now, you will also see the Test Steps uploaded. So, in the Test Steps section, you can see these test steps.  So, whatever you upload is the latest data.

Note: Whatever configuration, whatever Test steps you have in Provar Manager (in the Test Steps section, it doesn’t matter) will get overwritten by the configuration or the information you are having in Provar Automation. So whatever information you have in your local Provar Studio is the source of truth. So, all this information will be uploaded to the Provar Manager. 

Above: Snapshot of Test Steps uploaded in Provar Manager.

You also have the option to edit the test steps in Provar Manager; click Edit. You can manually edit,  add a test step (click Add Step), delete the test step, can save it. Click Save. A message “Changes saved!” is displayed.

Limitation to uploading Test Steps in Provar Manager

• Firstly, earlier, we used to send/ upload test objects in 200 batches like send plans 200, folders 200, instance 200, and also send 200 test cases. The only change now is that 200 test cases won’t be sent. Test cases will be sent one by one to upload in PM. So, now test cases would be sent one by one, first test case, then second test case, and third, and so on and so forth; because of this, the performance is somewhat slower compared to the earlier scenario when test cases were sent in batches.
• Secondly, the API of Salesforce that we are using, that API has a limitation. So, the one call you send, you can make only 500 changes at maximum. That means, in your test case 500 changes can be done at maximum. For example, you made a very lengthy test case with 1000 steps that will not be uploaded; it will fail.

Here, when we say that the limit is 500, it doesn’t mean that to create it is 500, so when it is overwritten, it will also have to delete this data and then upload the new data. So, this collective information(deletion, insertion, and update) is 500. 

Note: The user shouldn’t assume they can send 500 steps at a time. The collective information(creation, updation, insertion, and deletion ) is 500. That means they can send 500 test step changes. For example, we have a test case that has 500 test steps, and we try to upload it. So, the test case upload will fail and throw this error message, as shown in the screenshot below.