Forum Discussion

M_McDonald's avatar
M_McDonald
Super Contributor
17 years ago

Handling many assertions

I have many assertions that can apply to a single request. I also do not want to create many duplicate request steps to allow fine-grained testing (eg., assertions a,b and c but not d, e, and f.) To help in this situation, what about one or both of the following:


  • Assertion 'sets' in a request that group assertions together and that allow them to be enabled and disabled together.


  • A separate Assertion Step that can have a Request or a Property as a source to validate against (the Property so that the request could reside in another TestCase that would be called by Run TestCase with the reponse returned to the caller)


Not fully thought out yet, but wanted to get the ideas out there.

Thanks.

3 Replies

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

    thanks for your ideas!

    The "Assert Properties" step has been discussed before, allowing more complex logic to be applied for asserting multiple properties in different teststeps, I think this is the way to go..

    regards!

    /Ole
    eviware.com
  • M_McDonald's avatar
    M_McDonald
    Super Contributor
    16 years ago
    Just bumping this request again. Here's a scenario I would like to be able to handle.

    Say I have a request that returns a variable number of similar XML fragments and I need to execute a set of assertions against each fragment. If there was an Assertion step, I could have DataSource and DataSource Loop steps referring to the request result, with the Assertion step between them, and 1 set of assertions that could be applied against each of the fragments in the result.