attest icon indicating copy to clipboard operation
attest copied to clipboard

Modern, Pythonic test automation

Results 25 attest issues
Sort by recently updated
recently updated
newest added

https://github.com/dag/attest/compare/0.5.2...master

documentation

attest should have some way to report test coverage, probably using coverage.py. this is generally a very useful metric and so for attest to gain some real traction needs to...

documentation

- Maybe split tests into unit tests and functional tests etc - The reporter/runner tests could be made more flexible and cover more cases - The "meta tests" could include...

refactor

Similar to #105 but generative. Each context represents a call of each test function in the collection rather than nested contexts. Thanks ronny.

api

In attest, tests may have contexts. What about contexts for test collections? They would be useful for expensive setup/teardown of a collection's "environment". I know that they would not be...

research
api

May be useful to take advantage of Logbook's many handlers, maybe combined with watchdog to run tests continuously and, among other possibilities, get desktop notifications on failures.

idea

I'm testing the last revisions, using the assert_hook stuff. Maybe it's a bit premature to post issues about this feature, but I've written a little test to show the problematic...

research

Ideally I think of contexts as independent of each other, which allows for flexible reuse, but practically it seems useful to be able to get existing test arguments in further...

api

Perhaps keyword arguments would be better than positional arguments. That is: have contexts yield dictionaries, and pass by key name rather than position. This might not be backwards-compatible without some...

api