Related Content
Why the Burden of Security Should Be Assumed by the Entire Team Quality can be improved over time, and while it’s difficult to change perception, it’s still possible. But poor security can sink your ship before it even leaves the dock. Invest in the security of your application and be sure to spread that responsibility to multiple levels of your software team. |
||
Social Abilities Infuse Tech Know-How with Power Software testers tend to focus their personal development activities almost exclusively on boosting technical acumen, but social systems are just as important. Infusing tech know-how with social skills, such as communication, adaptability, collaboration, and problem-solving abilities, creates team and project success. |
||
Is There a Bias against Manual Testers? Manual testing might not be as all-important as it once was, but it’s still needed if you have any hope of delivering software at a quality you can be proud of. How we create software is going to continue to change, but the burden of that change needs to be handled by more than one group within the industry. |
||
How to Get Started Automating Your API Tests When designing a test automation strategy, an area that is often overlooked is automating API testing. API test scripts are faster and easier to write than other types of scripts and can be fairly simple tests. An added benefit is that API testing can be included in your continuous integration tools for quick feedback. |
||
Do Most Agile Teams Lack Creativity and Innovation? You can’t solve the problem unless you know what that problem is, and you can’t rekindle your creativity if you just don’t know why you’re doing what you’re doing. Pinpoint your team’s purpose, let everyone on your team contribute, and rekindle the innovative nature at the core of agile. |
||
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. |