Here at Cogniance, we have a bright team of automation and performance testers working together for 2.5 years on different projects. Average experience is 5+ years in target area per team player.

We work(ed) with the following software tools:

TestComplete, Quick Test Pro 9.2, Selenium, SilkTest for automation testing tasks and JMeter for performance testing.

TestComplete (licensed for us) and QTP (licensed for our customers) are our primary tools, while Selenium and SilkTest used specially for legacy projects and for comparison purposes. Below is the list of features of TestComplete:

• Script-free keyword testing for ease of use
• Scripted testing for total flexibility
• Windows and Web testing
• .NET, Java and Ajax support
• Flex, Flash, WPF and Silverlight support
• Internet Explorer 8 and Firefox 3 support
• Windows Mobile, Win CE, Smartphone support
• Windows NT, 2000, XP, Vista 32-bit and 64-bit support
• Open APIs,

which basically justified our choice of TC as a primary platform. As script language we use JavaScript.

QTP is mostly used for Flex application testing on costumer projects. Main advantages of QTP are:

• It has lots of plug-ins: such as ActiveX controls, Web Applications, VisualBasic, Microsoft .NET, Adobe Flex
• Keyword and Expert view modes
• Great object identification mechanism
• Centralization scripts running from the Quality Center

For performance testing tasks on all projects we use Jmeter, which is free and has following advantages:

• Complete portability and 100% Java purity
• Full Swing and lightweight component support
• Full multithreading framework allows concurrent sampling by many threads and simultaneous sampling of different functions by seperate thread groups
• Careful GUI design allows faster operation and more precise timings
• Caching and offline analysis/replaying of test results

Often we use remote script running (on the server where system is installed or in the same LAN area) to avoid connection latency issues and see real server performance and stress reduction ability.

JMeter has beanshell module, which allows writing java code that enables creating complicated projects (not only for regression testing) for different tasks and applications.

Regarding target platforms for web-automation tasks, we use IE7 and FF3 as the primary for automation testing, and manual scenarios for Mac and Chrome, if requested by costumer. Automation test development under Mac platform possible but not in strong demand for it yet.

Written by Sergey Lyakhov

First of all, it’s all about the application type – it can be native, cross-device, sms-powered, and a web application. Then, we need to consider carrier, handset manufacturer, model, OS and a browser. All these can give us the information about screen size (small vs. large), screen layout (portrait vs. landscape), input device (numeric keypad, QWERTY keypad, touch-screen), etc.

Here, at Cogniance, we experience each type of mobile applications testing, but the most exciting and bright experience was with Native applications development/testing. The application under test was Brew Mobile Client connected to the social network. It was developed for a predefined range of devices under Verizon Wireless carrier. I’m not going to describe the whole testing process and methodology, but the main bottlenecks were numerous certifications, signature files, application testing under a real network, using DeviceAnywhere Studio to cover required set of devices, and a lot of other extremely expensive procedures.

I would suggest moving towards the mobile Web applications. Think about it: If you’re creating a website, you don’t have to get permission from a carrier. You don’t have to get something certified by anyone. You don’t have to beg for being placed on the deck, and you don’t have to pay half your revenue to a reseller. In fact, the carriers, handset and OS vendors probably won’t even be aware of your existence. It will just be you and the user, communicating directly.

“The business of making native apps for mobile devices is dying, crushed by a fragmented market and restrictive business practices. The problems are so bad that the mobile web, despite its many technical drawbacks, is now a better way to deliver new functionality to mobiles. I think this will drive a rapid rise in mobile web development, largely replacing the mobile app business. This has huge implications for mobile operators, handset companies, developers, and users.” Michael Mace, a product planning and marketing executive in Silicon Valley.

Written by Alexey Koval

Last days, going through the web I found amazing resource with the huge  collection of interview questions for QA engineers and testers. Its located here

For about 75% those questions might satisfy seekers and interviewers.

Highly recommended.