36 days Of Web Testing

36 Days of Web Testing by Rob Lambert (The Social Tester)

36 Days of Web

Testing

By Rob Lambert

www.thesocialtester.co.uk

www.twitter.com/rob_lambert

36 Days of Web Testing by Rob Lambert (The Social Tester)

Welcome

Welcome to the “36 Days of Web Testing” eBook.

I originally posted this content out via my blog, as a series of 20 posts. I kept back 16 extra ideas for the

purposes of not boring people with too many posts. Here are all 36 in one book.

I actually had around 60 ideas but whittled them down to 36 to keep this book short and succinct.

It was amazing to get such a great response from the posts on my site. Thank you to all who commented,

emailed, tweeted, re-tweeted and otherwise shared the content around.

It was great to hear about people finding bugs after trying the techniques – the ultimate feedback for

those of us sharing hints and tips. It was also great to hear from people running startups or small teams

with no formal testing or testers; many found the posts very helpful in giving them ideas to test with.

This book is completely free and I would encourage you to share it with your friends and colleagues, but

please don’t change it and please try to reference the source when possible. (www.thesocialtester.co.uk)

The ideas in this book are not in depth, or technically informative but I do hope they give you a sense of

curiosity to explore the ideas further. They are starting points for your test ideas. Use them as you see fit

but never stop exploring your testing, your product and your skills. Exploration and development of

skills is at the heart of good testing. Enjoy.

36 Days of Web Testing by Rob Lambert (The Social Tester)

Welcome.....................................................................................................................................................2

Cross Browser .............................................................................................................................................5

Web Accessibility ......................................................................................................................................11

Is the HTML valid? .....................................................................................................................................14

Check for Dead-links..................................................................................................................................17

One, Two and many ..................................................................................................................................20

Multiple tabs and windows .......................................................................................................................23

Http and https...........................................................................................................................................26

Client and server watching ........................................................................................................................29

Browser Extensions...................................................................................................................................36

Back to the beginning again.......................................................................................................................42

Change the URL.........................................................................................................................................44

Automate the tedious ...............................................................................................................................47

Tab order ..................................................................................................................................................49

Soap Testing..............................................................................................................................................51

See the source...........................................................................................................................................54

Explore the competition............................................................................................................................57

Compliance and Claims..............................................................................................................................59

UX.............................................................................................................................................................61

Change the locale......................................................................................................................................64

Resize the windows and resolution............................................................................................................66

36 Days of Web Testing by Rob Lambert (The Social Tester)

Block pop-ups ...........................................................................................................................................68

Disable CSS................................................................................................................................................70

Text only ...................................................................................................................................................74

Disable java script .....................................................................................................................................76

Flash free ..................................................................................................................................................78

User Acceptance Testing............................................................................................................................81

Mobile friendly?........................................................................................................................................84

Race Conditions with Selenium..................................................................................................................87

Blink Testing..............................................................................................................................................90

Test in situ ................................................................................................................................................92

Print it out.................................................................................................................................................94

Too many extensions.................................................................................................................................95

Refresh during page loads .........................................................................................................................97

Check for SEO............................................................................................................................................99

Five second test ......................................................................................................................................101

Throttle It................................................................................................................................................104

36 Days of Web Testing by Rob Lambert (The Social Tester)

Cross Browser

Why?

There are a growing number of browsers entering the market (especially for tablet and mobile devices)

which means your website under test needs to be working well for your supported browsers.

The existing mainstream browsers (Internet Explorer, Firefox, Chrome, Opera, Safari) are also updating

themselves very frequently and often without the end user being aware of the update.

This makes testing against this growing number of browsers essential but also increasingly more time

consuming.

As with all testing though, ensure you check what is supported and what isn’t by your own

product/company. One of the most successful ways to reduce browser testing is to stop supporting older

browsers. This is a good strategy for some companies, but not possible for all.

It obviously doesn’t make these old browsers bug free but it does mean you can ignore potential

problems with these older versions and focus on the version you actively support.

How?

36 Days of Web Testing by Rob Lambert (The Social Tester)

Spread The Risk

One approach could be to run your everyday tests against a mixture of browser environments.

For example, you may be testing a simple web application where the user can log in, generate some

reports, send the reports and then log out. The system also has a simple “management” system where

sys admins or managers can view who is changing what.

To get a wider coverage you could test your log on functionality in one browser, test the send report

functionality in another browser and then the audit trail functionality using a third browser.

This is an effective way of covering different combinations of browsers at the same time as doing your

day-to-day testing. The above example won’t highlight a bug with the audit trail functionality in the first

and second browser though. So there are plenty of gaps for bugs to slip through, however the time it

saves may push your decision down this route.

Let someone else do it

For appearance issues there are many online tools like Browser Shots (http://browsershots.org/), which

will load your page in any of the supported browsers (they support a great many versions), take a screen

shot and then make these screen shots available to you.

This is great for websites, but applications that require credentials or have a huge number of pages are

somewhat more difficult.

36 Days of Web Testing by Rob Lambert (The Social Tester)

The Browser Shots homepage

36 Days of Web Testing by Rob Lambert (The Social Tester)

Check against standards

You could validate your site against an HTML standards checker. Checking against HTML will give you more

confidence the site works across many browsers, but there are still some browsers that will render pages

differently.

A good standards checker is at the W3.org (http://validator.w3.org/) page

Automate

You could automate your checking using something like Selenium (http://seleniumhq.org/) and then use a

tool like Selenium Grid (http://selenium-grid.seleniumhq.org/) to test against several browsers.

This has infrastructure requirements and is obviously reliant on an automation suite existing (or going to be

brought in to existence).

It will also only check what you have told it to check. Automated checks are great for functionality but will not

tell you about layout issues between browsers.

Fight Layout Bugs

You could write some automated tests to check the layout issues your site may face in different browsers.

Fighting Layout Bugs is an open source Java project providing an automated way of checking for potential

layout bugs. As it’s Open Source you can add to the project.

Fighting Layout Bugs – (http://code.google.com/p/fighting-layout-bugs/)

Manually Test It

You could manually test against each version by installing all of the versions on different machines. To make

this less of a chore it would be worthwhile using Virtual Machines.

36 Days of Web Testing by Rob Lambert (The Social Tester)

These can then be cloned and re-used by others, or centralized for multiple users to access. This too relies on

infrastructure. It also requires significant time and effort, but gives you the human analysis of cross browser

compliance.

Categorize

You could narrow the browsers down to engines.

Chrome and Safari use WebKit. Firefox uses Gecko. Internet Explorer uses the Trident rendering engine.

Opera uses the Presto rendering engine.

You could therefore “assume” that testing on Chrome will cover off Safari. This may be an assumption too far

for many though.

Emulate it

You could use tools that attempt to emulate the different browsers. There are a number of tools on the market,

as well as some inbuilt tools within the browsers themselves to render older versions.

A few words of caution though, they are not wholly accurate in my experience, but they *may* provide insights

that are useful.

Outsource Selenium

If you have a suite of Selenium tests but do not have the infrastructure or experience in house to get a grid up

and running then you might find services like Sauce Labs (http://saucelabs.com/) and Testing Bot

(http://testingbot.com/) quite useful.

I’ve not even touched on different operating systems or mobile devices but as you can see there are a number

of ways to approach the cross browser issues.

36 Days of Web Testing by Rob Lambert (The Social Tester)

Cross browser support may be your biggest pain-point, especially with the rapid rate of release that most of

the browser companies are now adopting.

In my experience a nice selection of a number of the above works well.

Useful Hint

Some browsers come with compatibility modes, which allow you to emulate different versions.

Some browsers, like Chrome, have developer tools for rendering pages in different browser and Operating

Systems.

Useful Links

Compatibility Mode page on Wikipedia - http://en.wikipedia.org/wiki/Compatibility_mode_(software)

Sauce Labs - http://saucelabs.com/

Testing Bot - http://testingbot.com/

Browsers and Rendering Engines - http://en.wikipedia.org/wiki/Web_browser_engine

Selenium Grid - http://selenium-grid.seleniumhq.org/

Thư viện tri thức trực tuyến

Nội dung xem thử

Mô tả chi tiết

Tài liệu tương tự (6)

36 kế cầu người & dùng người ( tam thập lục kế)

36 kế cầu người & dùng người ( tam thập lục kế)

36 sách lược dùng người / Kha Duy ; Kiến Văn, Trung Kiên biên dịch

36 kế nhân hòa

Kỹ năng thuyết trình (36 trang)

Tài liệu 36 kế nhân hòa ( Phần 3) pdf