Explore topic-wise InterviewSolutions in .

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.

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:

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.

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.

• 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).

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.

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.

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.

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.

• 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.

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.

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.

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.

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.

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.

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.

When a bug is found, it needs to be communicated and ASSIGNED to DEVELOPERS that can fix it. After the problem is resolved, fixes should be re-tested. Additionally, determinations should be made regarding requirements, software, hardware, safety impact, etc., for regression testing to check the fixes didn't CREATE other problems elsewhere. If a problem-tracking system is in place, it should encapsulate these determinations. A variety of commercial, problem-tracking/management software tools are AVAILABLE. These tools, with the detailed input of software test ENGINEERS, will give the team complete information so developers can understand the bug, get an idea of its severity, reproduce it and fix it.

When a bug is found, it needs to be communicated and assigned to developers that can fix it. After the problem is resolved, fixes should be re-tested. Additionally, determinations should be made regarding requirements, software, hardware, safety impact, etc., for regression testing to check the fixes didn't create other problems elsewhere. If a problem-tracking system is in place, it should encapsulate these determinations. A variety of commercial, problem-tracking/management software tools are available. These tools, with the detailed input of software test engineers, will give the team complete information so developers can understand the bug, get an idea of its severity, reproduce it and fix it.

A software project test plan is a document that DESCRIBES the objectives, scope, APPROACH and focus of a software testing effort. The process of preparing a test plan is a useful way to think through the EFFORTS needed to validate the acceptability of a software product. The completed document will help people outside the test group UNDERSTAND the why and how of product validation. It should be thorough ENOUGH to be useful, but not so thorough that none outside the test group will be able to read it.

A software project test plan is a document that describes the objectives, scope, approach and focus of a software testing effort. The process of preparing a test plan is a useful way to think through the efforts needed to validate the acceptability of a software product. The completed document will help people outside the test group understand the why and how of product validation. It should be thorough enough to be useful, but not so thorough that none outside the test group will be able to read it.

Documentation plays a critical role in QA. QA practices should be documented, so that they are repeatable. Specifications, DESIGNS, BUSINESS RULES, inspection reports, configurations, code changes, test plans, test cases, bug reports, user MANUALS should all be documented. Ideally, there should be a system for easily finding and OBTAINING of documents and determining what document will have a particular piece of information. Use documentation change management, if possible.

Documentation plays a critical role in QA. QA practices should be documented, so that they are repeatable. Specifications, designs, business rules, inspection reports, configurations, code changes, test plans, test cases, bug reports, user manuals should all be documented. Ideally, there should be a system for easily finding and obtaining of documents and determining what document will have a particular piece of information. Use documentation change management, if possible.

It depends on the size of the organization and the risks involved. For large organizations with high-risk PROJECTS, a serious management buy-in is required and a formalized QA process is necessary. For medium size organizations with lower risk projects, management and ORGANIZATIONAL buy-in and a slower, step-by-step process is required. Generally speaking, QA processes should be balanced with productivity, in order to keep any bureaucracy from getting out of hand. For smaller groups or projects, an ad-hoc process is more appropriate. A lot depends on team leads and managers, FEEDBACK to developers and good communication is ESSENTIAL among customers, managers, developers, test engineers and testers. Regardless the size of the company, the greatest value for effort is in managing requirement processes, where the goal is requirements that are clear, COMPLETE and testable.

It depends on the size of the organization and the risks involved. For large organizations with high-risk projects, a serious management buy-in is required and a formalized QA process is necessary. For medium size organizations with lower risk projects, management and organizational buy-in and a slower, step-by-step process is required. Generally speaking, QA processes should be balanced with productivity, in order to keep any bureaucracy from getting out of hand. For smaller groups or projects, an ad-hoc process is more appropriate. A lot depends on team leads and managers, feedback to developers and good communication is essential among customers, managers, developers, test engineers and testers. Regardless the size of the company, the greatest value for effort is in managing requirement processes, where the goal is requirements that are clear, complete and testable.

Software Testing can be defines as under:-
• Testing involves operation of a system or application under controlled conditions and EVALUATING the results (EG, if the user is in interface A of the application while using hardware B, and does C, then D should happen). The controlled conditions should include both normal and abnormal conditions. Testing should intentionally attempt to make things go wrong to determine if things happen when they shouldnt or things DONT happen when they should. It is oriented to detection.
• Organizations vary considerably in how they assign responsibility for QA and testing. SOMETIMES they are the combined responsibility of one group or individual. Also common are PROJECT teams that include a mix of testers and developers who work closely together, with overall QA processes monitored by project managers. It will depend on what best fits an organizations size and business structure.

Software Testing can be defines as under:-
• Testing involves operation of a system or application under controlled conditions and evaluating the results (eg, if the user is in interface A of the application while using hardware B, and does C, then D should happen). The controlled conditions should include both normal and abnormal conditions. Testing should intentionally attempt to make things go wrong to determine if things happen when they shouldnt or things dont happen when they should. It is oriented to detection.
• Organizations vary considerably in how they assign responsibility for QA and testing. Sometimes they are the combined responsibility of one group or individual. Also common are project teams that include a mix of testers and developers who work closely together, with overall QA processes monitored by project managers. It will depend on what best fits an organizations size and business structure.

Software QA INVOLVES the entire software DEVELOPMENT PROCESS - MONITORING and IMPROVING the process, making sure that any agreed-upon standards and procedures are followed, and ensuring that problems are found and DEALT with. It is oriented to prevention.

Software QA involves the entire software development PROCESS - monitoring and improving the process, making sure that any agreed-upon standards and procedures are followed, and ensuring that problems are found and dealt with. It is oriented to prevention.

• Miscommunication or no communication - as to specifics of what an application should or shouldn't do (the applications requirements).
• Software complexity - the complexity of current software applications can be difficult to comprehend for anyone without experience in modern-day software development. Windows-type INTERFACES, client-server and distributed applications, data communications, enormous relational databases, and sheer size of applications have all contributed to the exponential growth in software/system complexity. And the use of object-oriented techniques can complicate instead of simplify a project unless it is well-engineered.
• Programming errors - programmers, like anyone else, can make mistakes.
• Changing requirements (whether documented or undocumented) - the customer may not understand the effects of changes, or may understand and request them anyway - redesign, rescheduling of engineers, effects on other projects, work already completed that may have to be redone or thrown out, hardware requirements that may be affected, ETC. If there are many MINOR changes or any major changes, KNOWN and unknown dependencies among parts of the project are likely to interact and cause problems, and the complexity of coordinating changes may result in errors.
• Time pressures - scheduling of software projects is difficult at best, often requiring a lot of guesswork. When deadlines loom and the crunch comes, mistakes will be made.
• Poorly documented code - its tough to maintain and modify code that is badly written or poorly documented; the result is bugs. In many organizations management provides no incentive for programmers to document their code or write clear, understandable, maintainable code. In fact, its usually the opposite they get points mostly for quickly turning out code, and there is JOB security if nobody else can understand it (if it was hard to write, it should be hard to read).

Verification: typically involves reviews and meetings to evaluate documents, plans, code, REQUIREMENTS, and SPECIFICATIONS. This can be done with checklists, issues LISTS, walkthroughs, and INSPECTION meetings.
Validation: typically involves actual testing and takes place after verifications are completed. The term IV & V refers to INDEPENDENT Verification and Validation.

Verification: typically involves reviews and meetings to evaluate documents, plans, code, requirements, and specifications. This can be done with checklists, issues lists, walkthroughs, and inspection meetings.
Validation: typically involves actual testing and takes place after verifications are completed. The term IV & V refers to Independent Verification and Validation.

A walkthrough is an informal MEETING for EVALUATION or informational PURPOSES. LITTLE or no preparation is usually REQUIRED.

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

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 whats missing, not to fix anything. Attendees should prepare for this type of meeting by reading through 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 Why is it often hard for management to get serious about quality assurance.

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 whats missing, not to fix anything. Attendees should prepare for this type of meeting by reading through 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 Why is it often hard for management to get serious about quality assurance.

a). Poor requirements - if requirements are unclear, incomplete, too general, or not TESTABLE, there will be problems.
B). Unrealistic schedule - if too much work is crammed in too LITTLE time, problems are inevitable.
c). Inadequate testing - no one will KNOW whether or not the program is any good until the customer complains or systems crash.
d). Futurities - requests to pile on new features after development is underway; extremely common.
e). Miscommunication - if developers dont know whats needed or customers have erroneous EXPECTATIONS, problems are guaranteed.

a). Poor requirements - if requirements are unclear, incomplete, too general, or not testable, there will be problems.
b). Unrealistic schedule - if too much work is crammed in too little time, problems are inevitable.
c). Inadequate testing - no one will know whether or not the program is any good until the customer complains or systems crash.
d). Futurities - requests to pile on new features after development is underway; extremely common.
e). Miscommunication - if developers dont know whats needed or customers have erroneous expectations, problems are guaranteed.

QUALITY software is reasonably bug-free, delivered on TIME and within BUDGET, MEETS requirements and/or expectations, and is maintainable.

Quality software is reasonably bug-free, delivered on time and within budget, meets requirements and/or expectations, and is maintainable.

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 whats 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.

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 whats 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.

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.

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 good test engineer has a test to break ATTITUDE, an ability to take the point of view of the customer, a strong desire for QUALITY, and an attention to detail. TACT and DIPLOMACY are useful in maintaining a cooperative relationship with developers, and an ability to communicate with both.

A good test engineer has a test to break attitude, an ability to take the point of view of the customer, a strong desire for quality, and an attention to detail. Tact and diplomacy are useful in maintaining a cooperative relationship with developers, and an ability to communicate with both.

TRM means Test Responsibility Matrix. This is a vital reference document to ensure all the requirements are COVERED by at least one test case.It indicates mapping between test FACTORS and development STAGES.

Test factors like: Ease of use, reliability, portability, authorization, access control, audit TRAIL, ease of operates, maintainable etc.
Development stages like: Requirement gathering, Analysis, design, coding, testing, and maintenance.

TRM means Test Responsibility Matrix. This is a vital reference document to ensure all the requirements are covered by at least one test case.It indicates mapping between test factors and development stages.

Test factors like: Ease of use, reliability, portability, authorization, access control, audit trail, ease of operates, maintainable etc.
Development stages like: Requirement gathering, Analysis, design, coding, testing, and maintenance.

Its hard to make a decision. Most of the modern applications are very complex and run in an interdependent circumstance, so the complete testing will never be done. However, there are some COMMON factors for me to KNOW when to STOP testing, which are deadlines, test CASES completed with CERTAIN percentage passed, test budget used up, coverage of functionality and requirements reaches a specified point, bug rate falls below the specified level, milestone testing ends and so on.

Its hard to make a decision. Most of the modern applications are very complex and run in an interdependent circumstance, so the complete testing will never be done. However, there are some common factors for me to know when to stop testing, which are deadlines, test cases completed with certain percentage passed, test budget used up, coverage of functionality and requirements reaches a specified point, bug rate falls below the specified level, milestone testing ends and so on.

Testing work is unlimited, especially in large applications. The relatively enough testing is just to MAKE application MATCH product requirements and specifications very well, including FUNCTIONALITY, USABILITY, STABILITY, performance and so on.

Testing work is unlimited, especially in large applications. The relatively enough testing is just to make application match product requirements and specifications very well, including functionality, usability, stability, performance and so on.

First, with high speed and efficiency, AUTOMATED testing can release the MANPOWER from the complicated and repeated DAILY TESTS to spare consumption and time. Second, with high accuracy, automated testing will never make a mistake just like mankind does under TIREDNESS after long time testing.

First, with high speed and efficiency, automated testing can release the manpower from the complicated and repeated daily tests to spare consumption and time. Second, with high accuracy, automated testing will never make a mistake just like mankind does under tiredness after long time testing.

First, SINCE there is no such an automated test tool COULD replace mankind intelligence, we need to use manual testing to cover the PART that automated testing can't cover. Second, before the stable version comes out, manual testing is more effective than automated testing because automated testing may not be COMPLETED for system instability, crash for example.

First, since there is no such an automated test tool could replace mankind intelligence, we need to use manual testing to cover the part that automated testing can't cover. Second, before the stable version comes out, manual testing is more effective than automated testing because automated testing may not be completed for system instability, crash for example.

The SELECTIVE retesting of a software system that has been modified to ENSURE that any bugs have been fixed and that no other previously working functions have failed as a result of the reparations and that newly added features have not CREATED problems with previous versions of the software. Regression is ALSO referred to as verification testing.

The selective retesting of a software system that has been modified to ensure that any bugs have been fixed and that no other previously working functions have failed as a result of the reparations and that newly added features have not created problems with previous versions of the software. Regression is also referred to as verification testing.

Regression TESTING is initiated after a programmer has attempted to FIX a recognized PROBLEM or has added source code to a program that MAY have inadvertently introduced errors. It is a quality CONTROL measure to ensure that the newly modified code still complies with its specified requirements and that unmodified code has not been affected by the maintenance activity.

Regression testing is initiated after a programmer has attempted to fix a recognized problem or has added source code to a program that may have inadvertently introduced errors. It is a quality control measure to ensure that the newly modified code still complies with its specified requirements and that unmodified code has not been affected by the maintenance activity.

Severity: It is the impact of the bug on the application. Severity level should be SET by tester. The Severity levels are: Low, Medium, and high, very high and Urgent. It is set by the tester and it can not be changed.
1. Bug causes system crash or data loss.
2. Bug causes major functionality or other severe problems; product crashes in obscure cases.
3. Bug causes minor functionality problems, may affect "fit and finish".
4. Bug contains types, UNCLEAR wording or error messages in low visibility fields.

PRIORITY: How important is it to fix the bug is priority. Priority levels are set by the team lead or TEST MANAGER and it can be changed as required.
1. Must fix as soon as possible. Bug is blocking further progress in this area.
2. Should fix soon, before product release.
3. Fix if time; some what trivial. May be postponed.

Severity: It is the impact of the bug on the application. Severity level should be set by tester. The Severity levels are: Low, Medium, and high, very high and Urgent. It is set by the tester and it can not be changed.
1. Bug causes system crash or data loss.
2. Bug causes major functionality or other severe problems; product crashes in obscure cases.
3. Bug causes minor functionality problems, may affect "fit and finish".
4. Bug contains types, unclear wording or error messages in low visibility fields.

Priority: How important is it to fix the bug is priority. Priority levels are set by the team lead or test manager and it can be changed as required.
1. Must fix as soon as possible. Bug is blocking further progress in this area.
2. Should fix soon, before product release.
3. Fix if time; some what trivial. May be postponed.

Typical "V" shows DEVELOPMENT Phases on the Left hand side and Testing Phases on the Right hand side.
1. SRS/BRS User Acceptance. 
2. Analysis/Design System Testing. 
3. HLD Integration Testing.
4. LLD UNIT Testing. 
5. Coding.

Typical "V" shows Development Phases on the Left hand side and Testing Phases on the Right hand side.
1. SRS/BRS User Acceptance. 
2. Analysis/Design System Testing. 
3. HLD Integration Testing.
4. LLD Unit Testing. 
5. Coding.

QA:
It is process oriented.
It EVOLVES in entire process of software development.
Preventing oriented.

QC:
It is product oriented.
Work to EXAMINE the QUALITY of product.
Deduction oriented.

QA:
It is process oriented.
It evolves in entire process of software development.
Preventing oriented.

QC:
It is product oriented.
Work to examine the quality of product.
Deduction oriented.

Priority means “Importance of the DEFECT w.r.t CUSTOMER REQUIREMENT.”
SEVERITY means “Seriousness of the defect w.r.t functionality.”

Priority means “Importance of the defect w.r.t customer requirement.”
Severity means “Seriousness of the defect w.r.t functionality.”

F-Function Behaviours.
R-Requirements (OUTPUTS) of the System that is defined.
S-Specification (How, What, When, Where, and Way it behavior’s).
FRS : Function REQUIREMENT Specification.
This is a DOCUMENT which contains the Functional behavior of the system or a feature. This document is also known as EBS External Behaviour Specification - Document. Or EFS External Function Specification.

F-Function Behaviours.
R-Requirements (Outputs) of the System that is defined.
S-Specification (How, What, When, Where, and Way it behavior’s).
FRS : Function Requirement Specification.
This is a Document which contains the Functional behavior of the system or a feature. This document is also known as EBS External Behaviour Specification - Document. Or EFS External Function Specification.

Database Testing is PURELY done BASED on the requirements. You may generalize a few features but they won’t be complete. In general we look at:
1. Data Correctness (DEFAULTS).
2. Data Storage/Retrieval.
3. Database Connectivity (across MULTIPLE platforms).
4. Database Indexing.
5. Data Integrity.
6. Data SECURITY.

Database Testing is purely done based on the requirements. You may generalize a few features but they won’t be complete. In general we look at:
1. Data Correctness (Defaults).
2. Data Storage/Retrieval.
3. Database Connectivity (across multiple platforms).
4. Database Indexing.
5. Data Integrity.
6. Data Security.

Integration testing MEANS testing an APPLICATION to verify the data FLOWS between the modules. For example, when you are testing a bank application, in ACCOUNT balance it shows the 100$as the available balance. but in DATABASE it shows the 120$. Main thing is “integration done by the developers and integration testing done by the testers.”

Integration testing means testing an application to verify the data flows between the modules. For example, when you are testing a bank application, in account balance it shows the 100$as the available balance. but in database it shows the 120$. Main thing is “integration done by the developers and integration testing done by the testers.”

Functional testing is a testing process where we TEST the functionality/behaviour of each functional component of the application. i.e. minimize BUTTON, TRANSFER button, links etc.i.e we check what is each component doing in that application.

Regression testing is the testing the behaviour of the application of the UNCHANGED areas when there is a change in the build.i.e we check whether the changed requirement has altered the behaviour of the unchanged areas. The IMPACTED area may be the whole of the application or Some part of the application.

Functional testing is a testing process where we test the functionality/behaviour of each functional component of the application. i.e. minimize button, transfer button, links etc.i.e we check what is each component doing in that application.

Regression testing is the testing the behaviour of the application of the unchanged areas when there is a change in the build.i.e we check whether the changed requirement has altered the behaviour of the unchanged areas. The impacted area may be the whole of the application or Some part of the application.

HIGH severity BUGS AFFECTS the end users .testers tests an application with the users point of view, hence it is given as high severity. High PRIORITY is given to the bugs which affects the PRODUCTION. Project managers assign a high priority based on production point of view.

High severity bugs affects the end users .testers tests an application with the users point of view, hence it is given as high severity. High priority is given to the bugs which affects the production. Project managers assign a high priority based on production point of view.

The testing is not getting started after the CODING. After release the build the testers PERFORM the smoke TEST. Smoke test is the FIRST test which is done by the testing team. This is according to the testing team. But, before the RELEASING of a build the developers will perform the unit testing.

The testing is not getting started after the coding. After release the build the testers perform the smoke test. Smoke test is the first test which is done by the testing team. This is according to the testing team. But, before the releasing of a build the developers will perform the unit testing.

Developer is the one who sends the APPLICATION to the TESTER by doing all the necessary code in the application and sends the marshal id to the tester. The tester is the one who gives all the input/output and checks whether he is GETTING required output or not. A developer is the one who works on INSIDE interfacing where as the tester is the one who works on OUTSIDE interfacing.

Developer is the one who sends the application to the tester by doing all the necessary code in the application and sends the marshal id to the tester. The tester is the one who gives all the input/output and checks whether he is getting required output or not. A developer is the one who works on inside interfacing where as the tester is the one who works on outside interfacing.

Test plan document is prepared by the test lead, it contains the contents like introduction, objectives, test strategy, scope, test items, program modules user procedures, features to be tested features not to tested approach, pass or fail CRITERIA, testing process, test deliverables, testing, tasks, responsibilities, resources, schedule, environmental requirements, risks & contingencies, change management procedures, plan APPROVALS, etc all these THINGS help a test manager understand the testing he should do & what he should follow for testing that PARTICULAR PROJECT.

Test plan document is prepared by the test lead, it contains the contents like introduction, objectives, test strategy, scope, test items, program modules user procedures, features to be tested features not to tested approach, pass or fail criteria, testing process, test deliverables, testing, tasks, responsibilities, resources, schedule, environmental requirements, risks & contingencies, change management procedures, plan approvals, etc all these things help a test manager understand the testing he should do & what he should follow for testing that particular project.

A computer bug is an ERROR, flaw, mistake, FAILURE, or fault in a computer program that prevents it from working CORRECTLY or produces an incorrect result.

A computer bug is an error, flaw, mistake, failure, or fault in a computer program that prevents it from working correctly or produces an incorrect result.