Website qa
0 likes270 views
1. The document discusses various tools for testing, including Google URL shortener for analytics and QR codes, and Microsoft tags for categorizing documentation. 2. It provides tips for testing such as assuming bugs will be found ("quantum of bugs"), testing is structured sampling, and test coverage provides a robust product. Customers just want problems solved rather than how it's done. 3. Configuration matrices in Excel can track all browser and plugin permutations to test. Bug tracking needs real-time notifications, ease of use, and scalability. Cross-browser compatibility is important to test.
![• Creating a configuration matrix: Excel or the like to chart all the permutations you
will be testing on :
• which browsers (and versions thereof)
• plugins / addons: Flash, Silverlight, Shockwave, Sun Java, .NET
•Test cases: a simple sentence that represents the concept of testing one “atom”
based on:
INPUT > Transaction > OUTPUT [defined by an IF, THEN, ELSE statement]
More complex test cases factor in previous cases and their input and
cumulative effect. Can a shopping cart be too full?
6](https://image.slidesharecdn.com/websiteqa-120207122901-phpapp01/85/Website-qa-6-320.jpg)
Website qa
- 1. 1
- 2. Useful tools 1: Goo.gl shortener for: QR Code creation on the fly, basic analytics, consistent URL format. QR Codes and MS Tag: make it easy to classify / categorize documentation, make it easy for people watching an amazing presentation to collect links on the fly. 2
- 3. 3
- 4. • Quantum of Bugs – if we don’t start out searching for what doesn’t work we will never find it; if you test and don’t find any bugs that doesn’t mean they aren’t there, it may mean you need to review your testing strategy. • To infinity and beyond: so we test everything? Testing is structured sampling based on the tester having enough information to decide what can and can’t be tested in the time they have. What can be tested may be a misnomer: actually it is what needs testing. Good testing coverage provides a robust, scalable product .. We test products that sell and ensure a good user experience. 4
- 5. •The customer may have a personal preference for a technology they are familiar with but most people just want their problem solved they don’t necessarily want to know “how you are going to sweep the floor; they just want it clean”. •That said as testers we need to know the ins and outs of setup, configuration and use of the technology if it’s a simple widget, a 3rd party add-on, a browser plugin or a Content Management System. •When scheduling in Israel do u plan for: – •The Expected: e.g. release dates 2 days before the chagim, Apple announcing a new version of iOS/iPad/iPhone •The Unexpected Expected: e.g. Engagements, Weddings, Births, Miluim •The Unexpected: e.g. changes in customer requirements, power outages ... •And if so do you a. Buffer the whole project b. Create unrealistic release dates c. Run short interim workable releases (iterations) or d. Ask the people actually doing the work how long it will take them to get it done? •Real world bugs that mess us up: changes in Daylight saving and sync-able mobile devices... My nice MS story. •Test documentation: collaborative, backed up, track changes/ approval; send links over mail not the doc itself. •Heavy, very descriptive documentation including spec used to be the trend .. Does this require heavier maintenance. •What if there are no written requirements, no spec, no user cases? 5
- 6. • Creating a configuration matrix: Excel or the like to chart all the permutations you will be testing on : • which browsers (and versions thereof) • plugins / addons: Flash, Silverlight, Shockwave, Sun Java, .NET •Test cases: a simple sentence that represents the concept of testing one “atom” based on: INPUT > Transaction > OUTPUT [defined by an IF, THEN, ELSE statement] More complex test cases factor in previous cases and their input and cumulative effect. Can a shopping cart be too full? 6
- 7. • Filehippo is a safe repository for latest installs, an update manager for your PC and a repository for all old versions of the same apps / addons. • Examples: Flash, Shockwave, Sun Java, .NET, CCleaner (refer later or demonstrate) ... Example: Flex testing – Sun Java old version update with Flash. • Physical versus virtual test environments: •When is it good to use •When not? •Getting outside your LAN ... Using WiFi – replicate real world users. 7
- 8. Bug tracking needs to be: • Real-time notification – the more severe the bug, the more critical the Dev / PM are made aware of it and it’s impact (e.g. CDs and “read this way up” story) • Easy to manage, easy to input, easy to search • Scalable ALM like Microsoft Team System are a one-stop shop for your project but they aren’t free. Bug reporting should be objective, non-critical of the developer’s work and a means to identify and fix the issue Reproducing – add-ons for browsers and additional applications like Selenium Macro Recorder at the low end or MS Test Pro Manager allow for easy reproduce of what the tester saw. MS TPM links to the relevant code behind the event and the test case / defect. Windows Mobile has an equivalent application MyMobiler Selenium is more than just a macro recorder as it supports tests runs in most browsers and some limited mobile app testing. Conventionally, QA sets the Severity of a bug discovered and Product / Project Managers are responsible for Priority. 8
- 9. BuiltWith is a nice site that you input the URL of your site and it comes back with a comprehensive report of the technologies used in that site (Israel21c – Diskus IE crash example) IE9 Developer Tools (analogous to Opera Dragonfly or Chrome’s Inspect) one of the nice things in IE9 is the Tools are the W3C validators of which there is a Mobile Test Tool now. -------------------------------------------- Types of testing – functional, GUI, UX, regression, scalability / performance, security / pen. Testing Ad Hoc testing is okay if scheduling is tight and you are the person testing and fixing but the best tool can be post-its / a pad and pencil Don’t let things fall between the cracks ... If u suspect a bug investigate / note down for follow up but think “how much time will this take” what is the potential impact versus not completing my planned tests. Sometimes writing can be a pain .. Use an MP3/ video recorder and webcam/ mike and review later. 9
- 10. • Cross browser compatibility testing can be a painful process and knowing how Murphy’s Law plays a role the one configuration or browser you don’t test inevitably will be the one your site cannot render in. • The tester should exercise caution in solely relying on web based applications that merely preview the site (e.g. Malware block in Chrome) 10
- 11. Flash – the known bug, who hates it .. Where does it really stand versus HTML5? Flash and Silverlight don’t store cookies where cleaning the browser cache will remove them .... Flash and Sun Java (old versions): testing Flex apps and reporting bugs as known issues. Cookies – starting from clean or not? Chrome’s false positive response to tracking cookies and my example .. Oops? Facebook and SSL / HTTPS for Apps – is this really ready for primetime? Facebook’s solution down the line: impact, workarounds? SSL Certificates. PHP sites including Facebook, Drupal etc on different browsers. 11
- 12. 12