Okiseleva.blogspot.com Website Review

LIFE IS A MOVEMENT! And TESTING - THIS IS LIFE :) table of contents, so as not to flip through a lot of textbooks, but go straight where When you start a task, you need to justify it. You have to convince And sometimes you read bugs (especially newbie bugs) and ask yourself: I always say that you need and there are exceptions to justify your tasks. We really do NOT need to write a rationale if the system: Especially if it happened in production. If our site is lying here, there is no justification, it is necessary to beat the gong and run to the developer “urgently fix it!”. You can do without a bug. And you can with a brief “Error 500 on the main one”, that's enough. No need to su*k the rationale of the finger, because it is always necessary. To write the system should not fall - text for the sake of text. But! You must write the expected result. Even if it seems obvious to you, write it down, it will not lose you. > EXPECTED RESULT> The main page opened But there are examples. When you start a bug, you need to justify your expected result. Sometimes they don’t write a rationale at all, because “it's obvious!