Just another WordPress.com site

1. Decide What Test Cases to Automate
It is impossible to automate all testing, the first step to successful automation is to determine what test cases should be automated first

2. Select the Right Automated Testing Tool
Selecting an automated testing tool is essential for test automation. There are a lot of automated testing tools on the market, and it is important to choose the tool that best suits your overall
requirements.

3. Divide Your Automated Testing Efforts
Usually, the creation of different tests is based on the skill level of the QA engineers. It is important to identify the level of experience and skills for each of your team members and divide your automated testing efforts accordingly.

4. Create Good, Quality Test Data
Good test data is extremely useful for data-driven testing. The data that should be entered into input fields during an automated test is usually stored in an external file. This data might be read from a database or any other data source like text or XML files, Excel sheets, and database tables. A good automated testing tool actually understands the contents of the data files and iterates over the contents in the automated test. Using external data makes your automated tests reusable and easier to maintain. To add different testing scenarios, the data files can be easily extended with new data without needing to edit the actual automated test.

5. Create Automated Tests that are Resistant to Changes in the UI
Automated tests created with scripts or keyword tests are dependent on the application under test. The user interface of the application may change between builds, especially in the early stages. These changes may affect the test results, or your automated tests may no longer work with future versions of the application.

Advertisements

Sometimes, testing on various browsers becomes a challenge for software test professionals & project teams. Running the test cases on all browsers makes the testing cost very high. Specially, it becomes a challenge when we do not have expert designers in the team or when we don’t have verification/validation phase at the time of screen design. This is the bad part. Now, let’s see what is good.

browsers

The best thing is that there are many FREE as well as paid cross browser compatible testing tools available in the market. On top of it, you can do your job with most of the FREE tools. If you have very specific requirements, then you may need to have a paid cross browser compatible testing tool. Lets have quick look on some of the best tools:

1. IE Tab: This is one of my favourite & best tools available for free. This is basically an add-on of Firefox & Chrome. With a single mouse click from within Firefox & Chrome, you can see how the webpage will view in Internet Explorer. It is very light.

2. Microsoft Super Preview: This is a free tool offered by Microsoft. It can help you to check the webpage on various versions of Internet Explorer. you can use it to test and debug the issues in layout. You can download it for free from Microsoft website.

3. Spoon Browser Sandbox: You can use this testing tool to test the web application on almost all major browsers like Firefox, Chrome & Opera. Initially, it supports IE as well, but for the last few months, its support for IE has been reduced.

4. Browsershots: Using this free browser compatibility testing tool, you can test the application on any platform & browser combinations. So, it is most widely used tool. Due to large combination of browsers & platforms, it take long time to display results.

5. IE Tester: Using this tool, you can test the web pages on various versions of IE on various Windows platforms like Windows Vista, Windows 7 & XP.

6. BrowserCam: This is a paid browser compatibility online testing tool. It’s trial usage allows you to test for 24 hours only with the screen limit of 200.

7. Cross Browser Testing: This is a perfect tool for testing the website for JavaScript, Ajax and Flash features on various browsers. It offers 1 week free trial. It is available @ http://crossbrowsertesting.com/

8. Cloud Testing: If you want to test your application’s browser compatibility on various browsers like IE, Firefox, Chrome, Opera, then this tool is for you.

Apart from these tools, there are few other tools like IE NetRenderer, Browsera, Adobe Browser Lab etc. By investing some time on RnD on these tools, you can save your huge effort with excellent Quality.

Working with different stake holders in a project, teams would be facing difficulty in keeping transparency on bugs because of following common problems:

  • Lack of process for bug logging: Typical scenario like testing & development teams are not well educated on severities & priorities to be used and their importance.
  • No clear communication to testing team on required fields as part of bug logging. Testers may skip to mention required data like reproducible steps or may skip to attached screen shots.
  • Lack of a standard bug tracking / logging template. If all team members will follow their own template to describe defects, it may lead to discrepancy at a later stage.
  • Team will follow their own communication channel to communicate defects using phone/email. Sometimes they won’t even log defect after communicating issue to Dev and getting fix on the fly.
  • Team will not maintain appropriate statuses for defects. Even after they retest and close some times defect still shows as ‘Ready for Test’.
  • Improper Defect Triage/Communication Process: Triage process allows all stake holders to gather at one place (Physically or virtually) to discuss on all open defects and decide on action items. Without this call/meeting in regular intervals it will be difficult to have a common understanding on issues/defects or reasons for blocking of test execution.
  • Test team some time will not have control on Test environments and they would not know when the fix is deployed in to test environment. Sometimes Dev team adhocly performs certain actions on test environment and fixes the issue. Not having complete control on Test Environment would cause so many issues in ensuring quality of defect retest.

Tag Cloud