hitchstory

14 ms·

1. 151.▲
   by hitchstory 3y ago

   >When I use BDD, it's because I'm handed down scenarii written by non-tech people. And it's always in the Gherkin format Thats interesting. You're the first person I've heard of who actually did that rather than
2. 152.▲
   by hitchstory 3y ago

   The worst was "leading indicator". It was used initially to mean inputs to a machine learning model, but it organically spread to refer to almost any form of data at any point in the ML pipeline.
3. 153.▲
   by hitchstory 3y ago

   Good and bad names are a result of context.
4. 154.▲
   by hitchstory 3y ago

   Sounds like we had the same idea: https://github.com/hitchdev/hitchstory Like you I also dont want to go back. Declarative tests are the future.
5. 155.▲
   by hitchstory 3y ago

   I understand the hate. I created StrictYAML, which this tool uses, because of it (see the Norway problem - that was me). Type safety is paramount and regular YAML does not have any type safety. I also understand the hate from the perspectiv
6. 156.▲
   by hitchstory 3y ago

   If you like pytest and BDD I'd encourage you to check out my pytest library: https://github.com/hitchdev/hitchstory With it you can write integration tests with typesafe YAML which double as user friendly document
7. 157.▲
   by hitchstory 3y ago

   I'm a bit weirded out by how judgmental people get about this. Cafes that wanted to ban laptops are free to do so and always have been. Generally people who work on laptops come in during periods when the cafe would otherwise be fairly
8. 158.▲
   by hitchstory 3y ago

   Ive had product owners take an interest in docs autogenerated from tests. Especially with artrfacts embedded. They like tuff like this: https://github.com/hitchdev/hitchstory/blob/master/examples/...
9. 159.▲
   by hitchstory 3y ago

   This looks amazing.
10. 160.▲
    by hitchstory 4y ago

    Unfortunately Uncle Bob used to preach 100% usage and IIRC Beck never really specified when it should be used.
11. 161.▲
    by hitchstory 4y ago

    I built this framework coz while I didn't believe in "code as documentation" I did believe that example based specifications, tests and documentation were all sort of the same thing (triality): https://hitchdev.c
12. 162.▲
    by hitchstory 4y ago

    I built this documentation/testing framework to do just that: https://hitchdev.com/hitchstory I realized one day that the specs, tests and how-to markdown documentation I wrote all used the same examples. From that I d
13. 163.▲
    by hitchstory 4y ago

    I had a similar experience. After swapping out robot with pytest on a large project I was at least 4x as productive. The one thing I did like was the separation of concerns between a "readable" specification written in a non turin