3 ms·
> strict development environment fixated on validation I've spent some time working with ill-defined scenarios/flows so having validation doesn't look to be so
by drdaeman 9y ago
> strict development environment fixated on validation
I've spent some time working with ill-defined scenarios/flows so having validation doesn't look to be something bad to me. Although I had never worked in an environment that could be said to be fixated on it, so I guess I'm missing something.
So I wonder... what's bad about this? (Or I misunderstood what this is about?)
- expertentipp 9y agoI meant mostly which activities trigger running the tests of the project locally and on the CI server. Local build, git hooks, push to remote? Does CI validate all remote branches, is it possible to disable running tests on a particular branch? Given an overzealous quality evangelist in the team, there are too many ways to paralyze the workflow of those preferring to have space to move and air to breathe. Configuration of tools like JSHint can easily go too far as well.
- closeparen 9y agoHmm. We use Phabricator, and while you're free to skip unit tests and linters locally (on by default, but can be skipped) or ignore Jenkins build failures as you iterate over a diff, the expectation is that you get all the tests and linters to pass before landing to master (and usually before soliciting reviewers).
- zippergz 9y agoI've worked in places where the friction and overhead caused by the validation and QA process caused more damage than the issues they were trying to solve. As in most things, you need a balance.