There are upgrade branches but somehow they are stale and not worked on anymore. Probably so hard to and test everything manually that they stoped trying at all. How would you go on a project like this if you were to be the new lead there?
After buy-in from higher-ups and the associated teams, look at the development cycle and build process, how a change goes from local to production.
Add automation around linting, running the test suite, and build & deployment. A lot of it can go in dark, in case there's concern about blocking urgent things. Lay down a skeletal pipeline.
Create a couple template projects, for front- and backend, so future projects can start at the highest quality bar and with latest dependencies.
Partner with QA to collect and document test scenarios. On the frontend, at least you'll be able to mock or stub the backend.
Eventually, you'll want this system to block merges and deployments based on agreed-upon criteria. Exceptions can be made, so long as it's documented.
Throughout, it would be nice to add tests. It's an opportunity to understand the domain with fresh eyes as well.
turtleyacht|1 year ago
Add automation around linting, running the test suite, and build & deployment. A lot of it can go in dark, in case there's concern about blocking urgent things. Lay down a skeletal pipeline.
Create a couple template projects, for front- and backend, so future projects can start at the highest quality bar and with latest dependencies.
Partner with QA to collect and document test scenarios. On the frontend, at least you'll be able to mock or stub the backend.
Eventually, you'll want this system to block merges and deployments based on agreed-upon criteria. Exceptions can be made, so long as it's documented.
Throughout, it would be nice to add tests. It's an opportunity to understand the domain with fresh eyes as well.
Add mutation testing too.
morenatron|1 year ago