Software Testing Interview question

In which Software Life cycle phase does testing occur?
Can you explain PDCA cycle and where does testing fit?
What is the difference between white box, black box and gray box
testing?
Define Defect?
What is the difference between Defect and Failure?
What are the broader categories of defects?
What is the difference between Verification and Validation?
How does testing affect risk?
Does Increase in testing always mean good to the project?
As a manager what process did you adopt to define testing policy?
Should testing be only after build and execution?
Are number of defects more in design phase or coding phase?
What kind of inputs do we need from the end user to start proper
testing?
What is the difference between Latent and Masked Defect?
A defect which could have been removed during initial stage is
removed in later stage how does it affect cost?
In testing can you explain the concept of work bench?
What's the difference between Alpha and Beta testing?
Can you explain the concept of defect cascading?
Can you explain how one defect leads to other defects?
Can you explain what is Usability testing?
What are the different strategies of rollout to the end users?
Can you explain requirement traceability and its importance?
What is the difference between Pilot and Beta testing?
How will you do a risk analysis during software testing?
How do you conclude which section is most risky in your application?
What does entry and exit criteria mean in a project?
On what basis is the Acceptance plan prepared?
What's the relation between environment reality and test phases?
What are different types of verifications?
What's the difference between Inspections and Walkthroughs?
Can you explain regression testing and confirmation testing?
what do you mean by coverage and what are the different types of
coverage techniques?
How does fundamentally a coverage tool work?
What is configuration management?
Can you explain the concept of baseline in software development?
What are the different test plan documents in project?
How do test documents in a project span across software development
life cycle?
Can you explain inventories?
How do you do Analysis and design for testing projects?
Can you explain calibration?
Which test cases are first written white boxes or black box?
Can you explain Co-habiting software?
What different impact rating's you have used in your project?
Can you explain what a test log is?
Explain SDLC (Software development Life Cycle) in detail?
Can you explain waterfall model?
Can you explain big-bang waterfall model?
Can you explain phased waterfall model?
Explain Iterative model, Incremental model, Spiral model,
Evolutionary model and V-Model?
Explain Unit testing, Integration tests, System testing and
Acceptance testing?
what's the difference between system and acceptance testing?
Which is the best model?
What group of teams can do software testing?

Testing Techniques
Can you explain boundary value analysis?
What is BV in software testing?
Can you explain Equivalence partitioning?
Can you explain how state transition diagram can be helpful during
testing?
Can you explain random testing?
Can you explain monkey testing?
What is negative and positive testing?
Can you explain exploratory testing?
What exactly are semi-random test cases?
Can you explain the concept of orthogonal array?
Can you explain pair-wise defect fundamental?
Can you explain the concept of decision tables?
How did you define severity ratings in your project?

CMMI
What is a Software process?
what are the different cost element involved in implementing process
in an organization?
What is a model?
What is maturity level?
Can you explain the concept of process area in CMMI?
Can you explain the concept of tailoring?
What is CMMI and what's the advantage of implementing CMMI in an
organization?
what's the difference between implementation and
Institutionalization?
what are different models in CMMI?
Can you explain staged and continuous models in CMMI?
Can you explain the different maturity levels in staged
representation?
Can you explain capability levels in continuous representation?
which model should we use and under what scenarios?
How many process areas are present in CMMI and in what classification
do they fall in?
What the difference between every level in CMMI?
what different sources are needed to verify authenticity for CMMI
implementation?
Can you explain SCAMPI process?
How is appraisal done in CMMI?
which appraisal method class is the best?
Can you explain the importance of PII in SCAMPI?
Can you explain implementation of CMMI in one of the Key process
areas?
Explanation of all process areas with goals and practices?
Can you explain the process areas?

Six Sigma
What is six sigma?
Can you explain the different methodology for execution and design
process in SIX sigma?
What does executive leaders, champions, Master Black belt, green
belts and black belts mean?
what are the different kinds of variations used in six sigma?
Can you explain the concept of standard deviation?
Can you explain QFD?
Can you explain FMEA?
Can you explain X bar charts?
Can you explain Flow charting and brain storming?
Can you explain the concept of fish bone/ Ishikawa diagram?

Metrics
What is meant by measure and metrics?
Can you explain Number of defects measure?
Can you explain number of production defects measure?
Can you explain defect seeding?
Can you explain DRE?
How do you measure test effectiveness?
Can you explain Defect age and Defect spoilage?

Automated Testing
What are good candidate for automation in testing?
which automation tool have you worked and can you explain them in
brief?
Can you explain how does load testing conceptually work for websites?
Can you explain how did you perform load testing using tool?
Can you explain the concept of data-driven testing?
Can you explain table-driven testing?
How can you perform data-driven testing using Automated QA?

Testing Estimation
What are the different ways of doing black box testing?
Can you explain TPA analysis?
Can you explain in brief Function points?
Can you explain the concept Application boundary?
Can you explain the concept of elementary process?
Can you explain the concept of static and dynamic elementary process?
Can you explain concept of FTR, ILF, EIF, EI, EO , EQ and GSC ?
Can you explain on what basis does TPA actually work?
Can you explain step by step how did you do estimation for black box
testing?
How did you estimate white box testing?
Is there a way to estimate acceptance test cases in a system?

Testing Interview Questions-Part 1

1.What is the testing process?

2.Verifying that an input data produce the expected output.

3.What is the difference between testing and debugging?

4.What is the difference between structural and functional testing?

5.What is a bug? What types of bugs do you know?

6.Bug is a error during execution of the program.

7.What is the difference between testing and quality assurance (QA)?

8.What kinds of testing do you know? What is it system testing? What is it integration testing? What is a unit testing? What is a regression testing?

9.Tell me about ur self?

10.Process in ur company?

11.Responsibilities in the project?

12.Manual and automation exp?

13.How many test cases u have written in ur model?

14.Why u have automated ur project?

15.For exmp out of 100 test cases if I ask you to automate how many you can automate?

16.What features you have frequently used in wr?

17.In your cv you have mention few types of testing tell me about that?

18.Role ur self in wr?

19.You know about trasability matrix if so tell me the fields of that?

20.Few tsl functions in wr?

21.What do u mean by regression testing have u done ?

22.You have any idea about back end testing?

23.Tell me about u r project?

24.Who is the client of ur company?

25.What is the concept of your project and which domain?

26.How many modules are there in your project and which module you have worked?

27.Can u tell me the data flow in the module?

28.What do u mean mean by integration testing?

29.Can u differ data flow and control flow?

30.Tell me about your way of written scripting?

Interview Question Part 2

31. You said one more generic what do u mean by that?

32. Can u done database testing tell me some quries?

33.Tell me about parameterizing data?

34.Why we need to go for testing?

35. What is CM Plan?

36. What is the back-end you are using for the Current Project? (SQL-SERVER)

37.Tell me difference between Oracle and SQL?

38.How much you are strong with SQL?

39.Tell about CMM?

40.Have you ever interacted with the client?

41.Tell about your company background?

42.What are your day- by-day activities?

43.In testing which are you are strong?

44.Tell me about the Testing life cycle?

45.Do you ever worked with the Win Runner?

46.What is the current and expected Package?

47.Explain Test Case Template?

48.Explain your project & what is your role in that Project?

49.What is White Box Testing and Black Box Testing?

50.How will you prepare the Test Plan?

51.What are the severity levels in your project?

52.What version you are using in Win Runner?

53.What is load and Stress Testing?

54.How will you check the database?

55.What is GUI Testing and Functionality Testing?56.How will you report the bug?

57.Write a query to fetch the data is the table such as Employee Table and Dept Table.

Employee Department

EmpNo DeptNo

Name Dept Name

Sal DeptNo

58. To fetch the data who is in the Department Number = 10

59. How will you maintain the project?

60. How many members are there in your team? To whom you will report the bug?

61. Why do you want to join in this Company?

62. Can you test DB using WR? What are the Databases that WR can support?

63. How do you set a query to fetch data from the database?

64. Rate your self in WR?

65. Once a new build comes to Quality Team, what they will do?

66.What is database testing?

1. What is the testing process?

1. What is the testing process?

Verifying that an input data produce the expected output.

2. What is the difference between testing and debugging?

Big difference is that debugging is conducted by a programmer and the programmer fix the errors during debugging phase. Tester never fixes the errors, but rather find them and return to programmer.

3. What is the difference between structural and functional testing?

Structural is a "white box" testing and based on the algorithm or code. Functional testing is a "black box" (behavioral) testing where the tester verifies the functional specification.

4. What is a bug? What types of bugs do you know?

Bug is a error during execution of the program. There are two types of bugs: syntax and logical.

5. What is the difference between testing and quality assurance (QA)?

This question is surprisingly popular. However, the answer is quite simple. The goals of both are different: The goal of testing is to find the errors. The goal of QA is to prevent the errors in the program.

6. What kinds of testing do you know? What is it system testing? What is it integration testing? What is a unit testing? What is a regression testing?

You theoretical background and home work may shine in this question. System testing is a testing of the entire system as a whole. This is what user see and feels about the product you provide. Integration testing is the testing of integration of different modules of the system. Usually, the integration process is quite painful and this testing is the most serious one of all. Integration testing comes before system testing. Unit testing is a testing of a single unit (module) of within system. It's conducted before integration testing. Regression testing is a "backward check" testing. The idea to ensure that new functionality added to the system did not break old, checked, functionality of the system.

7.What are all the major processes will involve in testing?

The major processes include:

1.Planning (test strategy, test objectives, risk management)

2.Design (functions to be tested, test scenario, test cases)

3Development (test procedures, test scripts, test environment)

4.Execution (execute test)

5.Evaluation (evaluate test results, compare actual results with expected results)

8.Could you test a program 100%? 90%? Why?

Definitely not! The major problem with testing that you cannot calculate how many error are in the code, functioning etc. There are many factors involved such as experience of programmer, complexity of the system etc.

9.How would you test a mug (chair/table/gas station etc.)?

First of all you must demand requirements and functional specification and design document of the mug. There will find requirements like ability to hold hot water, waterproof, stability, break ability and so on. Then you should test the mug according to all documents.

10.How would you conduct your test?

Each test is based on the technical requirements of the software product.

Manual Testing Q & A Part 3

21.What is a 'walkthrough'?

A 'walkthrough' is an informal meeting for evaluation or informational purposes. Little or no preparation is usually required.

22.What's an 'inspection'?

An inspection is more formalized than a 'walkthrough', typically with 3-8 people including a moderator, reader, and a recorder to take notes. The subject of the inspection is typically a document such as a requirements spec or a test plan, and the purpose is to find problems and see what's missing, not to fix anything. Attendees should prepare for this type of meeting by reading thru the document; most problems will be found during this preparation. The result of the inspection meeting should be a written report. Thorough preparation for inspections is difficult, painstaking work, but is one of the most cost effective methods of ensuring quality. Employees who are most skilled at inspections are like the 'eldest brother' in the parable in Their skill may have low visibility but they are extremely valuable to any software development organization, since bug prevention is far more cost-effective than bug detection.

23.What kinds of testing should be considered?

·Black box testing - not based on any knowledge of internal design or code. Tests are based on requirements and functionality.

·White box testing - based on knowledge of the internal logic of an application's code. Tests are based on coverage of code statements, branches, paths, conditions.

·unit testing - the most 'micro' scale of testing; to test particular functions or code modules. Typically done by the programmer and not by testers, as it requires detailed knowledge of the internal program design and code. Not always easily done unless the application has a well-designed architecture with tight code; may require developing test driver modules or test harnesses.

·incremental integration testing - continuous testing of an application as new functionality is added; requires that various aspects of an application's functionality be independent enough to work separately before all parts of the program are completed, or that test drivers be developed as needed; done by programmers or by testers.

·integration testing - testing of combined parts of an application to determine if they function together correctly. The 'parts' can be code modules, individual applications, client and server applications on a network, etc. This type of testing is especially relevant to client/server and distributed systems.

·functional testing - black-box type testing geared to functional requirements of an application; this type of testing should be done by testers. This doesn't mean that the programmers shouldn't check that their code works before releasing it (which of course applies to any stage of testing.)

·system testing - black-box type testing that is based on overall requirements specifications; covers all combined parts of a system.

·end-to-end testing - similar to system testing; the 'macro' end of the test scale; involves testing of a complete application environment in a situation that mimics real-world use, such as interacting with a database, using network communications, or interacting with other hardware, applications, or systems if appropriate.

·sanity testing - typically an initial testing effort to determine if a new software version is performing

·well enough to accept it for a major testing effort. For example, if the new software is crashing systems every 5 minutes, bogging down systems to a crawl, or destroying databases, the software may not be in a 'sane' enough condition to warrant further testing in its current state.

·regression testing - re-testing after fixes or modifications of the software or its environment. It can be difficult to determine how much re-testing is needed, especially near the end of the development cycle. Automated testing tools can be especially useful for this type of testing.

·acceptance testing - final testing based on specifications of the end-user or customer, or based on use by end-users/customers over some limited period of time.

·load testing - testing an application under heavy loads, such as testing of a web site under a range of loads to determine at what point the system's response time degrades or fails.

·stress testing - term often used interchangeably with 'load' and 'performance' testing. Also used to describe such tests as system functional testing while under unusually heavy loads, heavy repetition of certain actions or inputs, input of large numerical values, large complex queries to a database system, etc.

·performance testing - term often used interchangeably with 'stress' and 'load' testing. Ideally 'performance' testing (and any other 'type' of testing) is defined in requirements documentation or QA or Test Plans.

·usability testing - testing for 'user-friendliness'. Clearly this is subjective, and will depend on the targeted end-user or customer. User interviews, surveys, video recording of user sessions, and other techniques can be used. Programmers and testers are usually not appropriate as usability testers.

·install/uninstall testing - testing of full, partial, or upgrade install/uninstall processes.

·recovery testing - testing how well a system recovers from crashes, hardware failures, or other catastrophic problems.

·security testing - testing how well the system protects against unauthorized internal or external access, willful damage, etc; may require sophisticated testing techniques.

·compatability testing - testing how well software performs in a particular hardware/software/operating system/network/etc. environment.

·exploratory testing - often taken to mean a creative, informal software test that is not based on formal test plans or test cases; testers may be learning the software as they test it.

·ad-hoc testing - similar to exploratory testing, but often taken to mean that the testers have significant understanding of the software before testing it.

·user acceptance testing - determining if software is satisfactory to an end-user or customer.

·comparison testing - comparing software weaknesses and strengths to competing products.

·alpha testing - testing of an application when development is nearing completion; minor design changes may still be made as a result of such testing. Typically done by end-users or others, not by programmers or testers.

·beta testing - testing when development and testing are essentially completed and final bugs and problems need to be found before final release. Typically done by end-users or others, not by programmers or testers.

·mutation testing - a method for determining if a set of test data or test cases is useful, by deliberately introducing various code changes ('bugs') and retesting with the original test data/cases to determine if the 'bugs' are detected. Proper implementation requires large computational resources.

24.What are 5 common problems in the software development process?

·poor requirements - if requirements are unclear, incomplete, too general, or not testable, there will be problems.

·unrealistic schedule - if too much work is crammed in too little time, problems are inevitable.

·inadequate testing - no one will know whether or not the program is any good until the customer complains or systems crash.

·featuritis - requests to pile on new features after development is underway; extremely common.

·miscommunication - if developers don't know what's needed or customer's have erroneous expectations, problems are guaranteed.

25.What are 5 common solutions to software development problems?

·solid requirements - clear, complete, detailed, cohesive, attainable, testable requirements that are agreed to by all players. Use prototypes to help nail down requirements.

·realistic schedules - allow adequate time for planning, design, testing, bug fixing, re-testing, changes, and documentation; personnel should be able to complete the project without burning out.

·adequate testing - start testing early on, re-test after fixes or changes, plan for adequate time for testing and bug-fixing.

·stick to initial requirements as much as possible - be prepared to defend against changes and additions once development has begun, and be prepared to explain consequences. If changes are necessary, they should be adequately reflected in related schedule changes. If possible, use rapid prototyping during the design phase so that customers can see what to expect. This will provide them a higher comfort level with their requirements decisions and minimize changes later on.

·communication - require walkthroughs and inspections when appropriate; make extensive use of group communication tools - e-mail, groupware, networked bug- tracking tools and change management tools, intranet capabilities, etc.; insure that documentation is available and up-to-date - preferably electronic, not paper; promote teamwork and cooperation; use protoypes early on so that customers' expectations are clarified.

26.What is software 'quality'?

Quality software is reasonably bug-free, delivered on time and within budget, meets requirements and/or expectations, and is maintainable. However, quality is obviously a subjective term. It will depend on who the 'customer' is and their overall influence in the scheme of things. A wide-angle view of the 'customers' of a software development project might include end-users, customer acceptance testers, customer contract officers, customer management, the development organization's management/accountants/testers/salespeople, future software maintenance engineers, stockholders, magazine columnists, etc. Each type of 'customer' will have their own slant on 'quality' - the accounting department might define quality in terms of profits while an end-user might define quality as user-friendly and bug-free.

27.What is 'good code'?

'Good code' is code that works, is bug free, and is readable and maintainable. Some organizations have coding 'standards' that all developers are supposed to adhere to, but everyone has different ideas about what's best, or what is too many or too few rules. There are also various theories and metrics, such as McCabe Complexity metrics. It should be kept in mind that excessive use of standards and rules can stifle productivity and creativity. 'Peer reviews', 'buddy checks' code analysis tools, etc. can be used to check for problems and enforce standards.

For C and C++ coding, here are some typical ideas to consider in setting rules/standards; these may or may not apply to a particular situation:

·minimize or eliminate use of global variables.

·use descriptive function and method names - use both upper and lower case, avoid abbreviations, use as many characters as necessary to be adequately descriptive (use of more than 20 characters is not out of line); be consistent in naming conventions.

·use descriptive variable names - use both upper and lower case, avoid abbreviations, use as many characters as necessary to be adequately descriptive (use of more than 20 characters is not out of line); be consistent in naming conventions.

·function and method sizes should be minimized; less than 100 lines of code is good, less than 50 lines is preferable.

·function descriptions should be clearly spelled out in comments preceding a function's code.

·organize code for readability.

·use whitespace generously - vertically and horizontally

·each line of code should contain 70 characters max.

·one code statement per line.

·coding style should be consistent throught a program (eg, use of brackets, indentations, naming conventions, etc.)

·in adding comments, err on the side of too many rather than too few comments; a common rule of thumb is that there should be at least as many lines of comments (including header blocks) as lines of code.

·no matter how small, an application should include documentaion of the overall program function and flow (even a few paragraphs is better than nothing); or if possible a separate flow chart and detailed program documentation.

·make extensive use of error handling procedures and status and error logging.

·for C++, to minimize complexity and increase maintainability, avoid too many levels of inheritance in class heirarchies (relative to the size and complexity of the application). Minimize use of multiple inheritance, and minimize use of operator overloading (note that the Java programming language eliminates multiple inheritance and operator overloading.)

· for C++, keep class methods small, less than 50 lines of code per method is preferable.

· for C++, make liberal use of exception handlers

28.What is 'good design'?

'Design' could refer to many things, but often refers to 'functional design' or 'internal design'. Good internal design is indicated by software code whose overall structure is clear, understandable, easily modifiable, and maintainable; is robust with sufficient error-handling and status logging capability; and works correctly when implemented. Good functional design is indicated by an application whose functionality can be traced back to customer and end-user requirements.For programs that have a user interface, it's often a good idea to assume that the end user will have little computer knowledge and may not read a user manual or even the on-line help; some common rules-of-thumb include:

· the program should act in a way that least surprises the user

· it should always be evident to the user what can be done next and how to exit

· the program shouldn't let the users do something stupid without warning them.

29.What is SEI? CMM? ISO? IEEE? ANSI? Will it help?

·SEI = 'Software Engineering Institute' at Carnegie-Mellon University; initiated by the U.S. Defense Department to help improve software development processes.

·CMM = 'Capability Maturity Model', developed by the SEI. It's a model of 5 levels of organizational 'maturity' that determine effectiveness in delivering quality software. It is geared to large organizations such as large U.S. Defense Department contractors. However, many of the QA processes involved are appropriate to any organization, and if reasonably applied can be helpful. Organizations can receive CMM ratings by undergoing assessments by qualified auditors.

Level 1 - characterized by chaos, periodic panics, and heroic

efforts required by individuals to successfully

complete projects. Few if any processes in place;

successes may not be repeatable.

Level 2 - software project tracking, requirements management,

realistic planning, and configuration management

processes are in place; successful practices can

be repeated.

Level 3 - standard software development and maintenance processes

are integrated throughout an organization; a Software

Engineering Process Group is is in place to oversee

software processes, and training programs are used to

ensure understanding and compliance.

Level 4 - metrics are used to track productivity, processes,

and products. Project performance is predictable,

and quality is consistently high.

Level 5 - the focus is on continouous process improvement. The

impact of new processes and technologies can be

predicted and effectively implemented when required.

Perspective on CMM ratings: During 1997-2001, 1018 organizations

were assessed. Of those, 27% were rated at Level 1, 39% at 2,

23% at 3, 6% at 4, and 5% at 5. (For ratings during the period

1992-96, 62% were at Level 1, 23% at 2, 13% at 3, 2% at 4, and

0.4% at 5.) The median size of organizations was 100 software

engineering/maintenance personnel; 32% of organizations were

U.S. federal contractors or agencies. For those rated at

Level 1, the most problematical key process area was in

Software Quality Assurance.

· ISO = 'International Organisation for Standardization' - The ISO 9001:2000 standard (which replaces the previous standard of 1994) concerns quality systems that are assessed by outside auditors, and it applies to many kinds of production and manufacturing organizations, not just software. It covers documentation, design, development, production, testing, installation, servicing, and other processes. The full set of standards consists of: (a)Q9001-2000 - Quality Management Systems: Requirements; (b)Q9000-2000 - Quality Management Systems: Fundamentals and Vocabulary; (c)Q9004-2000 - Quality Management Systems: Guidelines for Performance Improvements. To be ISO 9001 certified, a third-party auditor assesses an organization, and certification is typically good for about 3 years, after which a complete reassessment is required. Note that ISO certification does not necessarily indicate quality products - it indicates only that documented processes are followed.

· IEEE = 'Institute of Electrical and Electronics Engineers' - among other things, creates standards such as 'IEEE Standard for Software Test Documentation' (IEEE/ANSI Standard 829), 'IEEE Standard of Software Unit Testing (IEEE/ANSI Standard 1008), 'IEEE Standard for Software Quality Assurance Plans' (IEEE/ANSI Standard 730), and others.

· ANSI = 'American National Standards Institute', the primary industrial standards body in the U.S.; publishes some software-related standards in conjunction with the IEEE and ASQ (American Society for Quality).

· Other software development process assessment methods besides CMM and ISO 9000 include SPICE, Trillium, TickIT. and Bootstrap.

30. What is the 'software life cycle'?

The life cycle begins when an application is first conceived and ends when it is no longer in use. It includes aspects such as initial concept, requirements analysis, functional design, internal design, documentation planning, test planning, coding, document preparation, integration, testing, maintenance, updates, retesting, phase-out, and other aspects.a

Manual Testing Q & A Part 5

41.What is 'configuration management'?

Configuration management covers the processes used to control, coordinate, and track: code, requirements, documentation, problems, change requests, designs, tools/compilers/libraries/patches, changes made to them, and who makes the changes.

42.What if the software is so buggy it can't really be tested at all?

The best bet in this situation is for the testers to go through the process of reporting whatever bugs or blocking-type problems initially show up, with the focus being on critical bugs. Since this type of problem can severely affect schedules, and indicates deeper problems in the software development process (such as insufficient unit testing or insufficient integration testing, poor design, improper build or release procedures, etc.) managers should be notified, and provided with some documentation as evidence of the problem.

43.How can it be known when to stop testing?

This can be difficult to determine. Many modern software applications are so complex, and run in such an interdependent environment, that complete testing can never be done. Common factors in deciding when to stop are:

·Deadlines (release deadlines, testing deadlines, etc.)

·Test cases completed with certain percentage passed

·Test budget depleted

·Coverage of code/functionality/requirements reaches a specified point

·Bug rate falls below a certain level

· Beta or alpha testing period ends

44.What if there isn't enough time for thorough testing?

Use risk analysis to determine where testing should be focused.

Since it's rarely possible to test every possible aspect of an application, every possible combination of events, every dependency, or everything that could go wrong, risk analysis is appropriate to most software development projects. This requires judgement skills, common sense, and experience. (If warranted, formal methods are also available.) Considerations can include:

·Which functionality is most important to the project's intended purpose?

·Which functionality is most visible to the user?

·Which functionality has the largest safety impact?

·Which functionality has the largest financial impact on users?

·Which aspects of the application are most important to the customer?

·Which aspects of the application can be tested early in the development cycle?

·Which parts of the code are most complex, and thus most subject to errors?

·Which parts of the application were developed in rush or panic mode?

·Which aspects of similar/related previous projects caused problems?

·Which aspects of similar/related previous projects had large maintenance expenses?

·Which parts of the requirements and design are unclear or poorly thought out?

·What do the developers think are the highest-risk aspects of the application?

·What kinds of problems would cause the worst publicity?

·What kinds of problems would cause the most customer service complaints?

·What kinds of tests could easily cover multiple functionalities?

·Which tests will have the best high-risk-coverage to time-required ratio?

45.What if the project isn't big enough to justify extensive testing?

Consider the impact of project errors, not the size of the project. However, if extensive testing is still not justified, risk analysis is again needed and the same considerations as described previously in 'What if there isn't enough time for thorough testing?' apply. The tester might then do ad hoc testing, or write up a limited test plan based on the risk analysis.

46.What can be done if requirements are changing continuously?

A common problem and a major headache.

·Work with the project's stakeholders early on to understand how requirements might change so that alternate test plans and strategies can be worked out in advance, if possible.

·It's helpful if the application's initial design allows for some adaptability so that later changes do not require redoing the application from scratch.

·If the code is well-commented and well-documented this makes changes easier for the developers.

·Use rapid prototyping whenever possible to help customers feel sure of their requirements and minimize changes.

·The project's initial schedule should allow for some extra time commensurate with the possibility of changes.

·Try to move new requirements to a 'Phase 2' version of an application, while using the original requirements for the 'Phase 1' version.

·Negotiate to allow only easily-implemented new requirements into the project, while moving more difficult new requirements into future versions of the application.

·Be sure that customers and management understand the scheduling impacts, inherent risks, and costs of significant requirements changes. Then let management or the customers (not the developers or testers) decide if the changes are warranted - after all, that's their job.

·Balance the effort put into setting up automated testing with the expected effort required to re-do them to deal with changes.

·Try to design some flexibility into automated test scripts.

·Focus initial automated testing on application aspects that are most likely to remain unchanged.

·Devote appropriate effort to risk analysis of changes to minimize regression testing needs.

·Design some flexibility into test cases (this is not easily done; the best bet might be to minimize the detail in the test cases, or set up only higher-level generic-type test plans)

· Focus less on detailed test plans and test cases and more on ad hoc testing (with an understanding of the added risk that this entails).

47.What if the application has functionality that wasn't in the requirements?

It may take serious effort to determine if an application has significant unexpected or hidden functionality, and it would indicate deeper problems in the software development process. If the functionality isn't necessary to the purpose of the application, it should be removed, as it may have unknown impacts or dependencies that were not taken into account by the designer or the customer. If not removed, design information will be needed to determine added testing needs or regression testing needs. Management should be made aware of any significant added risks as a result of the unexpected functionality. If the functionality only effects areas such as minor improvements in the user interface, for example, it may not be a significant risk.

48.How can Software QA processes be implemented without stifling productivity?

By implementing QA processes slowly over time, using consensus to reach agreement on processes, and adjusting and experimenting as an organization grows and matures, productivity will be improved instead of stifled. Problem prevention will lessen the need for problem detection, panics and burn-out will decrease, and there will be improved focus and less wasted effort. At the same time, attempts should be made to keep processes simple and efficient, minimize paperwork, promote computer-based processes and automated tracking and reporting, minimize time required in meetings, and promote training as part of the QA process. However, no one - especially talented technical types - likes rules or bureacracy, and in the short run things may slow down a bit. A typical scenario would be that more days of planning and development will be needed, but less time will be required for late-night bug-fixing and calming of irate customers.

49.What if an organization is growing so fast that fixed QA processes are impossible?

This is a common problem in the software industry, especially in new technology areas. There is no easy solution in this situation, other than:

· Hire good people

· Management should 'ruthlessly prioritize' quality issues and maintain focus on the customer

· Everyone in the organization should be clear on what 'quality' means to the customer

50.How does a client/server environment affect testing?

Client/server applications can be quite complex due to the multiple dependencies among clients, data communications, hardware, and servers. Thus testing requirements can be extensive. When time is limited (as it usually is) the focus should be on integration and system testing. Additionally, load/stress/performance testing may be useful in determining client/server application limitations and capabilities. There are commercial tools to assist with such testing.

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