Another couple of questions from a new twist user:
1) Where I have used content assist for workflow steps or introduced workflow steps that exist in other workflows in the project, for every step or group of steps I use from a different workflow it brings the name of that workflow with it, so I have ended up with a long list of workflow names along the top of my business workflow...the only way I seem to be able to avoid this is to call all of my business workflows the same thing! Am I misunderstanding something?
2) In the Twist help Business Workflow page http://www.thoughtworks-studios.com/twist-agile-test-automation/1.0/help/concept_business_workflow.html one of the reasons used for writing your business workflow steps simply is "The scenario will have to be modified whenever the user interface changes. This leads to brittle tests that will need a lot of maintenance."...but surely if the test is automated and the UI changes there is a good chance that the automated test will break anyway because that will have been recorded (or coded) to the previous UI. I do understand the other reasons for writing the workflow at that level, and for manual testing it is a far more flexible approach, but again am wondering whether I am misunderstanding something here?
Thanks in advance for your plain-English answers,
Please sign in to leave a comment.