Browser archives - Quality Assurance and Project Management

Quality Assurance and Project Management:

browser

Nov 20 2009   10:00AM GMT

How your Web Application Performs on Various Browsers?



Posted by: Jaideep
Project Management, Software Project, web application, application performance, browser, web browser, software development, legacy software, developer, development team, tester, testing, software design, software requirement

You are in software development and in today’s world you can’t escape from most of your customer demanding either replacing their legacy software in use with new web application or the development of a new web application. Every customer wants to keep maximum leverage for its employees in terms of mobility, flexibility, easy usability etc. and that is why most applications in demand are web based.

Various stakeholders of the project get directly or indirectly activities assigned to them so as to make the project run and finish. The major role in web application development is that of development team. They should be very clear about the customer requirements – what browsers they want to use, what browsers they desire, what version of the browsers, future expectations etc. If these web based requirements are not crystal clear, it is going to create troubles not only for the developers and testers but for customer also. You can’t just dream and design, you have to have specific requirements in hand to develop an application.

Similarly Testers role is also quite prominent in validating customer’s browsers related requirements and ascertaining that all the browsers mentioned by customer (essential and desired) have to be checked for running the application completely.

This small issue can create a major backlog at a later stage. So it has to be handled right in the beginning before the start of development.

Jul 24 2009   10:00AM GMT

Four Environment Essentials to know before performing load testing



Posted by: Jaideep
load testing, testing, quality, software product, server, Test Server, production server, Staging Server, server configuration, n-tier, 2-tier, 3-tier, Software application, n-tier application, application, browser, browser version, architecture, performance, protocol

Which Server: Where is the load testing intended to be performed? Is it the test server, production server or staging server where load testing is to be performed? If it is being performed on Production Server, it is ok. Otherwise if it is to be performed on test or staging server, be careful that it is as near to production server in terms of configuration and setup as possible. It may give wrong projections if there is a wide gap in environment which is to be used in real versus the environment on which the test is performed.

How many Tiers: It is very important to understand how many tier application is, on which the load testing is to be performed. The n-tier count should include the client also.

What Browsers: Be very clear and specific on defining what all browsers are meant to be used for running this application (if this is a web application). The browser and its version is very important to conduct the load testing as each browser behavior, architecture and performance varies. Even between the different versions of the same browser.

What Protocols: Whether this is a client server application, web based application or n-tier application – identifying what protocols you are using to run the application is very important.