December 6th, as the sponsorship role, Perficient China GDC held the Agile Tour 2014 HangZhou Stop successfully. 106 Agile fans gathered in 6F of ShuiYou Building from 8:30 AM to 17:00 PM and enjoyed an one day Agile Tour. Read the rest of this post »
Our objective is to find a testing tool to automate the testing for EXTJS applications. A high level enterprise application based on EXTJS will have multiple UI controls floating around. The controls will have mostly dynamic values fetched from backend. Each UI control might take to many level of child pages and popup windows.
Let us take some sample scenario to consider for automation. A login page that will take to a base page. The base page will have some set of buttons and clicking on each button will lead to its feature pages. From the feature page, there can be many child pages and pop-up windows.
The automate Testing tool
After browsing through forums, we took the following testing tools for comparison: RIA Test and Test Complete.
Tool1: RIA Test
RIA Test tool is cross browser testing tool from Cogitek mainly specified for UI applications. It’s been mentioned that RIA Test recognizes EXTJS components. These were the pros and cons about the tool obtained from forum and its release notes. RIA Test tool can be downloaded from here.
Tool2: Test Complete
Test Complete tool is from Smartbear. Smartbear offers a range of testing tool and test complete web module is for testing web applications. Pros and cons of the tool obtained from forum and site are as below. Test Complete can be downloaded from here.
Here is the comparison done on both the tools with respect to test creation/ tool installation.
|Setup Installation||Can download and install trail pack any number of times||
Can download and install trail pack only once after which we could not install trail pack again
|Creation of Tests||A project to be created with specified browser and test cases comes under the project||
A project suite can have many projects. Test scripts comes under project
|Debugger, Watch Windows, Results window||Available||Available|
|Handing browsers||Need to manually install browser patches||Mostly installed with software installation. Patches for browser upgrade after installation need to be manually added|
|Test case recordable with images or videos||Yes||Yes|
|Looping a test in all supported browsers||A browser is specified for a project. Either multiple projects or manually change the browser after each execution||Browser loop is available for each test|
|Asynchronous testing||No||Supported as mentioned here|
Here is the comparison on same tools in creating solution to our problem statement.
|Test case in IE and Firefox||RIA Test||Test Complete|
|Logging in and Launching base page||Supported in both browsers||Supported in both browsers|
|Button click and leading to feature page from base page||Supported in both browsers||Supported in both browsers|
|Buttons and components recognition in feature pages and its child pages||Recognized in Firefox , not in IE||Recognized in both browsers|
|Native HTML 5 components recognition||Not supported||Recognized|
|Manual scripts||Supported with its own scripting language||Supported with scripting languages which resembles VB, JAVA etc.|
|Performance Testing||No||Supported along with another tool of smart bear. Fully not available in trail pack|
|Documentation||Not much||Well maintained documentation|
|UI Objects Properties Inspection||No||Yes|
Testing on pages which takes more time to load like applet
|Script abruptly stopped and only after restarted RIA Test, the tool worked further||Once timeout the playback stops and logs the error and shows the result page|
Why we pick Test Complete
Our application uses EXTJS as front end and the components are populated dynamically. We need object properties to be changed dynamically from scripts. Our application includes applets, so sometimes page response used to be slow. As testing resources spreads on onsite and offshore, in future distributed testing might be required. Test Complete meets all our expectations and we chose the same for our automated testing.
There are various tools available to test web services. Some of them are Soap UI, Soap UI Pro, Test Maker, Web Inject etc. The most common tool we use is Soap UI.
Soap-UI Pro (the licensed version) has come up with a user friendly UI. It gives utility to create the test data (to read/write from external files) step, create a data connection (to read/write from database tables) step and property Transfer (to transfer property between steps) step. It also provides a utility called Groovy script to achieve any validations/operations not possible with default SOAP UI steps.
In the last project, I was assigned to build and configure the search center. Thanks to teammates’ help and googling, I’ve get more and more familiar with search center.
When you want to query from one certain type of content, using result source is one of your good choices. In this blog I will demonstrate how to create a result source. Read the rest of this post »
Several days ago when I ran a PowerCenter session, I encountered an issue of populating column value of money data type from one Microsoft SQL Server table to another. For example, the original source value is 1234.1250, but after I loaded it to another table, it became 1234.1136.
In Informatica, the column data type is set to money in source and target table definition. And we set it to decimal (19, 4) in middle transformations because there is no money data type in transformation.
Solution: Read the rest of this post »
In the star-schema based data modeling, it is not very often to turn on slowly change dimension as type 2, while it will bring some advantage to feed some requirements such as ‘show me the history change for one business group folks’, ‘show me the revenue and cost incurred by the employees at point of time’, etc. All of these require tracking records for the persons. While in this short post I would like to share another type of requirement which is built upon SCD type 2 and my approach of how to resolve the issues – it may not be perfect but will give the OBIEE developers a quick way to GO. Read the rest of this post »
In this blog, I will introduce the defect triage processes that I previously defined and show how it can be tailored for similar, future projects.
I joined an integration project to lead and do integration testing after I already did functional testing for the client’s four projects, which were all related to the integration project. I thought it would be easy for me to tackle the integration testing because I have already done testing for these individual projects, and I knew the requirements and business rules quite well. I also have already communicated with the project managers and team members of the APP projects during functional testing.
However, when integration testing started for a while, I found the most challenging work was not about finding a valid defect quickly. Read the rest of this post »
What is a Mobile Simulator?
A mobile simulator is a software application for a personal computer that creates a virtual machine version of a mobile device, such as an iPhone, or other smart phone, on the computer.1 The mobile simulator allows the user to use features and run applications on the virtual mobile on their computer as though it was the actual mobile device. A simulator can be simply termed as a model for analysis. But in the case of an emulator, it can be used on the basis or particle-oriented purpose, or it can be substitution in case of the original device purpose. It is there to give you an idea about how something works.
We want to create a target flat file name with the current system date.
The following command will rename the file in the format filename_MMDDYYYY.out on Windows:
move $PMTargetFileDir\filename $PMTargetFileDir\filename_%date:~4,2%%date:~7,2%%date:~10%.out
“The best architectures, requirements, and designs emerge from self-organizing teams.”
– One of the agile principles.
Whenever I see an offshore delivery project where the architect is super busy on implementing/coding a particular feature and has little time to communicate with the development team, most likely the project is running into trouble… So, what should architect do in offshore delivery project?
The Architect should act as bridge between the customer and development team
Due to the time zone differences between the offshore team and customers, the onshore architect is naturally responsible for working directly with customer (and business analyst) to define functional and non-functional requirements, including identifying and resolving conflicting requirements.
On the other hand, architect should also work with the offshore development team to ensure that the requirements and the high level design are fully understood by the team. During the development, offshore team usually will ask requirement questions. Architect should be responsible for answering those questions in time.