I started tracking our organization’s Mean TIme to Detect (MTTD) a defect, and immediately noticed that the majority of defects opened were being discovered later
We’ve all been there. Cornered by your boss, usually near the end of the day, and you’re asked to test something “real quick”. You want
I would argue that just about every piece of the Software Development Lifecycle (SDLC) has drastically changed over the last decade, with the exception of
In America, 61 million people currently live with disabilities; globally that number reaches over a billion, according to the World Health Organization (WHO) (WHO/Y. Shimizu, Disability and Health). Testing your software to ensure that every person, disability or not, can browse and engage with your website is known as web accessibility testing. These disabilities include vision, physical, cognitive, literacy, and auditory disabilities. Understanding the unique testing considerations for each can be overwhelming, however, that understanding is important when creating your accessibility testing plan. In this article, I’ve outlined the importance and types of accessibility testing, specific things you can test for, and free tools that can help you execute your tests.
One of the most important things a tester can do is prepare. Writing test cases in advance, understanding the architecture of the feature you’re being given