You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I was trying to write some tests and interactors from scratch, I was a little confused about why and when to use child. I think this should have its own section on this page: https://frontside.com/bigtest/docs/platform/writing-your-first-test I saw that I was not supposed to add steps after assertions, but it did not occur to me to use child.
Here are some reasons why someone someone should use child:
Creating sets of steps and assertions
Grouping interactions into logical sections that can be rearranged as the user flow changes
Here's why BigTest uses this structure syntax:
BigTest uses an arrange/act/assert pattern
It's fast to do tests this way
The text was updated successfully, but these errors were encountered:
@jenweber yes, I would unpack the definition of "fast" to say that this allows us to optimize the test run without any extra effort by the user. We already do some first order optimizations, but I foresee us being able to do things like transparently parallelize a test run across multiple browsers with zero changes to your test code.
When I was trying to write some tests and interactors from scratch, I was a little confused about why and when to use
child
. I think this should have its own section on this page: https://frontside.com/bigtest/docs/platform/writing-your-first-test I saw that I was not supposed to add steps after assertions, but it did not occur to me to use child.Here are some reasons why someone someone should use
child
:Here's why BigTest uses this structure syntax:
The text was updated successfully, but these errors were encountered: