_cfl0

11 ms·

1. 31.▲
   by _cfl0 4y ago

   Wow! Seems like a challenge to test, would love to see what we can do. Regarding side effects, completely fine as long as they're mapped out. Would love to hear more, nothing pitchy or salesy.
2. 32.▲
   by _cfl0 4y ago

   java is scheduled next, would absolutely love to hear about your use-case?
3. 33.▲
   by _cfl0 4y ago

   That's a great point! Depends on the what you define by "externality". I like to look at it this way, what's being tested? I see three groups: - testing the software you wrote. - testing integration with other soft
4. 34.▲
   by _cfl0 4y ago

   Meta and Google employ AI based methods for skipping tests (See): they are pretty much flawed in a way, because they require you to wait weeks/months to gain statistical sagnificance. And even then they are too costly to train to make
5. 35.▲
   by _cfl0 4y ago

   How it works: First time you run nabaz: 1. Collects code coverage for every tests that runs, seperatly . 2. Saves code coverage in local sqlite db, along with commit ID as key. Second to n runs later: 1. Traverse git tree and que
6. 36.▲
   Show HN: We built a tool for fast-forwarding 95% of tests (MIT)(github.com)

   8 points by _cfl0 4y ago|17 comments