Hello Vijay,

With our investigation on this issue, we were able to find a way that can help you save time while this issue is being fixed.

Please try:

1. Debug Workflow [F6] or [Debug] button
2. Generate test from debug outputs button
3. As soon as the test surface loads [F5] test run (this should also save the test)
4. Close the test tab and reopen it (this should now show the test(s) you generated from the debug outputs following the above 1 - 3 steps)

A solution for this is underway, please take note of the changes in the status of this ticket to know when we start this work so as when it goes to the next installer.

Kind regards

Siphamandla Dube

Hello Vijay,

The image provided shows the object name as "[[@objGetSimStatus]]" and later the object is called using "[[@objGetSimStatus()]]" and this might be in violation of the Warewolf Syntax. Thus this error, in this case, should rather be expected.

Kind Regards

Siphamandla Dube

Hello Hermant,

In regards to: "Thus, we will keep this ticket open and use it to track the work needed to adjust the mechanism to cater to this." This has been revised and the best solution with this enhancement would be to manually clean the "%programdata%\Warewolf\CoverageReports" folder as with each test we run the Test Coverage report is generated.

Steps:

1. Delete all Coverage Reports inside "%programdata%\Warewolf\CoverageReports"
2. Run http://localhost:3142/secure/.tests or of that specific folder
3. Run http://localhost:3142/secure/.coverage should at this point regenerate all the reports you just removed

With this suggestion, this ticket will be closed.

Closing ticket as the is no longer any further communication in this regard. 

Hello Hermant,

Thank you for bringing these issues to our attention.

• The issue regarding Test 1 coverage report not deleting when Test 1 is deleted has been resolved with Warewolf Version: 2.6.6. However, any existing Test 1 coverage report generated using a Test 1that was deleted using an earlier version of Warewolf, is not catered for with this fix. 
  
  Thus, we will keep this ticket open and use it to track the work needed to adjust the mechanism to cater to this.
• The issue regarding the Error 500 has been resolved with Warewolf Version: 2.6.8, should this not be the same on your side, please log a different ticket which will include the resources of the folder where this break is experienced. 

Hello Jigar,

Thank you for bringing this issue to our attention.

The User selection should indeed be sending the Server_Name and Server_Password of the Server the tests sit-in, which is currently not the case with our codebase, the Public select should also be sending its payload as an anonymous user so this behavior can be tested correctly and hence this ticket will be used to enhance this framework in regards to these behaviors.

However, the security of the Warewolf server will not be in your way should you provide the server the tests sits-in with the Server_Name and Server_Password included in the URL as follows: 
http://[[SERVER_NAME]]:[[SERVER_PASWORD]]@localhost:54914/secure/Hello%20World.tests?Name=etetet" title="http://%5b%5bserver_name%5d%5d:%5b%5bserver_pasword%5d%5d@localhost:54914/secure/hello%20world.tests?name=etetet" href="http://%5B%5BSERVER_NAME%5D%5D:%5B%5BSERVER_PASWORD%5D%5D@localhost:54914/secure/Hello%20World.tests?Name=etetet" rel="noopener noreferrer" target="_blank" tabindex="-1">HTTP://[[SERVER_NAME]]:[[SERVER_PASWORD]]@localhost:54914/secure/Hello%20World.tests?Name=etetet

Hope this suggestion helps you resolve the critical part of your issue.

Kind regards

Siphamandla Dube