In this episode of Whiteboard Friday, we address Behavior Driven Development, aka BDD. We'll talk about what BDD is and compare it to a traditional development process. Watch the full Whiteboard Friday series: http://bit.ly/2nxk6kV A traditional development process begins with a stakeholder determining what the business needs are for the product and dictate that to the product owner. The product owner then writes the requirements on his or her own, leaving out the developer and tester. Because they were absent during the requirement writing, the developer and tester must translate the requirement into what actually needs to happen; the developer translates requirements to code, the tester must translate requirements to test cases and technical writer translates into technical documentation. A BDD process begins with the product owner, tester and developer collaborating around the requirements, asking questions and providing examples of the business need. Agreed upon requirements are defined as English-formatted scenarios. In BDD, the developers can then use the scenarios for automated tests and testers also use scenarios as the basis for their tests. The byproduct behavior driven development means moving away from silos to a more collaborative process, resulting in a more complete final product that what a traditional process can deliver. #BDD in a tweet: “Using examples at multiple levels to create a shared understanding and surface uncertainty to deliver software that matters.” -Dan North @tastapod
Views: 46170 QASymphony
Learn more about specific continuous testing tools in this edition of the Whiteboard Friday series, "Winning at DevOps with Continuous Testing". View the full Whiteboard Friday series: http://bit.ly/2ov6VpR In this episode, you'll about which tools you need for continuous testing, including: a planning tool, a version control system, a build tool and a testing tool. The continuous testing tools stack starts with a planning tool, such as JIRA by Atlassian. This allows tracking of user stories, epics and tasks that drive the development, testing and release processes in one central location. Of course developers have their own IDEs, but the next tool needed is a version control system, such as GitHub, that allows developers to check their developed code into a central repository. This acts as the main source of truth and good VCSs integrated seamlessly with the build tool. The build tool, like Jenkins, is alerted that a new code version is checked in and will trigger and run any tests designed against the code. A test tools, such as qTest Pulse, picks up where the build tool leaves off. Certain circumstances, like new feature testing, call for additional testing against user stories or features that might not have been covered with regression automation. qTest Pulse and other test tools will then, in the case of a test failure, go all the way back to the version control system and alert the developer of the failure on the source code. The complete feedback loop between tester and developer is especially important for the developer’s full visibility into the status of the code being written. Once any issues are fixed and the testing passes, the test tool will then map back to the ALM tool to show the status and allow the product owner to move the feature to done in JIRA.
Views: 29177 QASymphony
In this video we are taking a look at the role of the tester within an agile software development life cycle. This should provide some good insight into the world of agile testing
Views: 70974 QASymphony
Accelerate Testing to Match the Speed of Agile Development qTest by QASymphony is the only platform that adds innovative exploratory to manual and automated test management, creating a complete solution that helps you test faster and keep up with today's rapid software development. http://www.qasymphony.com/
Views: 11866 QASymphony
In this video we continue our discussion around breaking down behavioral driven development “BDD” taking a close look at feature and scenarios along with choosing a framework that might work best for your team
Views: 7851 QASymphony
Structured Programming, Total Quality Management, Agile, Scrum, Devops—and after all this time, projects still stumble and products still drive us crazy. Why? Part of the reason is surely that many projects are flying blind, without sufficient awareness of the status of the product and the problems in it. And why is that? Part of the reason is that the craft of testing is stuck in ideas that we out of date 30 years ago, and are even more out of date today. Rapid Software Testing (RST) is an approach to software testing developed by James Bach and Michael Bolton. The approach is targeted towards the fastest, least expensive testing that still completely fulfills testing’s mission — to reveal the status of the product through critical thinking, exploration, and experimentation. While process models, artifacts, and tools have roles to play, RST puts the mindset and the skill set of the individual software tester at the center of testing work. Despite the name, Rapid Software Testing isn't just testing with a speed or sense of urgency; it's mission-focused testing that eliminates unnecessary work, tells the story of the product, and constantly asks what testing can do to help speed the project as a whole—no matter what the development model might be. Want to reframe your ways of thinking about the craft? Join Michael for a whirlwind tour through some of the principles and tactics of Rapid Software Testing.
Views: 4499 QASymphony
Machine Learning is all the rage. Companies like Google, Amazon, and Microsoft are investing extreme sums of money into their ML budgets. But what is it, and more importantly, how will it affect me, as a tester? Last year, Paul was at a testing conference where a group of 5 executives decreed adamantly that ML would replace testers within the next few years. Anytime 5 executives agree on anything he questions it. So he wanted to learn if they were right. Over the last few months, Paul has researched and learned about ML. He's talked with industry experts in the field and testers with expertise in ML. He wanted to know what they had to say about this decree. He wanted to know, "is testing in danger of being automated by ML?" Paul Merrill talks about what he's found in his research, provides an introduction to ML, and give info to decide for yourself if the future of testing will be in the hands of ML algorithms.
Views: 3779 QASymphony
While most teams appreciate the benefits of automation, it is commonly viewed as too time-consuming to be considered as part of an agile sprint; resulting in automation being done in isolation and typically months after the story has been closed. This can lead to several problems including automation team members being disengaged and missing key aspects of the requirements, as well as teams going through a period where new features are being introduced but no regression testing is occurring. Angie's talk provides agile-friendly approaches to automation which will allow teams to close their sprints with automation in place. These automation techniques allow scrum teams to work smarter, not harder, and find bugs quicker with a more narrowed scope of the root cause, essentially leading to quicker resolution times. We’ll also walk through an example story and demonstrate how to apply these techniques to ensure automation is achievable within the sprint.
Views: 1418 QASymphony
In today's White Board Friday you will learn about the four principles that exploratory testing is NOT: 1) Exploratory testing is something that’s not structured 2) Exploratory testing is the only form of testing 3) Exploratory testing is just throw away work 4) Exploratory testing is not for my industry
Views: 1746 QASymphony
qTest eXplorer has the ability to generate an automated test script for Selenium and Protractor frameworks, after your test session has been completed.
Views: 13105 QASymphony
In this video we continue with our theme “Metrics that Matter” – Ryan Yackel dives into quality metrics and the reports behind them. View the full Whiteboard Friday series on “Metrics that Matter in Software Testing”: http://bit.ly/2nzSADC Software quality metrics refer to the results of test executions, including metrics like the time it takes to execute tests and session data. These metrics may also include non-results type of reports such as exploratory testing that is focused less on the actual pass/fail results, but more on the overall user experience. Understanding software quality metrics usually begins with the three core reports: test run summary and defect priority/severity and status. The test run summary is integral to showing tests by cycle, project or release -- ideally by the functional area. Look at the latest test run execution results in this view. The defect report by status, severity and priority helps determine the importance of defects found to evaluate which bugs need to addressed immediately and triage the remaining defects for resolution. Extra software reports include executions by week/sprint, results received per requirement and defect density. Understanding test execution by week or sprint shows which days are active for testing and allows you to reallocate test resources based on those needs. Results per requirement reports show which percentage of testing is assigned to each requirement, helping you identify over and under testing of requirements and reassign test executions appropriately. And defect density shows the defects that make up an application or functional area to identify risky applications or functional areas. A couple pro tips for software quality metrics is to keep track of the number of manual versus automated tests, days since test execution run and flapping. Knowing the number of manual versus automated test allows you to help identify some manual tests that can be moved to automated execution, saving time, as well as understand which type of testing produces high value. Tracking the days since test run, on an individual-type basis means you can gauge which test you haven’t run in an extended period of time and reduce the library of tests that have not been run recently. Flapping reports show you which tests always pass under one set of conditions while always failing under another set. When this happens, look at whether the test case has changed and that it is written correctly or check if there’s a problem with the requirement.
Views: 22058 QASymphony
qTest for Jira Test Management is a free Jira add-on that connects the QASymphony's qTest with Jira software for agile test management. Once the add-on is installed with Jira Cloud, Server, or Data Center, a project administrator would integrate to qTest to track all manual, exploratory, and automated testing with Jira issues. This add-on allows agile testing teams to: - Visualize instance test run results for Jira issues - Submit Jira bugs directly from test run results in qTest - Synchronize Jira Fix versions and Sprints with test plans - Gain Enterprise visibility into QA progress related to Jira issue coverage *qTest Platform license is required for Jira integration.
Views: 1921 QASymphony
Today more and more companies are becoming agile, which means they are developing software at a rapid pace. However, software testing metrics haven't kept up with the speed of agile development processes. qTest Insights is a revolutionary business intelligence solution that provides real-time data about the health and quality of your application, allowing you to quickly identify and trouble shoot issues in real-time.
Views: 138033 QASymphony
Today’s White Board Friday video is part one of two for introducing exploratory into a teams overall testing strategy and highlights three main ways this can be accomplished.
Views: 1669 QASymphony
Customers always tell the same story of chaos, complexity, and frustration when it comes to using JIRA and HP Quality Center together.
Views: 4670 QASymphony
Learn how to Link Requirements to Test Cases in qTest by QASymphony
Views: 1315 QASymphony
Managing the balance between speed and quality is a difficult decision for many organizations. The adoption of DevOps has brought this more into the forefront as testers find their place in this emerging area. Adam discusses his experiences as a tester bringing quality into the DevOps process, with key strategies used to ensure quality is infused in every step of your process. View the presentation from Quality Jam 2017 here: https://www.qasymphony.com/blog/quality-jam-2017-presentations
Views: 599 QASymphony
The qTest integration with VersionOne systems provides a complete test management solution. Users can cover requirements, execute test cases, and determine testing outcomes by submitting defects to them. In short, users can perform test execution in qTest and manage test results in these systems simultaneously. Submits defects using a fully customizable submission form directly within qTest without the need to login to these systems Supports auto-filling to quickly transfer crucial testing data into the defects management of these systems, thus improves tracking quality of the testing progress The integrated defects will be attached to the executed test runs to provide a complete testing traceability to help improve your testing experience www.QASymphony.com
Views: 646 QASymphony
Learn how to create test run configurations in qTest by QASymphony.
Views: 1930 QASymphony
In Part 1 we discussed a few ways teams can begin to introduce exploratory testing into their overall testing strategy. In this video we’re continuing our discussion on incorporating exploratory testing into an overall testing strategy.
Views: 887 QASymphony
qTest Insights provides actionable, real-time test metrics across your entire software development life-cycle for team and executive level reporting.
Views: 916 QASymphony
qTest by QASymphony is the complete JIRA test management platform for JIRA - enabling you to plan, track, test and work smarter and faster than ever before.
Views: 1813 QASymphony
QASymphony qTest Insights Training video on: How to Create Custom Reports and Drill Down
Views: 272 QASymphony
Learn more about Quality Jam on the conference website: http://bit.ly/2lLg0sL
Views: 151 QASymphony
Learn how to create or clone a new project in qTest by QASymphony.
Views: 785 QASymphony
The qTest integration with Rally Software systems provides a complete test management solution. Users can cover requirements, execute test cases, and determine testing outcomes by submitting defects to them. In short, users can perform test execution in qTest and manage test results in these systems simultaneously. Submits defects using a fully customizable submission form directly within qTest without the need to login to these systems Supports auto-filling to quickly transfer crucial testing data into the defects management of these systems, thus improves tracking quality of the testing progress The integrated defects will be attached to the executed test runs to provide a complete testing traceability to help improve your testing experience www.QASymphony.com
Views: 524 QASymphony
QASymphony qTest Insights Training video on: How to Create Shared and Personal Dashboards
Views: 120 QASymphony
Key Learning Points: - How to visually define a test strategy & prioritize/communicate testing coverage (and identify gaps) - How to visually document key business workflows & features from existing manual tests for automation candidates - How to reinforce domain expertise and business concepts with distributed teams
Views: 1273 QASymphony