I have been leaning towards not having descriptors for tests at all. If you think about it even an "integration" test is really just a really big unit test. And all tests should be written from the end-user's point of view, just some end users are developers and others are customers.
Just define what the unit and user is for a given test suite.
Yes, this seems like a very sensible approach. I think it's just a shame there isn't a good short word to describe these tests that everyone agrees on and has the same understanding of. I suppose we should concentrate on the concepts and not the names.
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 have been leaning towards not having descriptors for tests at all. If you think about it even an "integration" test is really just a really big unit test. And all tests should be written from the end-user's point of view, just some end users are developers and others are customers.
Just define what the unit and user is for a given test suite.
Yes, this seems like a very sensible approach. I think it's just a shame there isn't a good short word to describe these tests that everyone agrees on and has the same understanding of. I suppose we should concentrate on the concepts and not the names.