I am using the jbehave for automated testing. What I am doing in the story as high level:
1.Setup test data in the dependent systems 2.Send the request to the system under test 3.Once the response received, verify what is in the database with the expected results
There are few hundred scenarios and executing the same steps.
There are cases that the system under test may create extra records in the database, and these get persisted after the initial response is received by jbehave and missed.
The question here is that how it would possible to do another phase of number verification once all scenario execution finish ? i.e. a successful scenario may fail on the next phase so need to keep track and mark it failed again We need to have some sort of handle in to the jbehave context, so we can mark it as failed on the second phase of verification when necessary.
Aucun commentaire:
Enregistrer un commentaire