SOFTWARE TESTING

Nice picture to remember what I have to do :) Following the thought, regret and changing focus from quality would be the real enemy for the tester. The work is not efficient if I start thinking : oh, this is one more trivial usability or minor functionality issue. No one is going to fix it, so no point to worsen our unit's bug statistics by registering it; we need to release quickly in order to finish sprint successfully, so quick shallow testing will be enough - do not want to be bottleneck in my team's performance; loosing motivation to write automated tests or dig into technical stuff after being criticized by seniors. Oh sorry, that is called review and tough character. Quality of tests and skills is also important...  

In my company's techblog, mainly developers are contributing. While browsing across some links in the web, found that companies own pretty interesting tech blogs, sometimes filled with testing or QA relating stuff. Pretty cool to see one more resource to get insiders insights - how do others test, assure quality or handle challenges :) Some links from Linkedin , theGuardian   and Shutterstock  .

As I notice my personal emotional reaction for such kind of comments (above the picture), time to start blogging my testing journey again  :)