Presented by Christin Wiedemann, Co-CEO/Chief Scientist - October 2016
In this presentation recently delivered by Christin Wiedemann, Test-Driven Development is broken down from its history and premise to its different forms, such as Acceptance Test-Driven Development (ATDD) and Behavior-Driven Development (BDD). If you want to learn more about the advantages and challenges of TDD, contact us to schedule a presentation with your team!
Written by Marie Richardson, QA Manager - November 2016
QA Manager, Marie Richardson shares her User Acceptance Testing (UAT) checklist to help guide you and your team through your project’s UAT cycle.
Presented by Christin Wiedemann, Co-CEO/Chief Scientist - November 2015
Today’s software development projects are typically iterative, fast moving and subject to change. As testers in these environments, we are continuously faced with an overwhelming amount of information and data to take in, analyze and process in order to determine what testing approach to take. When time is tight, the pressure to make quick decision increases – how do we know that we are testing the right things, the right way, at the right time? How can we reduce decision-making time, without losing confidence in our decisions?
Presented by Christin Wiedemann, Co-CEO/Chief Scientist - November 2015
Is testing keeping up with the advances of software development? Are our approaches evolving as quickly as the new technologies, or are we being left behind, using the same methods and techniques as we did decades ago?
Testing needs to get more innovative! Scientific discovery relies on innovation; on scientists being willing to pursue new ideas even if it means having to learn new methods or technologies. Similarly, testers need to be creative and courageous, exploring new approaches and questioning old habits. Science is credible, curiosity-driven, critical, impartial and dynamic; science continuously challenges and questions methods, techniques and core beliefs. Shouldn’t testing do the same?
Presented by Christin Wiedemann, Co-CEO/Chief Scientist - October 2015
Deciding when to release a product to market means weighing the cost of a delay against the risk and consequences of an application failure. As illustrated by recent software failures experienced by a wide range of companies, inadequate testing not only puts your image and brand at risk, but it can also pose a threat to life and safety. Testing is a service to stakeholders, and testing can provide details on product risk, which is key to informed decision making. What information should you, as a project manager, ask your testers for, and how do you incorporate product risk assessment into your decision-making process?
Written by Sherry Heinze, Senior Test Consultant - April 2015
Sherry discusses what it is like to work on a team and work together to move forward. Sherry uses her past and present experiences to convey what a team is and how teams work together to maximize potential.
Written by Vijay Pallithekethil, Software Tester - March 2015
In a fast paced world where users want quick access to websites, how do we improve their experience and keep them coming back? The article provides thoughts on these very topics.
Written by Kevin McKay, Senior Software Tester/Delivery Manager - February 2015
Senior Software Tester Kevin McKay attended the Rapid Software Testing course and provides a review of the courses content and activities. If you are curious about the RST training offered by Satisfice, then this is the article for you.
Written by Sherry Heinze, Senior Test Consultant - January 2015
Innovation is the blood of IT. Can a tester or a team or a company visualize a situation differently and then act on the new vision? Can we be open to the changes it would take to do that?
Written by Christin Wiedemann, Regional VP/Chief Scientist - December 2014
Is testing really keeping up with the advances of software development? Are our testing approaches evolving as quickly as the new technologies, or are we being left behind, using the same methods and techniques as we did a decade ago? This article provides an approach for test planning which supports teamwork and innovation.
Presented by Christin Wiedemann, Regional VP/Chief Scientist - November 2014
From a software development perspective, the world seems to just keep spinning faster and faster, and in more and more intricate patterns. Is testing really keeping up with the advances of development? Are our testing approaches evolving as quickly as the new technologies, or is testing being left behind, using the same methods and techniques we were using a decade ago?
Written by Christin Wiedemann, Regional VP/Chief Scientist - November 2014
Are gamers predisposed to careers in software testing? The prevalent perception seems to be that testers enjoy playing games more than the general population, and that playing games makes us better testers by honing cognitive skills, which are especially important in our field. Can it be that people who enjoy games, riddles and puzzles are indeed better equipped to handle challenging software testing tasks?
Written by Derrick Collins, Software Tester - September 2014
One aspect of software testing is trying to find as many of the bugs in the software under test as possible and, in that sense, software testing can be viewed as a “Bug Hunt”. One testing style we often find ourselves using is scripted testing, which brings with it a certain kind of a “Bug Hunt” that is different than when using exploratory testing.
Written by Robin Price, Software Tester - September 2014
Three days dedicated to conferring with testers from all over the world, working in a wide variety of industry verticals and with every level of experience imaginable.
CAST is the Conference for the Association for Software Testing; a three-day conference held every August somewhere in North America. The theme this year was The Art and Science of Testing. If this conference or subject is of interest to you, please read Robin’s article.
Written by Stewart Kidd, Software Tester - August 2014
An example of a heuristic is “Consistent with the product’s history”, meaning the present version of the product is consistent with past versions of itself. Derived from the Greek “heuriskien” that means “find or discover”, heuristics are best suited for situations where the issues are not black or white, but occurring in the implicit areas that are somewhere in-between, and where there can be a definite lack of specifications. Using these heuristics, testers can see not only what is there, but also what might be missing.
Written by Michael Murphy, Software Tester - July 2014
In the past, projects were being rolled out in a year or even longer, now projects are being rolled out in shorter increments of time. So what is driving this trend and what does it mean for software testers?
Written by Don Spencer, President, IONA Software Solutions - June 2014
Losing your customers’ data is not only embarrassing, it can also be expensive. Both in terms of direct financial penalties and damage to the reputation of the business. Web Applications are risky and the developer must always expect the unexpected. The following article demonstrates what, where and how to prevent vulnerabilities.
Written by Ella Hoyt, Test Consultant - May 2014
Agile welcomes mutable requirements requiring adaption to changing circumstances. Watching and adapting to the ever-changing format and stories of Sesame Street conditioned those watching to embrace the ever changing Agile landscape. For further evidence on how Sesame Street influenced Agile Methodology, read Ella’s article.
Written by Brian Doyle, Delivery Manager - April 2014
Commercial Off-The-Shelf (COTS) software is pre-built software usually provided by a 3rd party vendor. COTS software is already commercially released and (we assume) vendor-tested, there is no need for the organization to test the COTS application; when testing is considered as part of a COTS implementation, the effort should be relatively lightweight and straightforward with few issues expected along the way, but this is not always the case. Both risk and cost need to be considered before testing a COTS solution.
Written by Mike Trites, Senior Test Consultant - March 2014
Good metrics are about more than just data. Used properly, they can be powerful communication tools that draw back the veil on testing and provide transparency to the process. Used improperly, they have the ability to send the wrong message to stakeholders and trigger false alarms or, even worse, to hide problem areas and give a false sense of confidence when things are not going well.
Presented by Christin Wiedemann, Regional VP/Chief Scientist - March 2014
Exploratory testing provides both flexibility and speed; characteristics that are vitally important with the quick pace of short Agile iterations. But how do you obtain traceability without losing creativity? How do you actually manage testing that is unscripted and at least partially improvised? A common misconception is that exploratory testing is by its very nature always unplanned, undocumented and un-measurable. One way to introduce more structure and documentation is to manage the testing as pre-defined, time-boxed sessions.
Written by Luiza Abaygar, Senior Tester - February 2014
So you ask, what is UX? It is a term for end-users’ overall satisfaction when interacting with a product or a system. UX has become one of the most defining factors for successful products, and it includes everything users see, hear or do and their emotional reactions. For most testers, usability testing comes to mind when UX is mentioned however, usability testing is only one aspect of a full spectrum of user experience. Why should testers care about UX? And why is it important to have UX knowledge?
Written by Keith McIntosh, CEO - January 2014
What actually makes someone a good tester? What qualities are we looking for, and how can we help testers grow those qualities? And can all the qualities we’re looking for actually be developed?
Presented by Keith McIntosh, CEO & Christin Wiedemann, Regional VP/Chief Scientist - January 2014
Creating a great test team is a lot like gardening: you need to find the right seeds, and make sure to plant them in an environment where they will thrive and grow. But what seeds do you look for, and how do you create the right conditions for them to develop into strong plants?
Written by Sherry Heinze, Senior Test Consultant - December 2013
I have gone from seeing myself as the Quality Police to seeing myself as a reporter. My job is to report what I see and what I don’t see. Sometimes, part of that is saying that we have not even looked at some areas, along with my assessment of how high a risk that creates. Sometimes, it involves arguing over testing scope with a project manager who does not want to look past the edge of our application or our change to see what the affect might be on another application and the company as a whole.
Written by Nathan Langton, Senior Software Tester - November 2013
In an age where many organizations are under pressure to accelerate their software delivery to customers, test automation is becoming a necessity. There are many reasons why it’s advantageous to implement a test automation solution as part of your testing strategy.
Written by Heidi Anderson, Software Tester - October 2013
Agile development methodologies focus on highly collaborative team environments that are continuously planning, developing, testing, integrating and delivering functional software. Agile team would be collocated to allow for face-to-face interactions between all team members, because this is historically thought to be the most efficient and effective method of conveying information. However, in today’s global marketplace, collocation is not always possible and this is the situation I have found myself in as a tester on an Agile team that spans two coasts and operates in three different time zones.
Presented by Christin Wiedemann, Regional VP/Chief Scientist - September 2013
Exploratory testing provides both flexibility and speed, characteristics that have become increasingly important with the quick pace of short agile iterations. But, how do you retain traceability in exploratory testing without losing your creativity? By using a combination of session-based test management (SBTM) and thread-based test management (TBTM) called xBTM. In session-based test management, exploratory testing is structured and documented in sessions. However, at times the work environment is too hectic or chaotic and requires the flexibility and freedom that is provided by thread-based test management. xBTM unites the two exploratory techniques to get the full advantage of both, from test planning to test reporting.
SQDG - http://www.sqdg.ca/
Saskatoon Testing Discussion Group - http://www.meetup.com/Saskatoon-Testing-Discussion-Group/
Quality Assurance Professionals - http://www.meetup.com/Quality-Assurance-Professionals/
TASSQ-Software Testing - http://www.meetup.com/TASSQ-Software-Testing-Meetup-www-toronto-assq-com/ or http://www.toronto-assq.com/
Kitchener Waterloo Software Quality Association - http://kwsqa.org/
nbQ Quality in New Brunswick - https://www.linkedin.com/grp/home?gid=4258253
* If you are having issues viewing these files, please download the latest version of Adobe Reader.