Manual Testing Q & A Part 6

Manual Testing Q & A Part 6

51.How can World Wide Web sites be tested?

Web sites are essentially client/server applications - with web servers and 'browser' clients. Consideration should be given to the interactions between html pages, TCP/IP communications, Internet connections, firewalls, applications that run in web pages (such as applets, javascript, plug-in applications), and applications that run on the server side (such as cgi scripts, database interfaces, logging applications, dynamic page generators, asp, etc.). Additionally, there are a wide variety of servers and browsers, various versions of each, small but sometimes significant differences between them, variations in connection speeds, rapidly changing technologies, and multiple standards and protocols. The end result is that testing for web sites can become a major ongoing effort. Other considerations might include:

·What are the expected loads on the server (e.g., number of hits per unit time?), and what kind of performance is required under such loads (such as web server response time, database query response times). What kinds of tools will be needed for performance testing (such as web load testing tools, other tools already in house that can be adapted, web robot downloading tools, etc.)?

·Who is the target audience? What kind of browsers will they be using? What kind of connection speeds will they by using? Are they intra- organization (thus with likely high connection speeds and similar browsers) or Internet-wide (thus with a wide variety of connection speeds and browser types)?

·What kind of performance is expected on the client side (e.g., how fast should pages appear, how fast should animations, applets, etc. load and run)?

·Will down time for server and content maintenance/upgrades be allowed? how much?

·What kinds of security (firewalls, encryptions, passwords, etc.) will be required and what is it expected to do? How can it be tested?

·How reliable are the site's Internet connections required to be? And how does that affect backup system or redundant connection requirements and testing?

·What processes will be required to manage updates to the web site's content, and what are the requirements for maintaining, tracking, and controlling page content, graphics, links, etc.?

·Which HTML specification will be adhered to? How strictly? What variations will be allowed for targeted browsers?

·Will there be any standards or requirements for page appearance and/or graphics throughout a site or parts of a site??

·How will internal and external links be validated and updated? how often?

·Can testing be done on the production system, or will a separate test system be required? How are browser caching, variations in browser option settings, dial-up connection variabilities, and real-world internet 'traffic congestion' problems to be accounted for in testing?

·How extensive or customized are the server logging and reporting requirements; are they considered an integral part of the system and do they require testing?

· How are cgi programs, applets, javascripts, ActiveX components, etc. to be maintained, tracked, controlled, and tested? site security information include the Usenet newsgroup 'comp.security.announce' and links concerning web site security Some usability guidelines to consider - these are subjective and may or may not apply to a given situation

·Pages should be 3-5 screens max unless content is tightly focused on a single topic. If larger, provide internal links within the page.

·The page layouts and design elements should be consistent throughout a site, so that it's clear to the user that they're still within a site.

·Pages should be as browser-independent as possible, or pages should be provided or generated based on the browser-type.

·All pages should have links external to the page; there should be no dead-end pages.

· The page owner, revision date, and a link to a contact person or organization should be included on each page.

52.How is testing affected by object-oriented designs?

Well-engineered object-oriented design can make it easier to trace from code to internal design to functional design to requirements. While there will be little affect on black box testing (where an understanding of the internal design of the application is unnecessary), white-box testing can be oriented to the application's objects. If the application was well-designed this can simplify test design.

53.What is Extreme Programming and what's it got to do with testing?

Extreme Programming (XP) is a software development approach for small teams on risk-prone projects with unstable requirements. It was created by Kent Beck who described the approach in his book 'Extreme Programming Explained .Testing ('extreme testing') is a core aspect of Extreme Programming. Programmers are expected to write unit and functional test code first - before the application is developed. Test code is under source control along with the rest of the code. Customers are expected to be an integral part of the project team and to help develope scenarios for acceptance/black box testing. Acceptance tests are preferably automated, and are modified and rerun for each of the frequent development iterations. QA and test personnel are also required to be an integral part of the project team. Detailed requirements documentation is not used, and frequent re-scheduling, re-estimating, and re-prioritizing is expected.

54.What are all the basic strategies for dealing with new code?

? Start with obvious and simple test

? Test each function sympathetically

? Test broadly before deeply

? Look for more powerful tests

? Expand your scope

? Do some freestyle exploratory testing

55.What is acceptance testing?

Its a formal testing conducted to determine whether a system satisfies its acceptance criteria -enables an end user to determine whether or not to accept the system

56.What is functionality testing?

Its a mandatory part in black box testing and is also known as requirement testing. During this testing testing team will validates the correctness of every functionality in terms of behavioral coverage,calculation coverage,input domain coverage and back end coverage.

57.What is GUI testing?

This testing is done against the windows compliance standards such as each windows present in the application,text boxes,options(radio buttons),check boxes,command buttons,drop down list boxes.

58.What is Retesting?

Testing of a particular test cases to check whether the bug is fixed or not.

59.What is the difference between functional testing and functionality testing?

Functional testing is a mandatory part in black box testing.

Functionality testing is also known as requirement testing,during this test testing validates the correctness of every functionality in terms of behavioural coverage,calculation coverage,input domain coverage,back end coverage

60.How to log defects in manual testing?

When you find a bug u have to post it in your company's issue tracker(as discovery or open status).While post the bug do not forget to mention the summary,description,build version,screen shot,step to reproduce,severity and reproducibility of the bug.

61.When to use regression testing and retesting?

Retesting:In retesting we are going to check whether the bug is fixed or not.

Regression: It means after getting conformation the bug is fixed,we are going to check the fixation is going to create any problems in the application or not.

62.What are all the main actions which will be taken by the project manager for testing a product?

1) Assess risks for the project as a whole

2) Assess the risk associated with the testing sub-project

3) Lay out criteria for important milestones and stick to them

4) Develop a project plan for the testing sub project

5) Track testing progress against the plan

63.What are all the important factors want to be trade-off when building a product?

1. Time to market

2. Cost to market

3. Reliability of delivered product

4. Feature set

64.What are all the favorite risks will be arised during the project plan?

? Are there fixed dates that must be met for milestones or components of the product?

? How likely is it that the test group will get the software on schedule?

? What technical areas of the product do the current members of the test group not understand?

? Which areas of the program must be well tested?

? Are there regulatory or legal requirements that the product must meet?

65.What is Guerilla testing?

It involves ad hoc testing done by some one who is skilled at finding errors on the fly. It is one person's best shot at finding bugs. This approach is typically time limited.

66.What is combinatorial testing?

The most comprehensive approach to testing program-input combinations is referred to as combinatorial testing. In this testing all possible combinations of the test data values selected for the program inputs are tested