When do you decide to start testing? What do you start testing for? What are things you are looking for and what are things you don't look for when you test?
For further actions, you may consider blocking this person and/or reporting abuse
When do you decide to start testing? What do you start testing for? What are things you are looking for and what are things you don't look for when you test?
For further actions, you may consider blocking this person and/or reporting abuse
Luca Liu -
Grenish rai -
Sotiris Kourouklis -
Gabrielle Niamat -
Top comments (2)
Testing plays a pretty huge role in everything we do. Strategically we use testing for:
I'm no heavy-handed evangelist of any of this stuff, but I'd say our strategy is mostly to achieve the points listed here, with plenty of laziness or hurriedness mixed in along the way.
We do a lot of integration with 3rd party and client software. This ends up providing me with an additional level to catch issues in integrated environments. I do take advantage of this, meaning I don't always investigate integration requirements or content as well as I could to catch issues. But what I do end up with lets me track down issue by reproducing them quickly.
I find that clients a much more willing to see issues if the resolution and build is fast. Obviously things can be much different when end-user are the client.