undefined | Better HN

0 pointsTainnor3y ago0 comments

What you're describing looks like magic to me. How would your ticket system know, without it being told (in some way, e.g. through backreferences from the tests), that a particular feature has been implemented? That's very likely going to be a formally undecidable problem.

0 comments

3 comments · 1 top-level

superice3y ago· 2 in thread

Writing end-to-end UI tests to validate a certain behavior and then automatically resolving a ticket once those tests pass seems really cool though. Not sure how realistic in practice, but it's definitely an interesting concept.

TainnorOP3y ago

Sure, but then you have to tag those tests with the ticket, and GP didn't want to have references to JIRA inserted in the code.

The other problem is that you still need to track when all the tests for the feature have been written.

marcus_holmes3y ago

yeah, something like TDD but the ticket is actually a set of integration or end-to-end tests that must pass for the ticket to be "done". Hmmm, interesting...

edit: actually, thinking about it, you could do plain TDD and track the tests as the tickets. Write all your tests for the project first, then track how many are passing as the progress measure.

j / k navigate · click thread line to collapse