|
Practical Security Testing for Web Applications It seems like every week the press has yet another story about security breaches or stolen data at some of the world’s largest companies or government agencies. Sometimes the responsibility for ensuring thorough security resides with an IT security group, and other times it gets outsourced altogether. The responsibility seldom falls to testing teams. However, this is changing. Having trained and experienced testers hunt for security bugs will make web applications safer from hackers and will further protect consumers, corporate assets, and brands.. Scott Aziz offers some practical techniques that will help you get started.
|
|
|
Why Is Extrapolation of Results in Performance Testing a Bad Idea? In this installment of FAQ, SQE Trainer Dale Perry answers one of the questions students ask him most often.
|
|
|
Automating Content Creation: An Interview with Clark Malmgren We recently had a chance to speak with senior engineering manager (applications) for Comcast Video Services, Clark Malmgren, about his role in test automation and how his experience and practices can lead to success in many areas of software testing.
|
|
|
Selecting the Right Mobile Testing Solution The mobile market dynamics are extreme, unpredictable, and fragmented. There are numerous operating systems and a multitude of platform versions, networks, hardware, and form factors making it a challenge to maintain mobile application quality. Find out how to adjust to the shift from traditional to mobile development—which additional elements are a must and which ones can be maintained.
|
|
|
From One Expert to Another: Markus Gärtner Markus Gärtner is a tester and the author of ATDD by Example. In this interview with Zeger van Hese, Markus talks about his new book, the software craftsmanship movement, and “Beyond Testing,” a workshop he’ll be delivering later this year.
|
|
|
FAQ: How Can I Know When to Stop Testing? In this installment of FAQ, SQE Trainer Rick Craig answers one of the questions students ask him most often.
|
|
|
Software Design for Testability Testability is a key ingredient for building robust and sustainable systems. Neglecting testability during software development increases technical debt and has severe consequences on systems that are destined to operate for many years. Peter Zimmerer describes influencing factors and constraints of designing software for testability and shares his experiences on the value and benefits of testability-and the repercussions of poor testability. Using real-world projects as examples, Peter describes key factors in designing for testability-an architecture providing control and observation points, testing interfaces, built-in tests, logging and tracing, diagnosis facilities, and more. Take back a checklist of important issues, facts, and practices on designing for testability in your systems.
|
Peter Zimmerer, Siemens AG
|
|
Automated Acceptance Testing of iOS and Android Applications In the fragmentation game, mobile devices have now claimed first place over the browsers. Android is scoring most of the fragmentation points for the team, but iOS isn't just standing idly by. While automated testing is a natural part of most modern software projects, it is currently not implemented on many mobile projects. Jonas Maturana Larsen and his company, LessPainful, are working to change this. Jonas introduces the BDD-framework Cucumber and shows how to use it to ease the pain of testing mobile applications across different devices, manufacturers, screen sizes, and Android versions. Drawing from his experiences working on Android projects for clients, Jonas shares war stories, highlighting some of the nasty quirks his team has encountered in Android OS.
|
Jonas Larsen, LessPainful
|
|
Design Patterns in Automated Testing: May the Power Be with You To keep up with ever-changing systems, most test automation developers spend countless hours updating, reworking, debugging, and validating test scripts. In an agile environment, keeping up is even more difficult. Bindu Laxminarayan explores powerful design patterns and coding practices she uses to maintain, extend, and reuse the test automation scripts. These design patterns will aid you in developing a robust automation framework and cut down the time you spend on routine maintenance tasks. Bindu describes and illustrates specific design patterns: Template Design Pattern, Test Object Pattern, Component Object Pattern, and Page Object Pattern. Take back code samples to help you understand the patterns in detail. By putting these patterns into practice, you'll improve test case development and make script debugging more efficient.
|
Bindu Laxminarayan, Overstock.com
|
|
Visualization: Seeing Test Requirements in a New Light Change is everywhere in software-feature enhancements, regulatory requirements, technology updates, re-designs, and re-implementations. How can we ensure that testers really understand requirements, business rules, and know what’s changing? Vijay Atmavilas shares how Verisign began to employ visual modeling and visual test design techniques to address these challenges. New models were produced using diagrams that highlighted process flows, input types and combinations to highlight data, and scenarios to highlight usage. As a result, team members quickly increased their understanding of feature requirements and improved their testing. Learn how Vijay and his team employ visual models to identify undertested functional areas and to help them measure coverage and the effectiveness of their regression tests and suites.
|
Vijay Atmavilas, VeriSign Inc
|