Thursday, July 28, 2011
In Selenium2.0 Remote Control is replaced by Web driver.This Web driver is very quick in test execution when compared to Selenium RC.
Major advantages with Web driver when compared to Selenium RC is
1.Selenium RC uses a Proxy through Java Script to launch a browser which usually takes some time,but coming to Web driver it supports some native apis for each web browser(Special api for each browser)so that web browser can be launched quickly using these apis.
2.The API of SeleniumRC is quite complex when compared to Web driver api.
Till now Webdriver supports only Java api.Drivers for all other langauges are still in development stage.
The Webdriver api will be available in the following link
Wednesday, July 27, 2011
For large or smalle Code of Applications it is Programmers job to test their code.Unit Testing one of the levels in Software Testing is purely for the developers.They have to write unit tests and they have to examine(test) their code.
A good unit test case is a small piece of code(mostly written in a single method)which is for testing specific functionality.In Large,complex well designed systems different objects have to work together to accomplish a particular task.
For example in order to write a simple test case to verify Login functionality user name and password has to be taken from database and using these as inputs test case has to be executed.
So if we are using database we have to create many objects(eg:Objects for Prepared statements,Result Set,DB Connection etc..).It is a complicated task to create some 'N' objects for testing simple unit test case.Creating these 'N' doesn't make our unit test to be completed in quick time.
Mock Objects are the Objects which Pretended to be as Real Objects makes this process easier.A mock object is a replacement for a real object that we create for the express purpose of testing. Mock objects were championed by Tim Mackinnon, Steve Freeman, and Philip Craig
There are Many Frameworks for effective usage of mock objectes in our unit tests like JMock,Mockito,EasyMock etc..
Tuesday, July 26, 2011
What is User Acceptance Testing?
User Acceptance Testing is often the final step before rolling out the application. Usually the end users who will be using the applications test the application before ‘accepting’ the application. This type of testing gives the end users the confidence that the application being delivered to them meets their requirements.
User Acceptance Testing – How to Test?
The user acceptance testing is usually a black box type of testing. In other words, the focus is on the functionality and the usability of the application rather than the technical aspects. It is generally assumed that the application would have already undergone Unit, Integration and System Level Testing.
However, it is useful if the User acceptance Testing is carried out in an environment that closely resembles the real world or production environment.
The steps taken for User Acceptance Testing typically involve one or more of the following:
.......1) User Acceptance Test (UAT) Planning
.......2) Designing UA Test Cases
.......3) Selecting a Team that would execute the (UAT) Test Cases
.......4) Executing Test Cases
.......5) Documenting the Defects found during UAT
.......6) Resolving the issues/Bug Fixing
.......7) Sign Off
What is Fitnesse?
FitNesse is a web server, a wiki, and an automated testing tool for software. It is based on Framework for Integrated Test (FIT). FitNesse is designed to support acceptance testing. Fitnesse allows users of a developed system to enter specially formatted input. This input is interpreted and tests are created automatically. These tests are then executed by the system and output is returned back to the user. The advantage of this approach is very fast feedback from users. The developer of the system to be tested needs to provide some support (classes named "fixtures").