We will be alternating with TISQA (Triangle Information Systems Quality Association). The next TISQA conference is in 2018, please join us for that.
Subscribe to be one of the first to know when the next Zenposium will be.
Bug Fest! Exterminating Pesky Bugs Using Kanban Techniques
Know any testers who have bugs opened more than a year ago and still sitting in their defect queue? More than two years ago? Three? The fact is that many software development efforts are focused on delivering new features and functionality, leaving workarounds in place for bugs released in prior versions of applications. Often these defects seem relatively minor—we all have some workarounds for customers—but these are still bugs and ultimately should be dealt with. If you are seeking effective methods to close out those bugs once and for all, Shaun Bradshaw shares his experience eradicating aging bugs—in a Bugfest! Shaun shows how to effectively use kanban techniques to bring visibility to a myriad of outstanding problems left over from previous releases as well as to order and prioritize the work to clear out the nastiest, most offensive defects—and ultimately exterminate those pesky bugs!
Nature vs. Nurture: Building Great Test Teams
When organizations expand internal test teams, hiring managers sort through piles of résumés hoping for a few gems. But scanning for coveted technical skills and relevant experience often leads to disappointment. With the proliferation of new software and the explosion of mobile devices, the QA industry is surging, and experienced testers are becoming harder to find. What inherent qualities do great testers really possess? Do those attributes show up on résumés? Should technical expertise or tool/application knowledge drive the hiring decision for new testers or are there more important capabilities and talents that managers should consider? Résumés often fail to describe other important factors, including the “tester’s mindset.” By zeroing in only on technical experience, we risk minimizing or ignoring the vital characteristics—curiosity, skepticism, and cooperativeness—of great testers. Join Shaun Bradshaw as he shares a proven, multi-step process used to evaluate candidates for the “tester’s mindset” and discusses the necessary technical aptitude that will create top performing testers. Learn the importance of developing and providing ongoing training and mentoring to ensure the process of building great test teams doesn’t end with the hire.
Integrating Mobile Automation with Jenkins
This presentation will cover an actual use case of mobile automation to proactively drive mobile website and application testing activities. Topics covered include:
– Using one script to test mobile and desktop websites
– Ensuring smoke test execution as part of the continuous integration (CI) process
– Providing timely reporting to make go/no-go decisions
– Use the Perfecto Mobile plugin with Eclipse and Java
– Leverage Perfecto Mobile cloud for mobile execution
– Use Selenium WebDriver
– Use TestNG and ReportNG
– Integrate with Jenkins
– Execution time reduced by 80%
– Coverage increased by 100% over manual testing
– Jenkins triggers automation of scripts across desktop browsers, including Firefox, IE, Safari and Chrome
– Jenkins schedules regression execution.
Mobile Testing: QA Strategy for Manual and Automated Testing
This course focuses on the major aspects that QA managers, test analysts, and test automation engineers must consider before undertaking a mobile QA/testing project. A combination of lecture, classroom discussion, and experiential techniques provide attendees with a thorough understanding of the strategies and efforts necessary to test mobile websites and apps. This includes the challenges of mobile testing, the strategy necessary to support both automated and manual testing projects, and additional considerations all testing professionals need to know.
A Tester's Guide to Collaborating with Product Owners
The role of the product owner in Scrum is only vaguely defined—owning the product backlog and representing the “customer.” In many organizations, product owners go it alone, trying their best to represent business needs to their teams. What’s often missing is a collaborative connection between the teams’ testers and the product owner—a connection in which testers help to define and refine requirements, broaden the testing landscape and align it to customer needs, provide a conduit for collaboration between the customer and the team, assure that the team is building the right thing, and help demonstrate complete features. This relationship is central to the team and facilitates transparency to help gain feedback from the entire organization. Join seasoned agile coach Bob Galen as he shares techniques for doing just this. Return with new ideas and techniques for helping your product owner and team deliver better received and higher value products—not just by testing but by fostering collaboration.
Establishing Agile Centric Release Criteria
A huge quality-centered activity in agile teams is establishing a Definition of Done or doneness as it relates to end of iteration or sprint deliverables. How we frame our teamwork goals, and measure their outcomes, plays an immense part in determining overall product quality and customer satisfaction. In this session, we will explore the 4 levels of doneness when it comes to agile release criteria:
- Team Craftsmanship Patterns
- Features – Complete
- Iteration – Complete
- Release – Ready
and share examples and stories of how doneness is a crucial constraint that drives healthy agile team behavior and high quality, high impact results.
Evolutionary Testing Practices in an Agile World
With the rapid pace of getting new product features to market in a digital age, users want their software capabilities and data to follow them wherever they go. From laptops on wifi to handheld devices on cellular, users expect their apps to work seamlessly as they roam from home to car and office. As a veteran consultant in the QA/Testing arena, I repeatedly see the following 3 factors that contribute to the inability to swiftly deliver high quality software that users demand: 1. Heavy reliance on labor-intensive manual testing 2. Redundant testing practices 3. Outdated processes and techniques With increased exposure to instant information from social media to blogs, companies are more vulnerable than ever and simply can’t afford software mistakes. How do agile teams strike the right balance of testing practices? This presentation will dive into each of these factors and discuss evolutionary QA and testing practices that can increase efficiencies without sacrificing quality.
Load it UP: Effectively Combining Performance and Functional Testing
Common industry software testing practices separate performance testing, functional test automation, and manual testing procedures. Typically, different teams with alternate skills and expertise perform their respective testing at staggered times with limited cross-team collaboration. Varied types of testing are often conducted in silos with different sets of defined goals. Rarely do we combine our efforts together in a meaningful way to achieve optimal, streamlined results. Doing these practices sequentially elongates the test schedule, actionable feedback loops and ultimately, time to market. By doing multiple practices in tandem, we can shorten testing cycle times and uncover potential defects sooner. Is it possible to verify performance test results for functional correctness or validate functional correctness under load concurrently? This presentation will explore three techniques to achieve optimal combinatorial test results: 1. Conceptual framework design patterns 2. Common modeling techniques for systems (functional and load) 3. Methodology for combining both aspects including tool usage