cobrakailab

you could try join teams that needs both frontend and backend(by that I mean distributed systems, not just write some api) or ML work. then volunteer more for the backend or ML work to gather more experiences. maybe a team with more senior backend engineers is better.

Thank you guys for your comments. I totally agree with most of you, when the tests are short and simple, when everyone on your team follows good practice, this library is probably an overkill.

But when your system is a bit more complex or a legacy, your unit tests are complex, your team is not that mature, not everyone follows good practice, comments does not match with reality or even crunch multiple scenarios into a single tests, asking them to re-write unit test may sounds rude...(guess I might sounds more like complaining now...), but anyway, that is kinda how all of a sudden this idea came to me the other day while I was writing my own unit tests.

My ideas is if my team can adopt this, at least this can help us improve unit test qualities and readability. Then maybe once we become a more mature team, we can ditch the 'crutches'.