Cross Browser Testing... IETester

In this Testing World, Cross browser testing is so tedious and complex. We should download all the browsers and install in the system. Our smart customers will use different versions of browsers like IE6, 7, 8, 9 and IE10. We should take all the versions of the browsers as well. The reality of the cross browser is bit different. When running multiple versions of the same browser and inaccurate third-party testing tools mean we can spend hours just evaluating whether a testing set-up is anywhere near reliable.

Let’s begin with our old friend, Internet Explorer (IE). As most of us know, running multiple versions of the original Internet Explorer executable on the same system is very difficult due to issues ranging from run time version conflicts to operating-system incompatibility. In truth, I don’t think Microsoft ever considered a scenario in which developers needed a way to achieve this back when it was first conceiving IE 6, 7 and 8.

When I was Googling about those best third party application for the Cross browser Testing, I came across IETester. This will solve all the cross browser testing.

Here I have created Mind Map for IETester. I hope it will be useful for all.

Developers are also Good Testers

Some days ago I created ticket, which was not replicable; hence I closed as Cannot Reproduced. But the next day the same ticket was replicable. So I reopened the same ticket.

But I was unable to replicate that ticket to the concern developer. I was thinking where the mistake happens. I was in confusion. I had two tickets with me in such scenario. I have to close those two tickets as cannot reproduce. I know that’s issue. But I don’t know the exact steps to replicate those issues. But no other clue, I have close as cannot reproduce. L

I was planning to close those ticket, suddenly one developer came to me and told “don’t close those tickets, I have figure out the exact steps to replicate the issues”. Then he explains me the exact steps to replicate those two tickets.

Same situation I came across some two or three times.

Being developers, they know exactly where the application breaks. So sometime they know exact steps to replicate some issues

Bug is bug…

Some two days back I have raised an issue that “users are not receiving SMS for their mobile”

Developers analyzed everything and mentioned in the ticket, Users will not receive any SMS if they enabled DND in their SIM, and it will not applicable for India region. They closed that ticket as “won’t fix”.

After the Elevation to the customers, we got first ticket from the customer side as customer ticket.

After the ticket came from the customer, QA manager, Dev Manager spends whole day find reason for that issue. All the qa folks worked on the same. Finally they solved the problem and testers validated the same and work fine.

Lessons Learned from that ticket.

1.    A bug is bug, do not worry about region.

2.    Don’t think we should give importance to customer ticket, of course we should give

3.    Make sure that we should not get any bugs from customer side