Tag Archives: Internet Explorer

IE 7 and IE 8 Mess with Websites

I do not have words to describe the pain we went through with handling IE7 and IE8 on a recent release of a new website for one of our very important clients.

As always, we followed a very rigorous QA testing process and our QA team had signed off on the cross browser testing of the application, The QA team had tested the website on PC, MAC and mobile browsers. They had tested on Firefox (versions 2, 3 and 3.6), Internet Explorer (7 and 8), Opera, Safari and Chrome. This testing was done on different resolutions.

After taking care of all these variations, we confirmed to the clients that the website was fully ready to go live. The client also tested from a machine at home and said that everything was fine.

Then started the nightmare.

The client went to the office and tested again to realize that their entire left menu did not work. The best part is, it worked right on a few machines and did not work on a few. I tested on a IE7 machine and it was messed up, It worked fine on another IE8 machine.

As we continued our investigation, we found out that with IE7 and IE8, Microsoft has introduced a new feature called ‘Compabitibility View’. As per Microsoft’s explanations on Compatibility view, Compatibility view exists to accomodate those features that were used in older sites.

In addition, we noticed that Javascript was disabled by default in IE7 and IE8. It is very difficult to believe that Microsoft just decided to strengthen the security and make such huge change on Javascript related features. Many of the online users would not even know where to go to enable it.

This problem was solved by enabling compatibility view or by enabling javascript. We are still trying to find out the exact set of steps that happen when we enable compatibility view, so that we can try and see if we can programmatically enable it if required.

The best case scenario will be where we develop the sites, test it across standard browsers and it works without any exceptions. We do remember the nightmare we went through with IE6 testing and we felt better after taking the decision to discontinue support for IE6 and provide only on demand support for IE6 for the websites we develop.

Will provide an update after we investigate this further.

Horde Mail issue with Internet Explorer 8

We identified that there is some known issue in horde when it is used in Internet Explorer -8.0. When we browse horde in IE8, the left menu  panel doesn’t work and it keeps on refreshing the page when clicking on it.

We got this back to the cpanel team and here is there response.

“This is currently a known issue with IE8 and is not something limited to our server or software but with the Horde software itself. As it stands, I don’t have an ETA for the fix but I assure you it will be published as soon as one is available to us.”

Hope they will fix it soon.

We will update you here shortly.

Discontinuing IE6 Support in Website Development

Ever since IE6 was released, for all design related changes, our design team and the QA team had to take care of specific testing related to IE6. This was due to the fact that IE6 did not support many XHTML elements such as absolute positioning, etc.

In the past month or so, we have seen many leading sites remove support for IE6. It appears You Tube will also follow this step soon.
It goes without saying that all the leading sites have realized the pain caused by supporting the exceptions in IE6 and hence will be taking the decision to cease support for the same in the near future.

Continue reading

Microsoft IE browser security issue and workaround

Microsoft has acknowledged the presence of a serious issue called Video ActiveX Controls allowing Remote Code Execution. This is primarily on  the Internet Explorer browser running on XP and Windows 2003 machines.

They have also released an advisory update / patch on this topic which is available here.

At Auro Infotech, we chose an alternate strategy which has been working well for quite some time now. This solution is called Using Firefox with NoScript.

Those who feel it is necessary to use Internet Explorer, please remember to visit the Microsoft Support Site. Others, please try our recommended solution out and let us know if you think it does not work out for you for any reason.

QA Testing Process at Auro Infotech

This post is to discuss the QA Testing Process that is followed at Auro Infotech and generally recommended by us.  QA Testing Process is one of the key items involved in any web development process.

QA Testing Process is embedded closely into our Auro Project Development Life Cycle model and hence is dependent on a few important parameters.

Baseline Parameters:

During the discussion process with any client for a new website development (or enhancement) we ask our clients some important questions related to QA testing of their website.

1. Which Operating Systems would you like your site to be tested on?

2. browsers would you like the site to be tested on?

3. Which versions of browsers would you like the site to be tested on?

4. Which display resolutions would you like the site to be tested on?

We facilitate this question with a simple spreadsheet (will post a copy of it here shortly).

For a typical website, the recommendation from Auro Infotech is something like:

1. Operating Systems: Windows and Mac

2. Browsers: Internet Explorer, FireFox, Safari, Chrome

3. Versions: IE 6, IE 7, FF2, FF3

4. Resolutions: 1024 by 768, 1200 by 800, 1600 by 1200.

In the past we have seen clients ask us to test on some things outside the above recommended list (eg. Mobile devices, 800 by 600, etc).

This baselining helps us to start the project with a clear understanding of the client expectations and helps us to plan the development better.

Version Numbers:

Every project has a major and minor version number using which each project is labeled.

We use the following format: Project Name v <Major Version Number> . <Minor Version Number>

Examples are given below:

– Weavez v1.0 (We typically use 1.0 if this is a brand new website we are developing).

– Floretz v2.0 (We typically use 2.0 if we get a website that is already built by some other team and we are taking it over)

– Flair Tours v1.1 (If a client asks for a minor change to be done to a website, we increase only the minor version and not the major version.)

– Music Plugin v2.5 (If it is a change that is not minor but not large enough to be called major, we just create a version .5 from the current version).

The team at Auro Infotech gets a better idea of the type of changes going on in any project from the minor version number.

QA Testing Cycle:

Our development team typically develops the applications and does their part of testing (called developer testing) on one standard browser (typically the one that the client uses personally).

Once the development task is completed our QA Testing Cycle begins.

The Auro QA Testing Cycle is documented below:

1. The Project Leader initiates the QA Testing Cycle by requesting the QA team to test the website. This initiation is done by providing the requirements document, static screenshots and the link to the website on our testing server.

2. The QA team assigns a QA Lead for each website, responsible for the quality of the website.

3. The QA Lead studies the documents, screenshots and works with the testing website links. After this, the QA Lead plans for a meeting with the Project Team to get a demo of the website and get a full understanding of the system.

4. At this point the QA Lead prepares the QA Testing Specifications Document and gets it approved by the Project Leader.

5. The QA Lead tests the application and presents the results of the testing in Test Results Document to the Project Team.  This round of testing is called Build 1.

6. The Project Lead decides whether to accept a finding or reject it. The web development project team fixes the findings that are accepted and all findings rejected by the Project Lead are sent to the Project Manager for approval.  The Project Manager decides whether the rejected findings can be ignored, as they are accountable to the client on the quality of the final product.

7. Once the issues are fixed, the web development project team promotes the changes to testing server and submits Build 2 for QA testing.

8. This cycle continues until the QA team has signed off on all the test specifications (except the findings rejected by the PL and approved by the PM).

9. Once the QA team signs off the website on one browser, it is submitted to the client saying it is ready for User Acceptance Testing (UAT). At this point, the QA team continues to test the website on other browsers. This helps us to save time during the parallel testing.

10. Once the QA team signs off on the entire website, the website is officially ‘Out of QA’ and ‘into full UAT’.

This completes the QA Testing Process Cycle as defined at Auro Infotech.