Firefox is a testers friend it really is. The extensions available are excellent and save a massive amount of time. Get Firefox from the right nav over there >>
Then add a few extensions to it >Tools>Add ons
These are must haves
Try the developer add on, its excellent, and lets you query all aspects of the page your testing. Also has a very handy overlay ruler tool for measuring page items.
Try the TAW add on, it's an accessibility extension that allows you to verify, with just a click, the accessibility of the Web sites that you are visiting, by means of the TAW3 online service (www.tawdis.net) and making use of the W3C Web Content Accessibility Guidelines (WCAG 1.0).
Try the HTML validator - never let a dodgy coded page out of your sight again.
Thursday, 1 March 2007
Testing and Design Matters
Brand stewardship is a big thing - it can make or break most web development agencies. Design QA is an essential part of the test job so make sure it's at the forefront of the testers thoughts at all time.
Designers PSD's are the key, once the client has signed them off, create a design bible from them so the tester has a reference point and get them set up with cool rule, juicy studio plug in for Firefox and a bunch of test beds with all the browsers your sites supporting.
Pixel matching the HTML to PSD's is time consuming but essential if what the client eventually sees is what they were expecting to see. It also keeps your designers on side and reinforces the QA teams position in the company as not just button pushers.
When your logging your bugs show them what the issue is, Gadwin do an excellent print screen tool just for the job.
Repeat the process once template to application integration has taken place as this usually breaks the designs - but you know if there are problems that they are integration issues and not the templates per se.
Finally get design reviews as explicit tasks in the project plan. The last thing you want is designers on launch date pulling the site apart because it doesn't match their vision.
Designers PSD's are the key, once the client has signed them off, create a design bible from them so the tester has a reference point and get them set up with cool rule, juicy studio plug in for Firefox and a bunch of test beds with all the browsers your sites supporting.
Pixel matching the HTML to PSD's is time consuming but essential if what the client eventually sees is what they were expecting to see. It also keeps your designers on side and reinforces the QA teams position in the company as not just button pushers.
When your logging your bugs show them what the issue is, Gadwin do an excellent print screen tool just for the job.
Repeat the process once template to application integration has taken place as this usually breaks the designs - but you know if there are problems that they are integration issues and not the templates per se.
Finally get design reviews as explicit tasks in the project plan. The last thing you want is designers on launch date pulling the site apart because it doesn't match their vision.
Subscribe to:
Posts (Atom)