Build new skills in specific areas through in-depth tutorials led by expert practitioners and industry experts. Available tutorials include:
Root Cause Analysis (RCA) is a very powerful process that can help any organization become more efficient and introduce potentially innovative ideas. Reporting project status alone is insufficient and additional information is needed to fully provide a true story as to how projects are affected by poor or broken processes. As QA groups become more involved in data collection and performing early analysis within IT projects, it is important that metrics and financial implications are identified and reported. These metrics along with a collaborative team culture can create an innovative environment focused on solutions to eliminate root causes of recurring process problems. The RCA process improves trust between all stakeholders by shifting the focus from individuals causing the issue to allowing individuals to have a voice in the solution. Join Jeremy and gain insight on how to become more business oriented in providing valuable data to your organization to drive improvement and innovation.
- Discover how performing root cause analysis can improve your QA group’s value to your organization
- Learn how to introducing cost/benefit analysis for continuous process improvement efforts
- Explore how to use root cause analysis to achieve collaboration with stakeholders
Test scripts have always been difficult to write. Do you have enough detail? Is there too much detail? What is the purpose of this script? These questions have bothered testing professionals for a long time. Over the past few years a solution has emerged that solves problems with writing test scripts. With the creation of the cucumber framework came the Gherkin Scripting format (also known as the Given-When-Then format). But its usefulness in writing test scripts is not limited to automation or agile projects. The structure of a Gherkin script is very straight-forward. Given provides you with the background. When tells you what is being created. Then tells you the expected results. Manual and automation testers, business owners and developers in every type of SDLC can benefit from Gherkin Scripts. During this workshop Matthew will walk through the process of crafting a well-written Gherkin Script from a traditional waterfall requirement. Then he will repeat the process using agile user stories and acceptance criteria. He’ll show you how a well crafted Gherkin Script can be a beautiful work of art.
- Learn the Gherkin Scripting syntax: Given-When-Then
- Write scripts in the language of the domain so all team members understand scripts
- Apply Gherkin Scripting to traditional requirements and agile user stories
Web performance optimization (WPO) is an emerging movement that focuses on trimming down the layers and speeding up the page download and display of web applications in the browser. In recent years, there has been a change in web application architecture where the bulk of the page load time and processing has shifted to the front-end (browser) due to emerging technologies and practices such as client-side scripting, Ajax, Web 2.0, etc. If mismanaged, this can lead to a bloated front end and sluggish performance. As more functionality moves to the browser and applications become more asynchronous, measuring client-side performance becomes an invaluable practice and a necessary precursor or parallel step to augment other performance testing alternatives offering a relatively faster feedback loop and faster ROI. Join Mais to:
- Discover web performance recommended practices, WPO patterns and anti-patterns
- Explore a set of front-end profiling tools & techniques
- Explore examples of front-end waterfalls and how to interpret, analyze, and identify performance offenders
The rapid pace of market driven changes today forces organizations to confront the traditional time versus cost versus quality conflict constantly. The Quality Management/Assurance/ Testing organization is under pressure to deliver low incident products in continuously shrinking development timelines. To succeed in the new marketplace, some enterprises need to establish world-leading quality assurance (QA) functions while others may need to implement small-scale change. Are you frustrated with how testing and quality is viewed within your organization? Do you feel that the expectations for performance from the testing organization are not aligned with reality? Do you wish you had the mechanism to affect change or maybe even transform your organization? Whether you desire small changes or a truly transformative organization, effecting change utilizes principles and methodologies that can be applied. Join Clyneice to get practical hands-on techniques for changing organizations.
- Prioritize opportunities for improvement
- Identify cultural barriers to change
- Map out a strategy for transformation
Every project manager needs an accurate estimate of testing effort, time, and cost. Providing this estimate is a challenge when there are many unknowns and variables. The problem is compounded when teams need to work with multiple system development lifecycle methodologies, all of which bring their own unique challenges. Carolyn defines an estimating procedure for your testing efforts and provides guidelines and templates that you can adapt to your projects in order to produce realistic estimates for testing activities for your projects. An approach to continuous improvement of the test estimating procedure and the estimates is included. This tutorial is for all quality assurance and quality control professions who are responsible for producing project estimates and defining estimating processes. Join Carolyn and get a better way of estimating the testing effort, time, and cost for your next project.
- Discover the necessary prerequisites for accurate estimating
- Determine which testing tasks require estimates
- Learn the guidelines and processes critical to producing accurate estimates
Test intensive development typically involves the application of numerous techniques such as test automation, exploratory testing, scripted testing, acceptance driven testing, and increased developer responsibility for the quality of their code. This tutorial will review the concepts of test intensive development and then focus on the key role exploratory testing plays in building high quality systems. It is the speaker’s belief that whether your team is using a waterfall process, Scrum, or any other form of iterative development, exploratory testing should be an important part of your test activities. In this tutorial we will define exploratory testing and show how it can be used even in highly regulated environments that require documentation of test activities. We will also explore the strengths and weaknesses of exploratory testing compared to other standard testing techniques. We will then further examine the impact of test intensive development on team structures, test policies and procedures, and the notion of risk driven testing.
Attendees will learn:
- Components and underlying philosophy of test intensive development
- How to use ROI thinking to guide the use of exploratory testing
- How to best plan and document exploratory testing
Finishing a product release is important; measuring your progress to get to the finish is critical. Metrics are essential to an organization to gauge and improve the team’s and their product’s performance. Initially we need to determine what Test Metrics exist and why they might be important to both the testers and the business. With the available list of metrics, the next question is to determine which metric will be both effective and efficient in the execution of testing and reporting to the stakeholders. Join Paul in this tutorial to build a metrics plan that will provide the information you need without impacting the efficiency of the testing process or the end result.
- Discover Test Metrics and why they are important
- Determine which metrics to use.
- Build a metrics plan
“Hey! We need to release this software in 2 weeks. Can you test it real quick?” Have you ever heard that before? In this tutorial, we will discuss strategies to add the most value with minimal times, documentation, and information. We will focus on how to really “get under the hood” of your application to both validate and verify that things are working as expected. Participants will learn strategies to implement critical manual and automated tests at the last minute.
- How to prioritize what to test under tight time (and information) constraints
- How to implement automated tests quickly that add value
- How to reverse engineer your tests into missing documentation
Many projects engage the business to assist with testing the solution. Most often the business is engaged to take part in UAT. However, depending on the project and resource constraints you may find business folks tasked with being the “testers” from start to finish throughout development. Involving the business aka the customer is an incredibly important part of increasing project success. However, the challenge is these folks are not really testers and what need from them isn’t really testing. In this workshop, Lynn McKee will share a new perspective on involving the business and driving towards product acceptance. The hands on exercises will challenge your thinking and provide you with strategies to apply on your projects.
- Understanding the importance of gathering product feedback vs. confirming if requirements have been met
- Sharing approaches to engaging the business in product testing without expecting them to turn into testers
- Learning strategies for influencing these changes change in your organization
As companies embrace more agile development and continue the trend to outsource software development projects, the impact on effective use of testers is significant. Impacts can be traced to testing methodology, practices, reporting, and last but not least the actual contract around which the services are obtained. Measurable outcomes and assessments are essential, and the development of appropriate testing outcomes requires forethought and planning. Clareice and Clyneice provide an overview of agile and outsourced testing today, basic contracting concepts, and tips on how to structure a performance-based agile test contract and for successful monitoring once the project is initiated.
- Explore basic contract concepts and what they mean for agile issues in an agile environment
- Learn how to develop outcomes that will lead to a better agile test contract
- Learn how to structure a performance/outcomes -based agile test contract that will improve monitoring efforts