In your experience, is it recommended to have different spec files depending on which type of test you are working on (i.e *.integrated.spec.ts) or to put everything in a single file?
Amadou is a Frontend Software Engineer from Senegal 🇸🇳 based in France 🇫🇷. He's a Google Developer Expert in Angular, and currently works at Air France.
I usually don't use *.integrated.spec.ts to make the distinction. I tend to put everything in the same file.
But it doesn't hurt if the file is named mean.pipe.integrated.spec.ts in my opinion.
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.
Thanks a lot for sharing! Keep it up!
In your experience, is it recommended to have different spec files depending on which type of test you are working on (i.e *.integrated.spec.ts) or to put everything in a single file?
Thank you for your time!
Hello Andrei,
Thanks for your kind comment.
I usually don't use
*.integrated.spec.tsto make the distinction. I tend to put everything in the same file.But it doesn't hurt if the file is named
mean.pipe.integrated.spec.tsin my opinion.