5 ms·
This has little value to me as it will likely take me longer to write the unit tests (asserts) than most of the functions I'd ask to be written. If you give me
by indymike 5y ago
This has little value to me as it will likely take me longer to write the unit tests (asserts) than most of the functions I'd ask to be written.
If you give me a way to live a documentation link and a register for api access link, I could do more meaningful units of work using my app's public and private apis.
- rahimnathwani 5y agoMaybe we need a service that takes a function, and returns a lot of unit tests.
- Bilal_io 5y agoTest is difficult to be automatically generated. Unit testing Shane's when it catches the edge cases, which cannot be automated or they're very different. That's why a few teams are employing AI to solve this issue.
- rahimnathwani 5y agoCan AI work better than property-based testing? https://hypothesis.works/articles/what-is-property-based-testing/ https://hypothesis.works/articles/what-is-property-based-tes...
- kyriakos 5y agoThis is true, in TDD writing the tests before implementing something is usually more than half of the work cause it requires to figure out how it should work in order to test for the edge cases.
- eneuman 5y agoI get your point and I know there are many kinds of tasks that have a similar issue: difficulty of generating a validation test ~= solving the issue. That's why I imagine cases where it could be easier to have a set of inputs and then compare submissions by several freelancers at once (this would be the validation criteria). Given than (in my experience) hourly cost of a dev in SV > 10 x hourly cost of dev anywhere else, there should be still some margin