-
-
Notifications
You must be signed in to change notification settings - Fork 2.8k
test intents #153
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
Comments
Could you please post more details here @RonnyPfannschmidt? 😄 |
bascially the equivalent of https://docs.python.org/3/library/unittest.html#distinguishing-test-iterations-using-subtests with an addition of turning tests into sections for acceptance tests |
Hmmm I see, thanks! That seems doable, could be even be implemented as a plugin I think. |
How about? def test_foo(subtests):
for i in xrange(5):
with subtests:
assert i * 2 < 5 |
A bit too minimal Names, retrying and flakyness should be handleable as well |
closing as unactionable wishlist item, wil lcome back with something more concrete |
Created Windows build on Travis
Originally reported by: Ronny Pfannschmidt (BitBucket: RonnyPfannschmidt, GitHub: RonnyPfannschmidt)
to unify various things i'd like to propose a reporting on a level of n subreports per test
the concept for that is an intent within a test
one intent should be something groups a set of operations within a context,
and decides how grave what kind of error is within that context
examples could be things like creating a certain state, working down one item of a user story or gernator test items
== example 1 - generative tests
== example 2 - full capuring of sections
The text was updated successfully, but these errors were encountered: