Option C is interesting, but I think it's a bit of a stretch to say no adaptation will be needed. The model will define the interfaces, but the test automation architecture will still need to be designed to work with that.
Option C is interesting, but I think it's a bit of a stretch to say no adaptation will be needed. The model will define the interfaces, but the test automation architecture will still need to be designed to work with that.
I'm not sure about option B - if there's a model, there will still need to be an execution layer to actually run the tests, right? Skipping that layer doesn't sound right.
Option A seems like the logical choice here. Model-based testing means the test generation layer will be automated based on the defined model, while the other layers like execution and reporting will still be needed.
Carmen
2 months agoReuben
23 days agoChauncey
26 days agoKandis
1 months agoTommy
3 months agoSylvie
1 months agoClement
1 months agoDanilo
2 months agoAlease
3 months agoBarbra
2 months agoLacey
2 months agoKatheryn
2 months agoCharlette
3 months agoErick
3 months agoLashon
2 months agoBettina
2 months agoMari
2 months agoDevora
2 months agoDetra
3 months agoJolanda
3 months agoAsuncion
3 months agoOren
3 months agoYolande
3 months agoCarlee
4 months agoCharlette
4 months ago