I landed a summer internship where TDD is one of the most important aspect of their development process. At first, it was really hard to find what to test and where to start.
A colleague with more testing experience introduced me to doing "Just Enough": Tightly test the core and most used features. An example is having a project where there is features used by many users and some only used by one administrator. It is vital for our features used by many to be well tested to reduce bugs. The features used by one person, which is an admin, we can cut corners since it only impact one user and he is on our side.
I liked your article a lot and some of these tips will go directly in my toolbox for future test writings.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I landed a summer internship where TDD is one of the most important aspect of their development process. At first, it was really hard to find what to test and where to start.
A colleague with more testing experience introduced me to doing "Just Enough": Tightly test the core and most used features. An example is having a project where there is features used by many users and some only used by one administrator. It is vital for our features used by many to be well tested to reduce bugs. The features used by one person, which is an admin, we can cut corners since it only impact one user and he is on our side.
I liked your article a lot and some of these tips will go directly in my toolbox for future test writings.