4 ms·
I'm working in hell right now. The current company has the site frontend, backend, and tests in separate repos and it's basically impossible to do anything with
by Gigachad 5y ago
I'm working in hell right now. The current company has the site frontend, backend, and tests in separate repos and it's basically impossible to do anything without force merging because the build is broken without a chicken and egg situation between the 3 pull requests.
- laurent123456 5y agoI worked at a company that not only did that, but also decided to split the main web app into multiple repos, one per country. It was so much fun to do anything in this project.
- xorcist 5y agoNow, that's a microservice if there ever was one!
- Iwan-Zotow 5y agothat is some good office porno!
- hinkley 5y agoYou might want the front end and backend to be compatible across revision numbers, so that’s less of a problem and more of an impedance mismatch with your process. The tests are a trickier problem, in theory you could lock version numbers (the new behavior increments to the new tests) but tests have bugs, and this doesn’t solve two people making behavioral changes at the same time. Short of merging the tests into the respective projects, going full feature toggle for all breaking changes is the only other lever that comes to mind.
- erik_seaberg 5y agoThis. Deployments and rollbacks are not atomic, so atomic commits do not make frontend+backend breaking changes safe.
- Gigachad 5y agoMy thinking is that the tests _have_ to be merged with frontend since they do stuff like "Find the button with the content 'continue' and then click it" There is no such thing as backwards compatible changes to button content but yeah you are right, it would be possible to create backwards compatible API changes but I don't know if it's even worth it since we are the only users of the api, and it is only used for the frontend.
- nitrogen 5y agoThere is no such thing as backwards compatible changes to button content If your form html is reasonably semantically structured, and/or you give meaningful IDs to each interactive element, then your tests can be made somewhat robust against content changes. E.g. "click button #next-step" rather than "click the word Next". If your frontend is a desktop or mobile app, look for ways to introspect the widget hierarchy to do the same thing (I know this is possible in e.g. Swing).
- Vinnl 5y agoBut generally you'll want to emulate how users use your application, which is looking for a button with a particular label (bonus points if your tests are looking for the accessible label), rather than something with a given ID.