Show HN: We built a tool for fast-forwarding 95% of tests (MIT)
11–18 of 18 posts
Re: Show HN: We built a tool for fast-forwarding 95% of tests (MIT)
#12Re: Show HN: We built a tool for fast-forwarding 95% of tests (MIT)
#13Sounds super cool! I’ll definitely show this to our devops guy in the company. However sounds like there might be a lot of edge cases that don’t include any code changes, e.g. some environment variable changes - have you thought about it?
About the env vars: yes. We have a list of edge cases that might affect the tests. Env vars specifically is the next edge case we are about to cover.
Roey from nabaz.
Re: Show HN: We built a tool for fast-forwarding 95% of tests (MIT)
#14This looks interesting and definitely something missing from our CI pipeline. What languages do you intend to support?
Would love to know more about your use case, email is somewhere in the comments
Re: Show HN: We built a tool for fast-forwarding 95% of tests (MIT)
#15Sounds super cool! I’ll definitely show this to our devops guy in the company. However sounds like there might be a lot of edge cases that don’t include any code changes, e.g. some environment variable changes - have you thought about it?
Hey, awsome! feel free to contact us at hello@nabaz.io. About the env vars: yes. We have a list of edge cases that might affect the tests. Env vars specifically is the next edge case we are about to cover. Roey from nabaz.
Re: Show HN: We built a tool for fast-forwarding 95% of tests (MIT)
#16We took all notes to heart, the main problem we identified that currently (at this stage of the product cycle we don't yet support all edge cases)
And this hurts usability and value, will figure out a way to deliver this kind of tech in a way that is still valuable at this early stage :)
Re: Show HN: We built a tool for fast-forwarding 95% of tests (MIT)
#17Re: Show HN: We built a tool for fast-forwarding 95% of tests (MIT)
#18I'm wondering if this works similar to https://github.com/digitalocean/gta which will do transitive analysis to find packages whose dependencies have changed and only run the tests for those packages?
Let's assume you have a function:
func myFunction(a int) {
if(a > 10) {
func1()
} else if (a
let's assume you changed func3 only, or func2, but during the run of the test only func1 ran.The test will be skipped because no change could of affected it's result. NOT in gta.