StringCalculatorPage autogenerates app element IDs #53
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
StringCalculatorPage.new() works well, but I realized two things:
I could autogenerate app element IDs using monotonically increasing numbers, eliminating the need for an appElemId argument.
Creating and destroying a new <div> for every test case seemed to start slowing the tests down.
Now the guidance isn't to call StringCalculatorPage.cleanup() in afterEach, but to use the pattern: