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 requirement 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 systems 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.
Compatibility 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.
“I18N “Testing:It is nothing but called as “Internationalization testing”
Determine wheather your developed product’s support for international character encoding methods is sufficient and whether your product development methodologies take into account international coding standards.
“L10″ Testing: It is nothing but called as ” Localization Testing”
verifies your products are ready for local markets or not
Sanity testing is subset of regression testing. A cusrsory and not through type of regression testing, to ensure that any changes implemented do not break up the existing functionality and the system behaves sainly. Where as initial testing effort to determine if a new software version is performing well enough to accept it for a major testing effort is called smoke testing.
I am a tester and would like to become a TEST MANAGER.
Can anyone give me any usefull tips (i.e. white paper about test manager interview techniques, what to do (learn) to be a good test manager, what is a good test mger..)
thanks, Michael
Functional Testing: Black-box type testing geared to functional requirements of an application; this type of testing should be done by testers.
Non-Functional Testing: Testing of those requirements that do not relate to functionality. i.e. performance, usability, Security, Installability, Compatibility etc.
An example of a “Low Severity and High Priority” mainly depends on the requirement of the project, An example could be, suppose the requirement will be to print and get the hard copy of an applicants name and other details and suppose if a particular common font (say the email address is generally in a different font and width usually) is not getting printed this could be of the “Low Severity and High Priority”.
High Severity and Low Priority an example could be suppose the application hangs for sometime only if a very very rare situation, say only if the memory is of very less and if the condition is almost never valid but can be entered by the user very very rarely, say something like typing a large very large number for age and submitting the appication hangs. Again it all depends on the requirement specified by the product.
What is Diff. betweem Manual and Automation Testing.
This answer is quite simple, Manual is when user needs to do many things based on the testcase specified, say like c\lick some tab and check if the tab is working fine or click on a particular URL and check if the web site specified opens.
The above stuff can also be done automatically, ie through some automated tools like Winrunner , Silk Test etc the things can be automated , so user just has to trigger the tool and the tool will take care of executing , only thing needed is we need to know how to make the testcases automated through that tool which is not very difficult.
What are the different typs of Test Plan templets.
I dont think so there are different types of testplans, but most of the testplans will be kind of some standard template, some may have few additional contents more than the standard template and some may skip few. Let me know if I need to type in some of the contents of the standard template ?.
I have questions regarding sdlc I am confussing with sdlc methologies i.e I know there are differnt methologies on those
1. water fall model
2.iterative model
3.spiral model
what about rup (rational unified process) and v model those are also come under methologies or not
If interviewr ask me what sdlc u fallowd in ur comany how can i answer this question
Plese help me about this one.
can anyone give the full details about boundary analysis value ?
This Techinque Partitions the input and output values of the component in to a number of ordered sets
with identified boundaries. that can be :
Poitive ( inside or on the boundary )
negative ( outside the boundary )
test are created for values immediately above the boundary, on the boundary and immediately below the boundary.
water fall model
The waterfall model is a sequential software development model (a process for the creation of software) in which development is seen as flowing steadily downwards (like a waterfall) through the phases of requirements analysis, design, implementation, testing (validation), integration, and maintenance.
spiral model
The spiral model is a software development process combining elements of both design and prototyping-in-stages, in an effort to combine advantages of top-down and bottom-up concepts
Iterative and Incremental development is a software development process developed in response to the weaknesses of the more traditional waterfall model. The two most well known iterative development frameworks are the Rational Unified Process and the Dynamic Systems Development Method. Iterative and incremental development is also an essential part of Extreme Programming and all other agile software development frameworks.
Validation - ‘are we building the right system’
Verification - ‘are we building the system right’
Validation endeavours to ensure that the system is what the customer really wants, that it is ‘fit for purpose’.
Verification involves checking the system against the requirements specification as this defines what characteristics the system should have; verification is concerned with correctness and completeness
The Agile Software Development primarily focuses on an iterative method of development and delivery.
The developers and end users communicate closely and the software is built. A working piece of software is delivered in a short span of time and based on the feedback more features and capabilities are added.
The focus is on satisfying the customer by delivering working software quickly with minimum features and then improvising on it based on the feedback. The customer is thus closely involved in the Software Design and Development Process.
The delivery timelines are short and the new code is built on the previous one.
Despite this, high quality of the product cannot be comprised
waterfall model The waterfall model is a sequential software development model in which development is seen as flowing steadily downwards (like a waterfall) through the phases of requirements analysis, design, implementation, testing (validation), integration, and maintenance.mostly we used this model only…
so we tell that this model we used…..
Tell me which one is QA and which one is QC in the pair of Verification and Validation
Verification is Come under QA. Validation Is come under QC/TESTER.
Verification is a High Level Activity . QA gone with Process .QA has to check each and Every Documents .
Validation is a Low Level Activity . QC/TESTER gone with Process.QC/TESTER has to check that the system meets the customer requirements.
Severity Priority
1. Severity is associated 1. Priority is ass with
with standards scheduling
2. How Bad A Bug Is 2. How Important Bug Is
3. Assigned as 3. Assigned as
a, High a, Most Urgent (p1)
b, Medium b, Immediate (p2)
c, Low C, No Problem (p3)
These Assignes r depend upon Company . it is vary from company to company.
Severity mean the project leader/PM who ever responsible for that particual project will put. where as priority , the testers will put according to the funcitonality of the bug
Well, the discussion on Severity and Priority are very different.
In the Working hierarchy, a Tester could give a different Severity and Priority and the Lead could change it. The Test Manager or the Project Manager could request the QA resource to change it (either the Lead or Tester) to a different status on one or both of them.
Severity is how bad the Defect is….. Tester generally issues a Medium for most of the defects (personal experience) the Lead might think its a High… but the Manager could think it as ShowStopper….
Priority… is how important that is.. Tester might disregard a UI related issue, but a lead or a manager could think it to be a important issue as the User is very picky about the GUI.
Well, if u are a tester ask the lead to define the Severities and Priorities. If u are a Lead define them and publish it. If u are a manager know what your Lead has done (since you approved those definitions).
i have had scenarios where Severity was low and the Priority was High. Severity was Showstopper (which was changed to Medium) and the Priority was low…..
QA is the last part of the SDLC….. cant ask why its done so… they are decided in a meeting of high-level peers….. :-)
The difference between severity and priority is that.
Severity means the how bug is critical, map with critical levels like, it crash the system, loss of data like that.
The priority means how that bugs is important to fix accroding to time schedual, may be the functionlity is not requir immediatly where that bug is blong.
In the simplest of the terms severity and priority fall as follows:
Severity: How it affects the system/application
(Critical/High/Medium/Low)
Priority: How early the defect needs to be attended
(Urgent/Very High/High/Medium/Low)
This message is for Lakshmi Says:December 13th, 2006 at 5:43 am
Hi Lakshmi,
Agile is a methodolgy. Agile testing menas you can change the requirement inbetween, the all stages like designing,coding,testing all can be changed at any time of period.
Inbetween the client can add or change some requirements. So we can modify requirement accordingly and the other stages respectively.
While the requirement is partially done, the design ,coding and test plan preparation,testcase preparation will be started. The changes in all phases can be done at any stage.
Nowadays mostly by 85% of companies follow Agile methodology only.
i saw all the q’s and answers no one given clear informationabt v model.
under v model we can see verification and validation
under verification we can see BRS,SRS(reviews) later HLD’s and lld’s(review) and in between coading
under validation totally testing plays like unit,integration,systemand user acceptance testing
verification : the monitoring and measuring the strength of development process is called as verfication.
validation : after completion of developement process, the delivered s/w component testingis called as validation.
clearly to say
**************
DURING PROCESS CHECKING IS CALLED VERIFICATION
44 Comments on SQA and testing frequently asked definitions
It would be useful to add definations of i18n and l10n testing
“I18N “Testing:It is nothing but called as “Internationalization testing”
Determine wheather your developed product’s support for international character encoding methods is sufficient and whether your product development methodologies take into account international coding standards.
“L10″ Testing: It is nothing but called as ” Localization Testing”
verifies your products are ready for local markets or not
Sanity testing is subset of regression testing. A cusrsory and not through type of regression testing, to ensure that any changes implemented do not break up the existing functionality and the system behaves sainly. Where as initial testing effort to determine if a new software version is performing well enough to accept it for a major testing effort is called smoke testing.
Hi ,
What is the Exact Use of QTP 8.2 ?
I am a tester and would like to become a TEST MANAGER.
Can anyone give me any usefull tips (i.e. white paper about test manager interview techniques, what to do (learn) to be a good test manager, what is a good test mger..)
thanks, Michael
Qa means you have to take care in testing that software would create less and minor acceptable bugs for enduser experience
tips:devotion and dedication with great different types of knowledge is must
Hi ,
Can any body tell me the Diff between functional and nonfunctional testing?
Functional Testing: Black-box type testing geared to functional requirements of an application; this type of testing should be done by testers.
Non-Functional Testing: Testing of those requirements that do not relate to functionality. i.e. performance, usability, Security, Installability, Compatibility etc.
can give the full details about boundary analysis value
Also it good to talk about , defination and Scope of for SQA and SQE
what is difference between checked and verified
Difference between Severity and Priority.
Give examples for
1. Low Severity and High Priority
1. High Severity and Low Priority
What is Diff. betweem Manual and Automation Testing.
What are the different typs of Test Plan templets.
An example of a “Low Severity and High Priority” mainly depends on the requirement of the project, An example could be, suppose the requirement will be to print and get the hard copy of an applicants name and other details and suppose if a particular common font (say the email address is generally in a different font and width usually) is not getting printed this could be of the “Low Severity and High Priority”.
High Severity and Low Priority an example could be suppose the application hangs for sometime only if a very very rare situation, say only if the memory is of very less and if the condition is almost never valid but can be entered by the user very very rarely, say something like typing a large very large number for age and submitting the appication hangs. Again it all depends on the requirement specified by the product.
What is Diff. betweem Manual and Automation Testing.
This answer is quite simple, Manual is when user needs to do many things based on the testcase specified, say like c\lick some tab and check if the tab is working fine or click on a particular URL and check if the web site specified opens.
The above stuff can also be done automatically, ie through some automated tools like Winrunner , Silk Test etc the things can be automated , so user just has to trigger the tool and the tool will take care of executing , only thing needed is we need to know how to make the testcases automated through that tool which is not very difficult.
What are the different typs of Test Plan templets.
I dont think so there are different types of testplans, but most of the testplans will be kind of some standard template, some may have few additional contents more than the standard template and some may skip few. Let me know if I need to type in some of the contents of the standard template ?.
hi..
can any body Explain me about The V-model…,
In the V–model.., Where will be our Actual Testing Team Involves..???
Hai This is uma.
I have questions regarding sdlc I am confussing with sdlc methologies i.e I know there are differnt methologies on those
1. water fall model
2.iterative model
3.spiral model
what about rup (rational unified process) and v model those are also come under methologies or not
If interviewr ask me what sdlc u fallowd in ur comany how can i answer this question
Plese help me about this one.
QTP is required just to get good job in MNC or CMM level company.
can anyone give the full details about boundary analysis value ?
This Techinque Partitions the input and output values of the component in to a number of ordered sets
with identified boundaries. that can be :
Poitive ( inside or on the boundary )
negative ( outside the boundary )
test are created for values immediately above the boundary, on the boundary and immediately below the boundary.
Tell me which one is QA and which one is QC in the pair of Verification and Validation
what ia agile testing?
water fall model
The waterfall model is a sequential software development model (a process for the creation of software) in which development is seen as flowing steadily downwards (like a waterfall) through the phases of requirements analysis, design, implementation, testing (validation), integration, and maintenance.
spiral model
The spiral model is a software development process combining elements of both design and prototyping-in-stages, in an effort to combine advantages of top-down and bottom-up concepts
Iterative and Incremental development is a software development process developed in response to the weaknesses of the more traditional waterfall model. The two most well known iterative development frameworks are the Rational Unified Process and the Dynamic Systems Development Method. Iterative and incremental development is also an essential part of Extreme Programming and all other agile software development frameworks.
What are Validation and Verification ?
Validation - ‘are we building the right system’
Verification - ‘are we building the system right’
Validation endeavours to ensure that the system is what the customer really wants, that it is ‘fit for purpose’.
Verification involves checking the system against the requirements specification as this defines what characteristics the system should have; verification is concerned with correctness and completeness
1 difference between verification & validation
2 what is verificaton methods
The Agile Software Development primarily focuses on an iterative method of development and delivery.
The developers and end users communicate closely and the software is built. A working piece of software is delivered in a short span of time and based on the feedback more features and capabilities are added.
The focus is on satisfying the customer by delivering working software quickly with minimum features and then improvising on it based on the feedback. The customer is thus closely involved in the Software Design and Development Process.
The delivery timelines are short and the new code is built on the previous one.
Despite this, high quality of the product cannot be comprised
hi …
waterfall model The waterfall model is a sequential software development model in which development is seen as flowing steadily downwards (like a waterfall) through the phases of requirements analysis, design, implementation, testing (validation), integration, and maintenance.mostly we used this model only…
so we tell that this model we used…..
what is FAT TESTING?
Tell me which one is QA and which one is QC in the pair of Verification and Validation
Verification is Come under QA. Validation Is come under QC/TESTER.
Verification is a High Level Activity . QA gone with Process .QA has to check each and Every Documents .
Validation is a Low Level Activity . QC/TESTER gone with Process.QC/TESTER has to check that the system meets the customer requirements.
What is Diff. betweem Manual and Automation Testing ?
Manual Testing : A test Engineer sonduct any test on applicationbuild without using any tool.
Here we right test case . Done Regression and functionality and other approches in manually.
Automation Testing : A TEster Conducts tests on an application build with the help of Tools.
Here we right scripts and done regression and functionality and other approches using Automation Tools like Winrunnerand etc..
Difference between Severity and Priority ?
Severity Priority
1. Severity is associated 1. Priority is ass with
with standards scheduling
2. How Bad A Bug Is 2. How Important Bug Is
3. Assigned as 3. Assigned as
a, High a, Most Urgent (p1)
b, Medium b, Immediate (p2)
c, Low C, No Problem (p3)
These Assignes r depend upon Company . it is vary from company to company.
What if i dont find any bugs at all?
i did it understand u r question is it before System TEsting or after System Testing.
Before System Testing It Is Impossible.Atleast u may get Cosmetic Bugs .
After Testing it may possible.
How can a tester verify whether the test cases/ data are right/ wrong?
Why we are moving into QTP from Winrunner?
What are the applications does winrunner support and what is the main advantage of moving to QTP?
Severity mean the project leader/PM who ever responsible for that particual project will put. where as priority , the testers will put according to the funcitonality of the bug
Well, the discussion on Severity and Priority are very different.
In the Working hierarchy, a Tester could give a different Severity and Priority and the Lead could change it. The Test Manager or the Project Manager could request the QA resource to change it (either the Lead or Tester) to a different status on one or both of them.
Severity is how bad the Defect is….. Tester generally issues a Medium for most of the defects (personal experience) the Lead might think its a High… but the Manager could think it as ShowStopper….
Priority… is how important that is.. Tester might disregard a UI related issue, but a lead or a manager could think it to be a important issue as the User is very picky about the GUI.
Well, if u are a tester ask the lead to define the Severities and Priorities. If u are a Lead define them and publish it. If u are a manager know what your Lead has done (since you approved those definitions).
i have had scenarios where Severity was low and the Priority was High. Severity was Showstopper (which was changed to Medium) and the Priority was low…..
QA is the last part of the SDLC….. cant ask why its done so… they are decided in a meeting of high-level peers….. :-)
Is it mandatory to know all the tools like Winrunner, load runner,QTP.?
Can anyone refer to me some good software testing books or Can I refer some sites online itself.
I have 3 years of experience in software testing and I have mostly worked on Manual testing, I would like to update myself on the latest tools.
The difference between severity and priority is that.
Severity means the how bug is critical, map with critical levels like, it crash the system, loss of data like that.
The priority means how that bugs is important to fix accroding to time schedual, may be the functionlity is not requir immediatly where that bug is blong.
In the simplest of the terms severity and priority fall as follows:
Severity: How it affects the system/application
(Critical/High/Medium/Low)
Priority: How early the defect needs to be attended
(Urgent/Very High/High/Medium/Low)
This message is for Lakshmi Says:December 13th, 2006 at 5:43 am
Hi Lakshmi,
Agile is a methodolgy. Agile testing menas you can change the requirement inbetween, the all stages like designing,coding,testing all can be changed at any time of period.
Inbetween the client can add or change some requirements. So we can modify requirement accordingly and the other stages respectively.
While the requirement is partially done, the design ,coding and test plan preparation,testcase preparation will be started. The changes in all phases can be done at any stage.
Nowadays mostly by 85% of companies follow Agile methodology only.
Can I know detailed what is STLC? and the difference between SDLC and STLC?
STLC is software testing life cycle
SDLC is software dovelopment life cycle
STLC is one of the phases in SDLC
i saw all the q’s and answers no one given clear informationabt v model.
under v model we can see verification and validation
under verification we can see BRS,SRS(reviews) later HLD’s and lld’s(review) and in between coading
under validation totally testing plays like unit,integration,systemand user acceptance testing
verification : the monitoring and measuring the strength of development process is called as verfication.
validation : after completion of developement process, the delivered s/w component testingis called as validation.
clearly to say
**************
DURING PROCESS CHECKING IS CALLED VERIFICATION
AFTER PROCESS CHECKING IS CALLED VALIDATION