Banking is increasingly a digital operation. Learn how the eggPlant range of test automation tools can address unique app testing needs in finance.
Learn about how application-level performance/load testing is an effective and simple answer to the challenges of testing complex retail websites. We’ll talk about how we used eggPlant Performance with application-level virtual users spread around the world.
Mobile device testing offers unique challenges from testing PCs, such as dealing with device fragmentation, testing of related back-end server components, performance timings, and network behavior. This page addresses the challenges of device fragmentation, end-to-end testing, performance testing, and network behavior, and how varying components of the eggPlant range can address these challenges.
eggPlant Performance can be used alone, and combined with eggPlant Functional, to address a wide variety of load testing situations. The suitability of eggPlant tools to a collection of common examples is described here.
Everyone wants their website to be accessible to as many people as possible. This means at least supporting four major desktop browsers (Chrome, Internet Explorer, Firefox, and Safari) each with several active versions. Cross browser testing is all about being able to test your website across all major browsers with almost the same effort as testing just one browser.
The eggPlant UX (user experience) helps you understand how your application will behave in the real world in the hands of real users. Most software products are now distributed systems, with components running across cloud, desktops, web browsers, and mobile devices. This distribution and diversity makes products much more difficult to test; but eggPlant UX addresses this through a combination of functional and performance testing.
Multi-user functional testing is executing multiple instances of a functional test at the same time, i.e. simulating a number of people using the system at the same time. The number of instances is small (e.g. 5) which is what differentiates this from load testing.
Localization is modifying an existing application for use in a specific geographical region. Typically this includes at least translating any text into the local language, changing currencies, and changing the date system; but it may include many other changes as well. Localization can be critical to selling your product in other regions, but it is can be very time consuming without the right tools support.
Acceptance Testing is testing done by a customer (rather than a product developer) to ensure that the product they are buying meets their requirements. For example, a financial services company would perform acceptance testing on a new trading platform, before they deploy it. From a technical perspective acceptance testing is similar to system testing, the difference it mainly in who is testing rather than what they are testing.
Data driven testing is a testing technique where a single test script is executed many, potentially thousands, of times with different data values. For example, a script to test a mobile banking application may be executed with 1,000 different valid and invalid sets of account information. Fundamentally, data driven testing allows you to cleanly separate the logic of your test script from the test data so that you can test lots of different data values without the script becoming complicated.
‘Embedded Systems’ has many definitions. Here we are talking about specialised computing systems often with non-standard platform software. For example, the National Air Traffic Services (NATS) use eggPlant to test their air traffic control systems. Embedded Systems often pose two key testing challenges. First, they use a lot of non-standard platform software. Second, no test software at all can be installed on the system-under-test (or modifications).