- Featured in a Magazine
- Most Wanted Bounty Winner
- Sold between 100 000 and 250 000 dollars
- Repeatedly Helped protect Envato Marketplaces against copyright violations
- Has been a member for 3-4 years
- Referred between 10 and 49 users
- Bought between 10 and 49 items
- Exclusive Author
themewaves saidThe viewpoint is not always accurate. I remember a case when i was arguing with a client because he said that something was broke in IE8 while i was clearly seeing that it worked in IE9 compatibility mode – IE8. When i viewed in an actual IE8, it was broken..
Any IE9 version there has Developer tools and that’s changing Viewpoint to IE8 and IE7 that’s really helped me lot and there has inspector too. I have used many different tools before. Now i’m using if i check the IE then i will always use this.
This has happened to me as well, IE9 with ie8 browser mode enabled displaying no issues, however when i installed ie8 into another machine, i could clearly see the issue.
Result, i’m not relying on ie9 developer tools anymore.
ChapterThemes saidYES, but testing with different physical devices is always very humbling experience with all kinds of strange issues showing: slow or choppy animation on older hardware, colors looking different on non hi grade graphic displays, fonts missing, patches/updates for IE not applied, links too small to click on some phones etc etc …
@ZxxxZ nice explanation. I just need the ability to check different IE browsers. Now i can but on different machines. And i’m not planning to always have like 3 machines available for IE testing.
I’ve never seen that modern.ie website. So i can get images for use with virtual box just like that? And test the different browsers?
Yes, similar images were once available on microsoft.com page and required some more magic to work in Linux, now Microsoft is trying even harder to make it easier to people to test compatibility. Backward compatibility was always a big thing for them, which ironically is partially responsible for all the headache IE is giving us now… introduce one bug back in IE5, now you need to carry it forward or people will blame YOU for breaking their broken page.Once there was a Linux LiveCD (so no installation required!) that contained number of exotic browsers, emulators and scripts to install IE – so you only would ever needed (in theory…) to run only it for testing, But the last release is 2 years old http://susestudio.com/a/ppX0Yr/browserbox .
Touch events etc. i think does need to be tested on devices like the ipad itself.
Now what you really need is automation. See: 10 browsers * 15 pages * 7 resolutions * 3 pixel densities * 2 orientations * 3 operating systems * huge number of feature like touch * some content variations (with images/without/short text/long text/no text/...) = a lot of testing
Of course final testing should be done by humans (preferably more than one human) but some testing needs to be done along the development. Some people say: just build it in chrome and add ‘rest’ at the end – this is good solution, but sometimes can result in unexpectedly long time spend in fixing issues with other browsers (not only IE) at the “end” of development.
Personally I’m in favor of splitting design into semi-independent aspects like: base typography, layout (including breakpoints), “theme” (colors, fonts, shadows, gradients and textures…), and components (menu, footer, sidebar, comments, etc…) – and trying to find issues as soon as possible at each step. Some CSS methodologies like SMACSS may be of help here.
I’ve heard some people utilize lot of automation with tools like Selenium – so tests run without human interaction, there are automatic lint-like tools to spot some cross-browser issues, http://csste.st/tools/ lists some of them – I was very impressed by this http://www.youtube.com/watch?v=WY3C6FHqSqQ (go to 21 minute and watch for 5 minutes).
But I’m yet to incorporate all of that into my workflow – time savings may be huge but so is initial investment:( There was also some service that records you testing your web page and “reruns” it in several browsers looking for glitches, but I’ve forgot the name:(
Testing being hard and time consuming is partially the reason why people are turning to prebuild components and frameworks.
Would love to read how others are testing things!
Anyone knows how Envato reviewers are dealing with it? With so many themes around they need to have some nice testing automation…
Don’t know how the reviewers test it.
Just tested with visualbox and a VM from the site, works perfect.
I don’t need such an extensive testing as you describe. I almost ‘never’ have any issues with my styling etc. Sometimes little things and those i can pick out easily now.
As for performance and colors etc., that’s something i don’t worry about. I’m not going test some tool or script on an too old machine etc. You want to use webapps or tools, get a modern computer/browser. Also most people who do use such things have a desent system already so no big deal there.
It’s mainly just about the proper styling for me. The rest always works
I like to test with the browser manually, using recent versions, but that can take a while.
Adobe Browser Lab is a good resource, but it can be VERY slow.
Anyone checked out browserling? www.browserling.com