Manual Testing Interview Question by Shammi Jha
Manual Testing Interview Question by Shammi Jha
2. Give me some example for high severity and low priority defect?
Suppose we have banking application which calculate Yearly, Monthly and Weekly interest.
But we have error in Yearly calculation then we can say it as HIGH SEVERIRTY and LOW priority
because we can fix it in next week also no problem.
2.1. Q. 8 Give me some example for high priority and low severity defect?
1. If suppose we have wrong title of the particular concern is not spelled correctly on HOME
page , it would give a negative impacted ICICC is spelled as a title for the project of the concern
ICICI. Then it is a high priority, low severity.
2. Suppose in one banking application there is one module ATM Facility. In that ATM facility
when ever we are depositing/withdrawing money it is not showing any conformation message
but actually at the back end it is happening properly without any mistake means only missing of
message, in this case as it is happening properly so there is nothing wrong with the application
but as end user is not getting any conformation message so he/she will be
Confuse for this. So we can consider this issue as HIGH Priority but LOW Severity defects…
2.2 Give me some example for low severity and low priority defect?
If suppose we have bug on page which is have very less hit i.e. rarely, then we can say it as low
severity, low priority defect.
The basic difference between web based application & client server application is that the web
application are 3 tier & client based are 2 tier.
CLIENT AND SERVER: Connected mode (connection exists always until logout) and Limited
number of users
In web based changes are made at one place & it is reflected on other layers also whereas
client based separate changes need be installed on client machine also.
So testing web application, apart from the above said two testing there are many other testing
to be done depending on the type of web application we are testing.
If it is a secured application (like banking site- we go for security testing etc.)
If it is an e-commerce testing application we go for Usability testing, performance testing etc.
If you want more technically then I can in according to development phases based on MVC
architecture then:
1. Web tier testing –> browser compatibility: Presentation layer(V view): Where only we can test
UI related things it’s the front view of the application.
2. Middle tier testing –> functionality, security: Logical layer (C Controller): This business logic
layer i.e. Controller all kind of processing and API work out here.
3. Data base tier testing –> database integrity, contents: Persistent layer (M Model): This layer
have direct relation with DB what ever the instruction request received from top logical layer
will forwarded to DB and processed response will be sent back which is requested.
In real time applications, in the case of server side programming one must follow the
architecture to develop a distributed application.
To develop any distributed application, it is always recommended to follow either 3-tier
architecture or 2-tier architecture or n-tier architecture.
3-tier architecture is also known as MVC architecture.
M stands for Model (database programming)
V stands for View (client side programming, HTML/AWT/APPLET/Swing/JSP) and
C stands for Controller (server side programming, Servlet )
The general architecture of MVC or 3-tier:
7.suppose the product/application has to deliver to client at 5.00PM,At that time you or your
team member caught a high severity defect at 3PM.(Remember defect is high severity)But the
client is cannot wait for long time. You should deliver the product at 5.00Pm exactly. Then
what is the procedure you follow?
The bug is high severity only so we send the application to the client and find out the severity is
priority or not, if its priority then we ask him to wait.
Here we found defects/bugs in the last minute of the delivery or release date
then we have two options
1. Explain the situation to client and ask some more time to fix the bug.
2. If the client is not ready to give some time then analyze the impact of defect/bug and try to
find workarounds for the defect and mention these issues in the release notes as known issues
or known limitations or known bugs. Here the workaround means remedy process to be
followed to overcome the defect effect.
3. Normally this known issues or known limitations (defects) will be fixed in next version or next
release of the software
10. How can you report the defect using excel sheet?
To report the defect using excel sheet
1: The Feature that been effected.
2: Test Case ID (Which fail you can even mention any other which are dependency on this bug)
3: Actual Behavior
4: Expected Behavior as mentioned in Test Case or EFS or EBS or SRS document with section
5: Your Test Setup used during Testing
6: STR: Steps to Re-Produce the bug
7: Additional Info
8: Attach a Screen Shot if it is a GUI bug
9: Which other features it is blocking because of this bug that you are unable to
Execute the test cases.
10: How much time you took to execute that test case or follow that specific TC
which leaded to bug?
OR
1. Test case ID
2. Module/section of the application (if applicable)
3. Issue (defect) description – a short describing what the bug is
4. Actual Behavior
5. Expected Behavior as mentioned in Test Case or EFS or EBS or SRS document with section.
6. STR Steps to reproduce the bug-information that will help re-encounter the issue.
7. Attach a Screen Shot if it is a GUI bug
8. Severity(High, medium and Low)
9. Which other features it is blocking because of this bug that you are unable to
execute the test cases.
10. How much time you took to execute that test case or follow that specific TC
which leaded to bug?
11. Issue status (Fix, Fail and Pending)
12. Project manager comment
11. If you have executed 100 test cases every test case passed but apart from these test case
you found some defect for which test case is not prepared, then how you can report the bug?
While reporting this bug into bug tracking tool you will generate the test case mean put the
steps to reproduce the bug.
12. What is the difference between web based application and client server application?
The basic difference between web based application & client server application is that the web
application are 3 tiers & client based are 2 tiers.
In web based changes are made at one place & it is reflected on other layers also whereas
client based separate changes need be installed on client machine also.
13. What is test plan? And can you tell the test plan contents?
Test plan is a high level document which explains the test strategy, time lines and available
resources in detail. Typically a test plan contains:
-Objective
-Test strategy
-Resources
-Entry criteria
-Exit criteria
-Use cases
-Test cases
-Tasks
-Features to be tested and not tested
-Risks/Assumptions.
14. How many test cases can you write per a day, an average figure?
Complex test cases 4-7 per day (10)
Medium test cases 10-15 per day (20)
Normal test cases 20-30 per day (30)
15. Who will prepare FRS (functional requirement documents)? What is the important of FRS?
The Business Analyst will prepare the FRS.
Based on this we are going to prepare test cases.
It contains
1. Overview of the project
2. Page elements of the Application (Filed Names)
3. Prototype of the application.
4. Business rules and Error states
5. Data Flow diagrams (DFD)
6. Use cases contains Actor and Actions and System Responses.
16. How you can decide the number of test cases is enough for testing the given module?
The developed test cases are covered all the functionality of the application we can say test
cases are enough. To know the functionality covered or not you can use RTM.
17. What is the difference between Retesting and Data Driven Testing?
Retesting: it is manual process in which application will be tested with entire new set of data.
Data Driven Testing(DDT)-It is a Automated testing process in which application is tested with
multiple test dated is very easy procedure than retesting because the tester should sit and need
to give different new inputs manually from front end and it is very tedious and boring Procedure.
After the Bug fixed, testing the application whether the fixed bug is affecting remaining
functionality of the application or not. Majorly in regression testing Bug fixed module and its
connected modules are checked for their integrity after bug fixation.
20. How does u perform regression testing, means what test cases u select for regression?
Regression testing will be conducted after any bug fixed or any functionality changed.
During defect fixing procedure some part of coding may be changed or functionality may be
manipulated. In this case the old test cases will be updated or completely re written
According to new features of the application where bug fixed area.
Here possible areas are old test cases will be executed as usual or some new test cases will be
added to existing test cases or some test cases may be deleted.
21. What are the client side scripting languages and server side scripting languages?
22. If a very low defect (user interface) is detected by u and the developer not compromising
with that defect, what will u do?
User interface defect is a high visibility defect and easy to reproduce.
Follow the below procedure
1. Reproduce the defect
2. Capture the defect screen shots
3. Document the proper inputs that you are used to get the defect in the defect report
4. Send the defect report with screen shots, inputs and procedure for defect reproduction.
Before going to this you must check your computer hard ware configuration that is same as
developer system configuration. And also check the system graphic drivers are properly.
Installed or not. If the problem in graphic drivers the User interfaces error will come.
So first check your side if it is correct from your side then reports the defect by following the
above method.
23.if u r only person in the office and client asked u for some changes and u didn’t get what
the client asked for what will u do?
One thing here is very important. Nobody will ask test engineer to change software that is not
your duty, even if it is related to testing and anybody is not there try to listen carefully if you are
not understand ask him again and inform to the corresponding people immediately.
Here the client need speedy service, we (our company) should not get any blame from
customer side.
25. How many Test-Cases can be written for the calculator having 0-9 buttons, Add, Equalto
buttons? The test cases should be focused only on add-functionality but mot GUI.What is
those test-cases?
Test-Cases for the calculator
so here we have 12 buttons totalize 0,1,2,3,4,5,6,7,8,9,ADD,Equalto -12 buttons
here u can press at least 4 buttons at a time minimum for example 0+1= for zero u should press
‘zero’ labeled button for plus u should press ‘+’ labeled button for one u should press ‘one’
labeled button for equal to u should press ‘equal to’ labeled button 0+1=here + and = positions
will not vary so first number position can be varied from 0 to 9 i.e. from permutation and
combinations u can fill that space in 10 ways in the same way second number position can be
varied from 0 to 9 i.e. from permutation and combinations u can fill that space in 10 ways
Total number of possibilities are =10×10=100
This is exhaustive testing methodology and this is not possible in all cases.
In mathematics we have one policy that the function satisfies the starting and ending values of
a range then it can satisfy for entire range of values from starting to ending.
then we check the starting conditions i.e. one test case for ‘0+0=’ (expected values you know
that’s ‘0′) then another test case for ‘9+9=’(expected values you know that’s ‘18′) only two test
cases are enough to test the calculator functionality.
27. How will you prepare Test plan. What are the techniques involved in preparing the Test
plan?
Test plan means planning for the release. This includes Project background
Test Objectives: Brief overview and description of the document
Test Scope: setting the boundaries
Features being tested (Functionalities)
Hardware requirements
Software requirements
Entrance Criteria (When to start testing):
Exit criteria (when to stop testing):
Test environment established, Builder received from developer, Test case prepared and
reviewed.
All bug status cycle are closed, all functionalities are tested, and all high and medium bugs are
resolved.
Project milestones: dead lines
32. In which way tester get Build A, Build B….. Build Z of an application, just explains the
process?
After preparation of test cases project manager will release software release note in that
document there will be URL path of the website link from that we will receive
the Build,
In case of web server projects, you will be provided with an URL or a 92.168. ***. *** (Web
address) which will help you access the project using a browser from your system.
In case of Client server, the Build is placed in the VSS (Configuration tool) which will help you
get the .exe downloaded to your computer.
(A VSS is network system virtualization technology that pools multiple Cisco ® Catalyst ® 6500
Series Switches into one virtual switch, increasing operational efficiency, boosting nonstop
communications, and scaling system bandwidth capacity to 1.4 tbps)
33. Apart from bug reporting what is your involvement in project life cycle?
As a Test engineer we design
1. Test cases,
2. Prepare test cases,
3. Execute Test cases,
4. Track the bugs,
5. Analyze the results report the bugs and
Involved in Regression testing, performance of system testing, system integration testing at last
preparation of Test summary report.
Test Report:-
1. Test Environment (Should be covered the OS, Application or web servers, Machine names,
Database, etc…)
2.Test Methods(Types of Tests, we have done in the project like Functional Testing, Platform
Testing, regression Testing etc.)
3. Major areas Covered.
4. Bug Tracking Details. (Includes inflow and outflow of the bus in our delivered project)
5. Work schedule (When we start the testing and we finished)
6. Defect Analysis
6.1 Defects logged in different types of tests like Functional Test, regression Test as per area
wised.
6.2 State of the Defects at end of the Test cycle.
6.3 Root cause analysis for the bugs marked as NOT A BUG.
7. QA observations or learning’s thought the life cycle.
Now let us write HIGH LEVEL TEST CASE and LOW LEVEL TEST CASE cases.
HIGH LEVEL TEST CASE (maximum test cases are functionality as per requirement):-
1. Verify that User is able to login with valid login and valid password.
2. Verify that User is not able to login with invalid login and valid password.
3. Verify that Reset button clears the filled screen.
4. Verify that a pop up message is displayed for blank login.
Etc…
LOW LEVEL TEST CASE (maximum test cases are UI related screens):-
1. Verify that after launching the URL of the application below fields are displays in the screen.
1. Login Name 2.Password.3.OK BUTTON 4.RESET button etc.
5. Check box, provided for the label “remember my password” is unchecked.
2. Verify that OK button should be disabled before selecting login and password fields.
3. Verify that OK button should we enabled after selecting login and password.
4. Verify that User is able to check the check box, provided for the label “remember my
password”.
Etc.
In this way, we can categories all the test cases under HIGH LEVEL and LOW LEVEL.
EMAIL PASSWORD
Empty Empty
Empty Invalid
Empty Valid
Valid Empty
Valid Invalid
In-Valid Empty
In-valid In-valid
In-valid Valid
VALID Login Success VALID Login Success
Test deliverables will be delivered to the client not only for the completed activities, but also for
the activities, which we are implementing for the better productivity. (As per the company’s
standards).Here I am giving you some of the Test deliverables in my project.
1. QA test Plan
2.Test case Docs
3. QA Test plan, if we are using Automation.
4. Automation scripts
5. QA Coverage Matrix and defect matrix.
6. Traceability Matrix
7. Test Results doc
8. QA Schedule doc (describes the deadlines)
9. Test Report or Project Closure Report. (Prepared once we rolled out the project to client)
10. Weekly status report (sent by PM to the client)
11. Release Notes.
TE is test case design, and execution and bug tracking and reporting them, Generally TL is
involved in preparation of the Test Plan. But it is not mandatory only TL will take main part in
the preparation of the TP. Test engineer can suggest to TL, if he (or) she has good understanding
on project and resources, if he or she has more exp with the project, if TL is wrongly given
deadlines. If your suggestions are valid, TL will incorporate all of them to the Test Plan but in
most of the companies Test engineers are just audience.
41. If a project is long term project, requirements are also changes then test plan will change
or not? Why?
Yes, definitely.
If requirement changes, the design documents, specifications (for that particular module which
implements the requirements) will also change. Hence the test plan would also need to be
updated. This is because “Resource Allocation” is one section in the test
Plan. We would need to write new test cases, review, and execute it. Hence resource allocation
would have to be done accordingly. As a result the Test plan would change
44. What is the Difference between Stub Testing and Driver Testing?
Stub testing:-
In top down approach, a core module is developed. To test that core module, small dummy
modules r used. So stubs r small dummy modules that test the core module.
Driver testing:-
In bottom up approach, small modules are developed. To test them a dummy core module
called driver is developed.
47. How would you perform performance testing manually for web site?
By noting the time to load page or perform any action with stop watch. I know it sounds funny
but this is the way performance is tested manually.
50. When will do the beta test? When will do the alpha test?
Alpha and Beta tests comes under User acceptance test. We will conduct these two systems
being released. We are giving opportunity to customer to check all punctualities covered or not.
Alpha testing conducting for software application by real customer at development site.
Beta testing conducting for software product by model customer at customer site.
at customer site.
52. How do you select test cases for Regression Testing (The point is when there is change
code how do you come to know which part of code or modules it will affect)?
Consider an example of a form which has a user name, password and Login button.
There is a code change and a new button “Reset” is introduced. Regression testing (for that
build) will include testing only the “Login” button and not the Reset button (testing Reset
button will be a part of conation testing). Hence the Regression tester need not worry about the
change in code, functionality. But he has to make sure that the existing functionality is working
as desired. Testing of “Reset” button will be included as a part of Regression, for the next build
53. Can you explain with example of high severity and low priority, low severity and high
priority, high severity and high priority, low severity and low priority?
1. High severity and high priority - Database connectivity cannot be established by multiple
users (in single device doubt).
2. Low severity and low priority - Small issues like, incorrect number of decimal digits in the
output.
3. Low severity and high priority - Images not updated.
4. High severity and low priority - In a module of say 2 interfaces, the link between them is
broken or is not functioning.
(1)High priority & High Severity: If u clicks on explorer icon or any other icon then system crash.
(2) Low priority & low severity: In login window, spell of ok button is “Ko”.
(3)Low priority & high serverty: In login window, there is a restriction login name should be 8
characters if user enter 9 or than 9 in that case system get crash.
(4)High priority & low severity: Suppose logo of any brand company is not proper in their
product. So it affects their business.
54. What will be the Test case for ATM Machine & Coffee Machine?
Test cases for ATM Machine:-
1. Successful inspection of ATM card
2. Un successful operation due to insert card in wrong angle
3. Un successful operation due to invalid account ex: other bank card or time expired card
4. Successful entry of PIN number
5. Un successful operation due to enter wrong PIN number 3times
6. Successful selection of language
7. Successful selection of account type
8. Un successful operation due to invalid account type
10. Successful selection of withdraw operation
11. Successful selection of amount to be withdraw.
12. Successful withdraw operation
13. Unsuccessful withdraw operation due to wrong denominations
14. Unsuccessful withdraw operation due to amount is greater than day limit
15. Unsuccessful withdraw operation due to lack of money in ATM
16. Unsuccessful withdraw operation due to amount is greater than possible balance
17. Unsuccessful withdraw operation due to transactions is greater than day limit
18. Unsuccessful withdraw operation due to click cancel after insert card
19. Unsuccessful withdraw operation due to click cancel after insert card & pin number
20. Unsuccessful withdraw operation due to click cancel after insert card, pin number &
language
21. Unsuccessful withdraw operation due to click cancel after insert card, pin number, language
&account type
22. Unsuccessful withdraw operation due to click cancel after insert card , pin number ,
language ,account type & withdraw operation
23.unsuccessful withdraw operation due to click cancel after insert card , pin number ,
language ,account type ,withdraw operation &amount to be withdraw
56. In SDLC process what is the role of PM, TL, DEVELOPER, tester in each and every phase?
Please explain me in detail?
In the SDLC we have these phases
1. Initial phase
2. Analysis phase
3. Designing phase
4. Coding phase
5. Testing
6. Delivery and maintenance
1. PM:-In the initial phase project manager can prepare a document for the requirements.
TL:-Team leader will prepare a team which is having test engineers, developer will provided by
the project manager.
Tester: tester will prepare test cases for that particular project
2. Analysis phase: Here all the members have a meeting to finalize the technology to develop
that project, the employee, time.
3. Designing phase: The project manager like senior level management will give the “guidelines
and directions” to the team members to develop the actual code that will be given in this phase.
4. Coding phase: Developer will develop the actual code using the provided doc, SRS, Guidelines
by PM and TL and they release the application to the tester.
5. Testing phase: they deploy their test cases to that application and prepare a bug profile
document if there is any defect/bug in that application and send it back to developer, developer
may rectify and releases than application as next build and if the bug not understand it will send
to the project lead in the delivery phase the so test engg can deploy the application in the client
environment.
6. Maintenance phase: if the client get any problem with the application it may solved by the
project lead with help of testers and developers
57. How do you Test Application with having any requirement and Document?
If it is an existing system or if a build is available then we explore the system while testing. This
helps knowing the functional use of the system, and its usability.
By asking questions to end users and how they use it will be more beneficial. Also, you may
work with BA to know more about the system.
Black box test is nothing but the same where you explore the system without having any prior
knowledge to the system.
59. What are the reasons why parameterization is necessary when load testing the Web
server and the database server?
When you test your applications, you may want to check how the application performs the
same operations with multiple sets of data.
For example, suppose you want to check how your web site responds to ten (10) separate sets
of data. You could record ten separate tests, each with its own set of data. Alternatively, you can
create Data Table parameters so that your test runs ten times, each time using a different set of
data.
62. When will u make update and modify the test object properties in the repository?
When ever the developer may change any one of the object properties definitely we have to
change the same in the object repository.
If a new version net build released from the development department we the test engineers
must to modify or update the same is compulsory, otherwise than test will show the bug.
63. What is the document needed to create a test case? How u tell it is test case?
System requirements specification (SRS)
Use case document
Test Plan
64. In customer details form having fields like customer name, customer address. After
completion of this module, client raise the change as insert the two radio buttons after
customer address. How you can check as a tester?
1. First we need to verify whether the radio button is there are not?
2. Confirm the radio buttons are present after the customer address or not.
3. Verify the no of radio button.
4. Verify only one radio button should be checked initially when we open the Customer details
form (if it is mentioned in FS)
5. Verify the functionality of the radio buttons i.e. if we check one ratio button, second radio
button should be unchecked.
6. Verify the spell check of radio button label name.
7. Verify the alignment of radio buttons in the form.
65. At the time of testing web based applications and client server applications, what you
absorbed as a tester?
We generally check for the links, data retrieving and posting.
We perform load and stress testing especially for Web based and Client-Server applications.
67. What is testing policy and testing methodology? And what is the difference?
Testing policy means all types of testing or testing techniques (i.e. functional testing, sanity
testing etc).
Testing methodology means white box and black box testing.
70. What participation a manual tester can do in documentation? Are there any tools
available for only documentation?
Yes, Manual tester will do Sub Test plan documents, as of my knowledge no tool is used to
prepare documentation.
71. What is the difference between low and high level test cases? Give Examples?
High level Test cases are those which covers major functionality in the application (i.e. retrieve,
update, display and cancel functionality related test cases, database test cases)
Low level test cases are those which are related to UI related test cases.
72. Is it mandatory to use USECASES or directly one can write test cases from requirements?
It’s not mandatory to write Use Cases, if the requirements are clear you can go ahead with Test
Cases.
Use Cases are written to know the business flow of the module/application
74. Given requirement collection doc, tester can prepare which test plan?
Test lead can prepare a test plan which performs testing on an application in an efficient
effective and in an optimized way. Test development will done by the testers using the test Plan
in the test plan they prepare the test strategy.
76.As far as the SDLC is concerned last test case, will it be written for “Maintenance Phase”?
As far as the SDLC is concerned last test case will be written for “Acceptance Testing”
77. What is test scenario and test case? Please explain in detail?
Test Scenario:
Test scenario is like laying out plans for testing the product, environmental condition, number of
team members required, making test plans, making test cases and what all features are to be
tested for the product. Test scenario is very much dependent on the product to be tested.
Test scenario is made before the actual testing starts.
Test Case:
Test case is a document which provides the steps to be executed which has been planned earlier.
It also depends on the type of product to be tested. Number of test cases is
Not fixed for any product.
78. What is the difference between Project Based Testing and Product Based Testing?
Project based is nothing but client requirements. Product based is nothing but market
requirements. Ex.stiching shirt is a project based and ready made shirt is product based.
80. What is testing process in related to Application testing process is the one which tells you
how the application should be tested in order to minimize the bugs in the application?
One main thing no application can be released as bug free application which is impossible.
81. What is the difference b/n Testing Methodology and Testing methods?
Testing Methodology define process, set of rules and principle which are follow by group
concerned with testing the application. Here I explain 7 step testing methodology:
1. Test Requirement Analysis
2. Test Plan
3. Test Design
4. Test execute
5. Defect track
6. Test Automation
7. Test Maintain
Testing methods or we can say that Testing Techniques:
White Box Testing (Unit Testing, Integration Testing)
Black Box Testing (System Testing, Functional Testing, Performance Testing>Load testing>stress
testing>volume testing & Security Testing) UAT (done by user/client with actual/live data)
83. How GUI testing will be done in manual testing for a website?
For any testing there should be some set of standards to be followed. Particularly in GUI testing,
look and feel should be good. We should follow the requirements specification documents for
GUI testing.
There should be some screen shots (given by client) which we should follow as it is.
And for button sizes, font, font size ,colors used, placing of links, objects and the placing of the
objects in the page should be followed some standards. If we take a button in the page that
should be some standard size. If the size of that button is more or less the client feel bad about
that. So we should have minimum common since while testing GUI testing. Some time there
may be some mistakes in the screen shots provided by the client also, but that is our
responsibility to raise those issues.
86. What is Test data? Where we are using this in testing process?
What is the importance of this data?
To execute test cases we should have test data. This test data should be for positive and
negative testing. for win runner we can get this test data from keyboard, excel sheets or from
data base
87. What is the difference between test case and test script?
Test case is a description what data to be tested and what data to be inserted what are the
actions to be done to check actual result against expected result what are the actual inputs we
will use? What are the expected results? Is called test script
Test Script: Is a short program written in a programming language used to test part of the
functionality of the software system. A written set of steps that should be performed manually
Can also be called a test script; however this is more correctly called a test case.
90. What is the difference between quality assurance and system testing explains in detail
with an example?
Quality Assurance: It is nothing but building an adequate confidence in the customer that the
developed software is acceding to requirements. Entire SDLC comes under QA. It is process
oriented.
System Testing: It is the process of executing entire system i.e. checking the s/w as well as parts
of system.
92. What is the difference between Build Management and Release Management?
When will conduct build verification and end to end testing?
Build Management is managing the issue fixture tasks in the builds whereas Release
management is managing the functionality to be incorporated in the Release.
Build Verification Test (BVT) is done when the build is first received by the testers. The basic
functionality is checked with valid data. This is done to check whether the build is testable or
not. This is done by testers.
End to End testing is also called system testing. Done by senior test engineers or Test lead.
93. What is boundary value analysis (BVA)? What is the use of it?
Boundary value analysis is a technique for test data selection. Test engineer chooses the values
that lie along the data extreams.It includes max, minimum, just inside, just out side, typical
values and error values.
Boundary Value Analysis is a technique used for writing the test cases. For example: If a
particular field accepts the
Values from 1 to 1000, then we test that field by entering only 1, 1000, 0, 1001, 999, 2.
I.e. we check on the boundaries and then
Minimum-1, minimum +1 and maximum+1, maximum-1.
99. What is a broken link in web testing and how test it?
When we clicked on Hyper link if it opens Page can’t be displayed then that Hyper link is called
as broken link.
100: What is CMM level? I need the answer in detail.
The Capability Maturity Model for Software describes the principles and practices underlying
software process maturity and is intended to help software organizations improve the maturity
of their software processes in terms of an evolutionary path from ad hoc chaotic processes to
mature disciplined software processes. The CMM is organized into five maturity levels
-
- Created by Shammi Jha