Forum Discussion

Prudential_UK_A's avatar
Prudential_UK_A
Frequent Contributor
16 years ago

Amending assertions - lag time

Hi,

We have some test requests that have over 1000 assertions on them.  When we try to edit the assertions, if the case has already been run, there is a 2-3 minute lag time for each change.  This is because it is running the assertion against the already produced results.

Would it be possible to add an option whereby you could choose whether you wanted your amended assertions to be run against the response message?  A check box within the assertions window would be ideal and then if you had a lot of assertions like we do, you could save yourself an immense amount of time by selecting this option.

Please let me know your thoughts,

Cheers,
Nicole :-)

3 Replies

  • SmartBear_Suppo's avatar
    SmartBear_Suppo
    Icon for Alumni rankAlumni
    16 years ago
    Hi Nicole!

    over 1000 assertions? wow! I definitely can see this being a problem.. let me think of a solution in the line of your ideas..

    regards,

    /Ole
    eviware.com
  • M_McDonald's avatar
    M_McDonald
    Super Contributor
    16 years ago
    Let me cast my vote here again for a separate assertions step that could be linked to a request. That way multiple assertion groups could be created allowing easier maintenance and allowing groups to be turned on or off easily.

    I have a need for something of this sort in an upcoming project. I have thought about faking it by grabbing the response from the request and "echoing" it via a Mock Service to subsequent requests, each of which would contain a different set of assertions.
  • SmartBear_Suppo's avatar
    SmartBear_Suppo
    Icon for Alumni rankAlumni
    16 years ago
    Hi!

    That is a great idea which has been on our list for a long time, unfortunately always bumped down for more urgent features.. I'll give it another nudge..

    regards!

    /Ole
    eviware.com