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
1 months agoTommy
2 months agoClement
22 hours agoDanilo
24 days agoAlease
2 months agoBarbra
8 days agoLacey
16 days agoKatheryn
18 days agoCharlette
2 months agoErick
2 months agoLashon
17 days agoBettina
18 days agoMari
22 days agoDevora
24 days agoDetra
2 months agoJolanda
1 months agoAsuncion
1 months agoOren
1 months agoYolande
2 months agoCarlee
2 months agoCharlette
2 months ago