Often, when evaluating a potential new tool, it can be overwhelming and difficult to quantify which tool to select. The approach our team takes is to outline success criteria very clearly, to ease the evaluation and decision process.
We’ll use Eran’s selection criteria as an example.
Walk through needed capabilities (selection criteria) definition
Once you identify the needed capabilities, then you’ll want to identify the importance of each capability. As in, how critical is the capability to your decision? This will help you “weight” each capability which you’ll see is very important when making a decision later on.
Also useful when you have someone that wants to include criteria that you don’t think is as important (you just add it and give it a lower weight). Helps get away from “shiny penny” distractions.
Once you have identified the importance, then you’ll want to define your scoring key. This is how you will actually document whether or not the tool you are evaluating has met (or not met) your expectations for that particular capability. This can also be useful if you are asking multiple people to evaluate the tool and provide feedback. (I usually hide the weighting when asking others to evaluate the tool).
The scores are pretty close…
The final step is to put it all together and score the applications together. You’ll see we just do basic math to determine the final decision. Walk through the math and show the total that takes into account all aspects.
Note that it is always good to do a “reality check” to make sure the scores reflect overall needs (or even add additional capabilities discovered throughout the evaluation).
The Infrastructure as a freeway slide will go here…
Essentially, I’ll talk about what happens when other teams want to utilize a different tool than the one you “selected” and use my “Infrastructure as a Freeway” concept to describe the concept and how I handle that.
Here is the concept if you want more specifics: https://www.linkedin.com/pulse/software-infrastructure-freeway-bryan-osterkamp/
Cross browser testing
Strategy For Selecting the
Right Cross—Browser Testing
• Lead Technical Evangelist at Perfecto
• Blogger and Speaker
• 18+ Years in Development & Testing
• Author of The Digital Quality Handbook
Weekly Podcast - Testiumpod
Cross-Browser Testing != Desktop Web Testing
There is no Web Testing vs.
• 4 out of 10 transactions today take place on multiple
• 48% of users today complain that the websites they use are
not optimized for their smartphones and tablets
• Identify your object in a robust fashion that fits all digital
• Build object repository and use smart locators
Responsive Web Design (RWD) - Objects
The average website includes nearly 400
Now try locating them on each and every
DIGITAL platform in your lab…
• Take screenshot and use Visual Checkpoint/assertion to
validate responsive aspects
Responsive Web Design (RWD) – visual validation w/ Screenshots