The webinar has finished, but you can watch a replay of the recording.
During the webinar we showed a bunch of videos and our notes for the sessions.
We will link to, or include, all those resources here.
OutlineWe added a 'stealth mode' to our Newsletter signup on the front page of our website. We debriefed on the testing we did to share our thoughts and ideas.
Consider how you would test http://blackopstesting.com/
Identify the context * Scope (what features, content and types of testing are in and out of scope?) * Time (how long have I got?) * Risk (what really matters?) * Rationale (why are we testing, and who for?)
Testing initial ideas * Input constraint and data validation * Mandatory fields * Email address format enforced? * Is there a maxlength? * Client-side or server-side validation? * Can we enter multiple email addresses with delimiters? * Already-registered email address * Whitespace * Leading and trailing whitespace. * Accessibility
Testing * Input constraint and data validation * Mandatory? Yes, there is an error message if it no email address is entered. * All validation is done server-side. * Email address format enforced? Yes, but not correctly. * BUG - [email protected] is accepted (domains must be at least 2 characters) * INTERESTING - there is a banned list e.g. [email protected]
http://blackopstesting.com/ *Bug*: The email address input field has white text on a white background so you can't see the text you enter as you enter it. *Better? bug*: css styling makes the text white on a white background in the email address input field so you can't see the text you enter as you type it. *Automation* - functional automation tests would work fine on this, because they don't need to see, they just find the field, type it in, and good to go. Unless it is an image based tool. In which case they might fail. *Workarounds*: 1. click on field and ctrl+a to select the text and see it, before you type a range of letters - use memory to fill it in 2. Just click subscribe and the 'alternative' error checked input form comes up 3. Inspect element and amend the css 1. stop the color from inheriting (chrome, firefox) 2. change the color on the blackops header 4. I can look at the css itself - a wrong id has been used on the div (in stealth mode - this is the 'real' bug so I could amend the id to 'mc_embed_signup' 1. I can edit the CSS in the Sources, and work 1. I could edit and save the CSS locally then put an autoresponder in the proxy to pull the local file Scope of testing? Scope of testing - do we want to test mailchimp? or the input form
Coming Soon - james created a couple of videos - we haven’t uploaded those yet
James supplied his notes as a pdf, which you can download here