5 Matching Annotations
- Jun 2021
But if you're working on a bigger project, with multiple packages and a complex dependency tree, you might want to combine npm with a tool like Lerna.
This is why for a recent Angular+Rails project we chose to use a testing stack from the backend technology’s ecosystem for e2e testing.
We used testing tools that were in the same ecosystem as our backend technology stack for primrily three reasons: We owned both ends of the stack Team experience Interacting with the database
- testing: stack: choosing
- testing: end-to-end
- using disparate technologies in a single project
- how to choose a dependency/library/framework
- key point
- software stack: choosing
- answer the "why?"
- distributed (client/server) system
- frontend vs. backend: owning both ends
- determining if something is an appropriate application / best tool for the job
- end-to-end testing
- explaining why
- how to choose software stack
- testing: stack
- Aug 2020
Knowing all this, what would you do? Which path would you choose and why? The answer might seem obvious now that you come from the future - React