[QUESTION] Assertions vs. Checks UI

Given this test definition:

testDefinition:
- selector: span[name = "POST /pokemon/import"]
  assertions:
  - tracetest.span.duration <= 50ms
  - http.status_code = 200
  - tracetest.response.body contains 52
- selector: span[name = "queue.synchronizePokemon send"]
  assertions:
  - messaging.payload contains 52

I read this as "I have two tests or checks. In this first test / check I am asserting 3 things (ie. I have 3 assertions).

However the UI flips these definitions and calls the assertions above, checks. So according to the UI, I have 2 assertions. Assertion 1 contains 3 checks and assertion 2 contains 1 check.

Can someone clarify which was round is correct?

[jorgeepc]

I agree with @agardnerIT in the following structure:

Test – has a set of checks – with a selector – that can match multiple spans – and apply multiple assertions against these selected spans

In my mind, an assertion is one single affirmation, and most test tools use that term with a similar meaning.

Maybe we can find a new word for check that makes it easier to understand the concept of selector + assertions. Any idea?

[agardnerIT]

Perhaps for above: I have one test. The test consists of two checks defined by one selector for each test. Check #1 contains 3 assertions. Check #2 contains one assertion.

Sidenote - the UI doesn’t opinionated on when a “check” fails (ie. if all 3 assertions fail, is the “check” assumed to have failed?)