-
Notifications
You must be signed in to change notification settings - Fork 31
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[TEST] Fix id convention in model-complete-semantic.bpmn #678
[TEST] Fix id convention in model-complete-semantic.bpmn #678
Conversation
10dc3b7
to
6d1b1d0
Compare
d718e98
to
c008467
Compare
c008467
to
75233c9
Compare
c3e7c7e
to
c309648
Compare
c309648
to
72df6da
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Id and labels names are now consistent. Thanks for that and having improved the positions of the elements in model-complete-semantic.bpmn
}); | ||
expectModelContainsShape('task_with_loop', { | ||
expectModelContainsShape('task_id', { kind: ShapeBpmnElementKind.TASK, label: 'Task' }); | ||
expectModelContainsShape('task_with_loop_id', { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
❓ do you remember why you removed the expectation about font here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
To avoid to duplicate the same expectation about font (and configuration on diagram), I just check it on task_with_flows_id task.
No description provided.