Browsing articles in "Software Testiing"
Aug 6, 2012

Cross-Browser Testing

Lets discuss a type of compatibility testing which is known as cross-browser testing, which is mostly “forgotten and ignored” in many projects with web based applications, or even with organization’s internal applications but with multiple browsers installed in their environments.
Several reasons which makes cross-browser testing as “Forgotten and ignored” , because a project team ,
1. Only considered testing the application/website on the browser (s) of choice
2. Considered it, but don’t have the “time” to do cross-browser testing across all browsers
3. Tested in the latest versions of two browsers of choice
Browsers generally use different layout engines, as well as having differences in the way they present and handle code. It is for this reason, that unless you are in a severely locked down environment with one installed browser, and nobody in the world outside your organization needs to use whatever it is that you are developing, then you need to perform cross-browser testing.

Not everyone uses the same browser. Similar to how everyone is running on a different operating system, you can’t expect all people to be using the same web browsing tool.
So what are the options? The data about current browser share varies depending on the source and the region, but in general, Internet Explorer, Firefox, Chrome, Safari, and Opera make up most of the market share, with Internet Explorer dominating the market.When there are so many different options out there, each running their own rendering engine, how do you ensure that your web design or application will hold up in each of them?

You do not need to go to the point of ridiculous and test every version of every possible browser.
But if you are developing something which will be seen in world wide web, and you want to ensure that it does not break or contain high severity bugs that may actually cost you more money to fix than to test, then you need to test it on the latest versions of the most popular browsers.

Why the latest versions? Because in the real world, people do update their browsers automatically from the internet. This update is usually with minimal impact on their browsing experience.
If you are lucky enough to be developing something that can be reached *from* the internet, you could also make use of Browsershots to give you visual feedback on a wide range of browsers. Be aware that if you are testing with sensitive data, do not consider using that option.

Below goes some help available on the web for cross-browser testing.
Adobe Browser Lab

Adobe Browserlab offers an awesome solution for viewing on demand screenshots of your site. This is usually my go-to program for testing in various browsers.

Allows you to test the compatibility of your design with Mac OS X browsers.

The next time that you are on a Web application testing project, ask the question if it is not already discussed… “Are we testing on multiple browsers?”
And if you want to be noticed as a thinking tester, do ask, “Are we testing mobile phones? In which platforms? Android? Ios/iPhone? Do we have an interface optimised for mobile browsing?”
Sometimes, you will be amazed to hear that it has not been thought of yet.

I plan to discuss on testing your site in some web based mobile emulators in my next article

Aug 1, 2012

Arete TestLabs- Why?

Arete TestLabs ia an independent software testing company that prides itself on offering software testing services that matters to your business. By this we mean, we only recommend software testing that offers value to your business and your clients.

We make our most sincere efforts to understand your business and the software testing we recommend and perform reflects this.

At Arete TestLabs , We’ve grown in knowledge and understanding of what software testing means. We’ve studied software testing, software development and many other fields because we want to be the best software testers in India .

We want to share our testing ideas with you. We believe they will help you add value to your testing in a practical and visible way.

We are confident that you will like the testing we do, why not give us a call?

Jul 25, 2012


First, test what’s important. Focus on the core functionality—the parts that are critical or popular—before looking at the ‘nice to have’ features. Concentrate on the application’s capabilities in common usage situations before going on to unlikely situations. For example, if the application retrieves data and performance is important, test reasonable queries with a normal load on the server before going on to unlikely ones at peak usage times. It’s worth saying again: focus on what’s important. Good business requirements will tell you what’s important.

The value of software testing is that it goes far beyond testing the underlying code. It also examines the functional behavior of the application. Behavior is a function of the code, but it doesn’t always follow that if the behavior is “bad” then the code is bad. It’s entirely possible that the code is solid but the requirements were inaccurately or incompletely collected and c mmunicated. It’s entirely possible that the application can be doing exactly what we’re telling it to do but we’re not telling it to do the right thing. A comprehensive testing regime examines all components associated with the application. Even more, testing provides an opportunity to validate and verify things like the assumptions that went into the requirements, the appropriateness of the systems that the application is to run on, and the manuals and documentation that accompany the application. More likely though, unless your organization does true “software engineering” ,the focus will be on the functionality and reliability of application itself.

Testing can involve some or all of the following factors. The more, the better.
♦ Business requirements
♦ Functional design requirements
♦ Technical design requirements
♦ Regulatory requirements
♦ Programmer code
♦ Systems administration standards and restrictions
♦ Corporate standards
♦ ♦ Hardware configuration
♦ Language differences

Jul 24, 2012

The WHY ASPECT : Why Software Testing is essential?

Software testing answers the following questions that development testing and code reviews can’t.
♦ Does the software really work as expected?
♦ Does the software meet the users’ requirements?
♦ Do the users like it or is it user friendly?
♦ Is it what the users expect?
♦ Is it compatible with our other systems?
♦ How does the application perform?
♦ How does it scale when more users are added?
♦ Is the software ready for release to production?
♦ Which areas/modules of the software need more work?

What can we do with the answers to above questions?
♦ Save time and money by identifying defects early
♦ Avoid or reduce development downtime
♦ Provide better customer service by building a better application
♦ Know that we’ve met users’ requirements
♦ Build a list of desired modifications and enhancements for later versions
♦ Identify and catalog reusable modules and components
♦ Identify areas where programmers and developers need training

Jul 18, 2012

Functionality Testing

Functional testing is typically the base-line technique for designing test cases, for a number of reasons. Functional test case design should begin as part of the requirements specification process, and continue through each level of design and interface specification; it is the only test design technique
with such wide and early applicability. Moreover, functional testing is effective in finding some classes of fault that typically elude so-called “whitebox” or “glass-box” techniques of structural or fault-based testing. Functional testing techniques can be applied to any description of application behavior, from an informal partial description to a formal specification and at any level of granularity, from module to system testing. Finally, functional test cases are typically less expensive to design and execute than white-box tests.

Testing is aimed at verification and validation — that is, at finding any discrepancies
between what a software/application does and what it is intended to do —
one must obviously refer to requirements as expressed by users and specified by software engineers. A functional specification, i.e., a description of the expected behavior of the software, is the primary source of information for test case specification.

Functional testing, also known as black-box or specification-based testing, denotes techniques that derive test cases from functional specifications.Usually functional testing techniques produce test case specifications that identify classes of test cases and be instantiated to produce individual test

Functional testing can be applied at any level of granularity where some form of specification
is available, from overall system testing to individual units, although the level of
granularity and the type of software influence the choice of the specification styles and
notations, and consequently the functional testing techniques that can be used.

The core of functional test case design is partitioning the possible behaviors of the software into a finite number of classes that can reasonably expected to consistently be correct or incorrect. In practice, the test case designer often must also complete the job of formalizing the specification far
enough to serve as the basis for identifying classes of behaviors. An important side effect of test design is highlighting weaknesses and incompleteness of program specifications.Deriving functional test cases is an analytical process which decomposes
Specifications into test cases.


February 2018
« Mar