Related Content
Devices and Desires: Understanding How Users Experience Your Software When we design, build, test, and deliver software, it is imperative that we provide our users with what they need—not what we want, but what that they want. We need to understand the scope and breadth of the user base. Here are three questions to ask to learn more about how users experience your software. |
||
Security Testers Should Think like Hackers It is a common belief that testers should think like end-users by going beyond the defined requirements, seeing if the application under test addresses end-user expectations, and evaluating how it fares against competition. But with security testing, testers have to think not only like end-users, but also like hackers. |
||
Elevate Code Quality by Integrating Testing and Development Pair programming generally involves two programmers working on a single change from start to finish. You can augment this pattern by adding a test specialist, so you can test-drive feature changes first and the tester can ask questions and guide test and code design. What you get is quality built in from the start. |
||
What’s Our Job When the Machines Do Testing? It’s a safe bet that testing jobs won't be taken over by machines anytime soon. However, those of us in the test industry would be wise to heed cross-industry applications of analytics and machine learning and begin staking out the proper role of the machine in our testing domain. What could AI mean for testing? |
||
UI and the Need to Meet User Demands A customer-centric mindset might be most important when it comes to the user experience and user interface. With so many different available options on mobile devices, if users don’t like the way your app runs, looks, or functions, they’ll drop it before you get a chance to update anything. |
||
Embedding Performance Engineering into Continuous Integration and Delivery In the world of continuous integration and continuous delivery, the importance of ensuring good performance has increased immensely. While functional and unit testing are relatively easier to integrate into these processes, performance engineering has typically raised more challenges. Here's how you can mitigate them. |
||
Do Testers Really Need to Learn How to Code? Because automation, AI, and agile have changed how we test software, the thought is that testers need to understand a certain amount of coding so that they can make themselves more well-rounded and better able to adapt within a software project. But there are other things testers can focus on before learning to code. |
||
Testing Next-Generation Digital Interfaces With chatbots, facial recognition, voice integrations, and more, digital interfaces have a complex software side. With concrete examples from the market, Amir Rozenberg offers new approaches for embedding quality and test activities into the development cycle when dealing with this new generation of digital interfaces. |