Related Content
An Agile Mindset: Learning Early, Not Failing Fast Agile encourages teams to continuously improve through learning. One of the phrases associated with this process is "failing fast"—trying new things and taking lessons from mistakes as you go. But Johanna Rothman thinks "learning early" is a better phrase. That change in terminology can give you a happier mindset. |
||
The Difference between Software Testing and Hardware Testing Hardware and software have become a necessary part of virtually every company and household, and the vendors that serve these audiences must ensure that their products work as they should. Sanjay Zalavadia looks at the difference between software testing and hardware testing. |
||
The Value of Experimentation in Testing With new concepts, platforms, methodologies, and devices being introduced at a rapid rate, it’s critical to both initiate and establish a culture of experimentation within your testing team. You need to experiment and take risks in order to keep pace and hopefully surpass the competition. |
||
3 Common Collaboration Problems for Teams Transitioning to Agile A shift toward working in smaller teams on tighter releases forces organizations adopting agile to rethink what successful delivery looks like. It can be a big change for those used to silos. Here are three key symptoms of agile teams that don’t have close collaboration—and some solutions you can implement to fix them. |
||
The Importance of Testing in Conjunction While it is important to have distinction between testing efforts to maintain specialization and core subject matter expertise, having overlap in test efforts—testing in conjunction—is becoming a common practice. |
||
Has Mobile App Quality Caught Up with the Rest of the Industry? Software companies around the world are putting a significant portion of their resources into mobile application development. And even though we’ve made great strides in terms of speed and security, can mobile app quality hold a candle to more traditional applications? |
||
3 Reasons Exploratory Testing Is Great for Agile Teams Specification-based testing is critical for determining whether a user story is “done done.” But that doesn’t ensure a positive user experience. Coherence, comprehension, and usability are beyond the scope of automated functional testing. Here are three reasons agile teams should embrace exploratory testing. |
||
Software Testers, What Should You Be Doing Right Now? As a software tester, there are any number of jobs you could be doing at any given time. The first problem in software testing, the one we have to think about before even deciding on our approach, is: What should I be working on right now? Communication, time management, and prioritization are essential to our jobs. |