Assertions Panel issue to update assertions since update 3.63
Unable to edit or reorder assertions in a test step after making changes in the Assertions panel. After modifying assertions in the Assertions panel (for example, deleting an assertion) it becomes impossible to further edit the remaining assertions in the test step. Specifically: Assertions cannot be moved or reordered. Remaining assertions cannot be edited or removed.
Create assertion 'templates' so you can apply & edit an assertion to multiple test steps
Right now, assertions are individually managed as unique entries on each test step. I can 'clone' an assertion to multiple other test steps/cases/suites, but it is only a copy. If i have an assertion i want to apply multiple places, it would be EXTREMELY helpful to create a template assertion and apply it to all the relevant test steps. This way if i need to modify the assertion across the board, i could update it in one place rather than editing each individual assertion for every. single. test. step.
Smart Assertions with large responses
We have found that large response messages (e.g., 85000 lines) can cause the Smart Assertion to engage up for an unacceptable time during which the application becomes locked and unresponsive (can be over an hour). The only way to regain control when interacting with the ReadyAPI application is to kill the program process and restart the program. Is there a way to set a time-out for a Smart Assertion? Will this happen using testrunner? I feel we have just gotten lucky this hasn't come up using testrunner via Jenkins, but it feels like we're playing minesweeper and the data will be hit eventually. Thanks.
Unable to Assert or Access Kafka Consumer Data
I have set up a Kafka Consumer using an API Test step and I can see the data returned from the topic under 'Received Data', but I cannot apply assertions or access the data using Get Data function. I saw that this was an issue dating back 3 years ago but the only resolution is a work around creating a consumer using groovy and the apache library. Any thoughts on why this is not possible, and any solutions using the existing API Connection?
Is it possible to set the test case failed reason that is used in the reports?
This question came up a couple of days ago when going through a TestSuite Report with other team members. Is it possible to set the test case failed reason to a custom message? Currently when a TestCase fails the report simply shows the reason as 'Failing due to failed test step', and I was asked "That's a bit vague, any chance of getting a more descriptive message there." This leads to another question, what other reasons are there? I checked back in a few reports and all I ever see is "Failing due to failed test step." I looked through the javadocs and gained no particular insight there. ps. I would love for there to be a "Curiosity" label for questions like these. 😼
