Faraz's Blog

Microsoft is coming up with some serious gaming innovations.

I t's been a while that I used to do Arabic Calligraphy. Still trying to get better at it.

I wrote this swing application to do the RMI implementation for one of my grad-level course project assignments. The underlying architecture is based on RMI. Following is the use case diagram for the implementation. Use Case Diagram: Airline Reservation System Following is the package diagram of the project. The application was written in NetBeans 6.5. Package Diagram Class Diagram The following image shows the Airline Headquarters user interface view. The HQ can enter new airplane records or can view all records present in the database. The "connect to Server" button performs the Naming.Lookup to look for the bound remote interface object. Considering that the remote object is already bound to the  java.rmi.Naming . Once the instance of the remote object is obtained, all functionalities can be performed. Airline Headquarters UI View All Records UI The following images show the travel agent user interface view. A travel agent can search for a seat or can r...

1. SUPPORTED LANGUAGES: a. Mercury WinRunner: It makes use of its own C-like test script language. No other language support is provided. TSL is easy to use & very user friendly. b. TestComplete: It makes use of C++ Script, C# Script, Jscript, VBScript and DelphiScript. What I have found using TestComplete is that it is not user friendly in terms of coding. It requires significant effort to get used to the syntax of the scripting languages supported unlike Mercury WinRunner. 2. EASINESS: a. Mercury WinRunner: WinRunner is very easy to use because of its C-like syntax. b. TestComplete: User has to get familiarized with the syntax of scripting languages in order to use it. 3. FEATURE ENRICHMENT: a. Mercury WinRunner: Mercury WinRunner has relatively less features as compared to TestComplete, e.g. to test an application, it needs to be run through script. Moreover, the objects (buttons, labels etc) stored during the recording are mapped onto a GUI Map Editor and ne...

I conducted a comparison a little while ago for the following versions of the automation tools: • Mercury WinRunner 8.20 Build 8520 • QA Wizard 2007.0.0 Build 2358 1. SUPPORTED LANGUAGE: a. Mercury WinRunner: It makes use of its own C-like test script language known as TSL. No other language support is provided. TSL is easy to use & very user friendly. The scripts can either be recorded or manually written or a combination of both can be done. Scripting in TSL is quite similar to writing code in C language and is prone to syntactical errors. b. QA Wizard: QA Wizard makes use of its own proprietary scripting language. The language constructs are somewhat similar to Visual Basic. But, it still requires some effort to get used to the syntax of the scripting language. The scripts are viewable in text & grid views to provide experienced & novice programming experience, respectively. According to “Seapine’s WinRunner Comparison”, Users can ...

A very resourceful repository of APIs