I believe that the best way to discover new tools is by having tasks and problems that require them Why bother trying something new if you don’t have a real advantage in using it or a problem to solve? Of course, it’s always good to learn and try new things but it’s a different story Some tools may be useful for me in the future, but it’s mostly about developing your skills and exploring new options. Sometimes, in terms of improving my work efficiency new tools are useless because I don’t have appropriate cases to use them or existing is effective enough for the business, and implementing ne ..read more

All of them and: (x) Developing them by myself ..read more

shad0wpuppet: I believe on the MoT platform and here on Club you’ll find dozens of resources for beginners Hi @giedras. Thanks for sharing here. Amplifying @shad0wpuppet’s comment. Feel free to dive into lots of super helpful questions and answers via the new-to-testing tag. Perhaps it might give you lots of ideas and avenues to explore. The community absolutely appreciates it can be super overwhelming to join the world of testing. One day Ministry of Testing will provide a Foundation Certificate in Software Testing which will also be another way for folks to get stuck in. In the meantime ..read more

F is for flaky tests What else ..read more

Whether or not we’re aware of it, we probably all have a default testing persona. We touched on this during a This Week in Testing call. Reflecting on this now and being open, I guess my default testing persona is someone who wants to get the thing done with minimum fuss via the app/site I’m using. Is someone who is technically savvy and understands how to browse and navigate without any accessibility requirements. Is someone a bit forgiving when things go wrong yet is keen to raise problems when they occur and also likes to celebrate the good stuff. There’s no right or wrong persona here yet ..read more

Cem Kaner has a well-rounded description of the scenario testing technique I recommend looking into: kaner.com ScenarioIntroVer4.pdf 251.02 KB ..read more

I think of this generally: Responsiveness - how quickly a service returns a response; Load - how the system reacts under some load over time or at a time. Most of the rest rely on these initial types, they just vary things a bit, depend on certain quality characteristics, or relate to how testing is done or the outcome expected. Digging on the internet for types of performance tests I collected these: load, stress, soak/endurance, spike, scalability, volume, concurrency, throughput, latency, benchmark, isolation, failover, compatibility, distributed, real user monitor, resource utilization, ca ..read more

If you hear the term scenario of mobile application what comes to mind? Well, I was thinking about that and made a short article about the Mobile Application Testing Scenarios. Have a look and write to me what you think ..read more

I’m disappointed in the clickbait of the BBC, but it did make me chuckle. BBC News Apple working to fix alarming iPhone issue Users have been reporting unexpected lie-ins after the alarms on their phones failed to go off ..read more

Going by their git code for the axe-core library used by cypress: github.com dequelabs/axe-core/blob/7ac63921e7fab21f3359dcfc8affa7585bc9c25b/build/configure.js#L58 }; var descriptions = { wcag20: { title: 'WCAG 2.0 Level A & AA Rules', rules: [] }, wcag21: { title: 'WCAG 2.1 Level A & AA Rules', rules: [] }, wcag22: { title: 'WCAG 2.2 Level A & AA Rules', intro: 'These rules are disabled by default, until WCAG 2.2 is more widely adopted and required.', rules: [] }, bestPractice: { title: 'Best Practices Rules', intro: 'Rules that do not necessarily conform to WCAG succes ..read more