Manual-Testing Questions

1. What is main difference between Testing Techniques and Testing Methodology?

A] Testing methodology is nothing but the method you’re using in your company for eg:
waterfall method or V model or spiral model etc.Testing techniques are like black box,
white box etc

2. How do you approach for testing a web application?

A] A web-application is a three-tier application. This has a browser (monitors data)
[monitoring is done using html, dhtml, xml, javascript]-> webserver (manipulates data)
[manipulations are done using programming languages or scripts like adv java, asp, jsp,
vbscript, javascript, perl, coldfusion, php] -> database server (stores data) [data storage
and retrieval is done using databases like oracle, sql server, sybase, mysql].The types of
tests, which can be applied on this type of applications, are:
1. User interface testing for validation & user friendliness
2. Functionality testing to validate behaviors, i/p, error handling, o/p, manipulations,
services levels, order of functionality, links, content of web page & backend coverage’s
3. Security testing
4. Browser compatibility
5. Load / stress testing
6. Interoperability testing
7. Storage & data volume testing

3. What is mean by exactly the difference between the testcase and usecase?
A] An usecase are prepared from BRS.this will be in document form only which can be
understand by the team. it describe about how the software should when the end user uses
.where as testcases are written by tester using SRS.testcase are used for testing the
functionality or behavior of the application
B] Actually Test cases are derived from use cases use cases contains field validation of
fields Positive and negative scenarios for each functionality Difference between test case
and use case contains only validations but the test case contains test data

4. Can u define the usecase and testcase.

A] Usecase: It is in-depth detailed description about Customer Requirements. It is
developed from BRS/SRS. It is prepared by business analyst or QA Lead.
Testcase: It is a document describing the input, action and expected response to
determine whether the application is working correctly according to the customer
requirements. It is derived from srs,usecases and test scenarios. While developing test
cases we can find gaps in the requirements also.

6. What is bug life cycle?

A] Bug Life Cycle is the different status a bug takes in the process of it being FIXED.The
status can be
New
Reject
Open
Fixed,
Reopen
Retest
Closed.

9. What is traceability matrix?

A] Traceability matrix is nothing but mapping User requirements to Test cases. This
ensures that u have written enough test cases covering all the functionalities.

11. What is the purpose of using Tractability Matrix and how can you tell that testing has
been succeeds.
A] In traceability matrix we will map the Test Cases with Particular Test Scenario so that
we can find that any scenario is missed and if the total scenarios are mapped with
particular Testcases then the testing is fulfilled.

12. What is the main theme of doing Regression Testing?

A] By doing the Regression testing we can make sure that any new bug fixes did not
change the functionality of the application.
B] I think the main purpose of Regression is to know that any impact on the functionality
of the application or specific module where the developer had changed the code while
fixing the bug. Tester had to test the total scenarios not that particular scenario in
Regression

13. How can you define Priority and severity?

A] Priority: This is defined as how much time that developer should take to solve that
bug depending upon the functionality.
Severity: This is defined as how much impact is shown on the functionality.

14. Describe Bug life Cycle and the process taken in your organization.
A] As soon as Test Engineer finds a Bug will Raise the bug as in NEW Status and will
post it development Tl and Will keep it in Open Status and assign it to concerned
developer. And he can change the status of bug as duplicate, As designed, not
Reproducible, if it is a bug then developer will work on it and give it as Fix status. Then
Tester will retest that bug and see that it is reproducible or not if it is not reproducible
then he will close the bug, if its reproduce the same bug then keeps it in reopen status.

15. What is the Testing Process in your organization?

A] 1. According to my company BA and PM will get the Requirements initially from the
client these requirements can be named as BRS(business requirement specification) or
BRD.
2. then PM and Quality Analyzer will prepare the software Requirement
Specification(srs)ie., the flow of the functionality of the application, then SRS will be
send to concerned TL (ie both development and testing)
3. Then Testing TL will Prepare TestPlan based on SRS
4. Then Test engineer will be part of testing of preparing the testcases based on usecases
prepared by development Team
5. Then after Build Deployed TE has to Execute the Testcases.
6. Bugs found should be raised.

16. Describe the difference between Test scenario and Test Case
A] Test case is to validate the functionality of the scenario.
Test scenario is to know the flow the functionality of that particular scenario.

17. What are the different types of defects/errors are commonly appear during
the real time software testing?
A] Basically the defects are classified in to three types:
1. Missing Functionality (Requirement not implemented)
2. Extra Functionality (Added some thing more than need )
3. Wrongly implemented functionality (implemented requirement is not working)
Apart from this there is a very big list of defects are there:
1. Incorrect or missing functions,
2. Interface errors,
3. Errors in data structures or external database access,
4. Performance errors, and
5. Initialization and termination errors
6. GUI related
7. Failure of validation conditions.....etc

18. Explain Bug/Defect Life cycle?

A]
Bug found
|
|------>Test Engineer Finds Bug and Assigns that bug to
| Developer
|
Open ---->During Developer fixing bug it's status will
| be changes to open
|
|------>Developer fixes the bug
Resolved---->then developer changes its status to Resolved
|
|
|
Closed=------>Test engineer tests the system if it is fixed then he will change the bug
status to closed
So Bug has mainly three statuses
1. Open
2. Resolves
3. Closed
19. Phases of Software Testing Life Cycle?.
A] These are the phases of STLC
1. Requirements
2. Use Case Document
3. Test Plan
4. Test Case
5. Test Case execution
6. Report Analysis
7. Bug Analysis
8. Bug Reporting

20. Use of Regression Testing?

A]
1. Determine previously tested system functions properly without getting effected though
changes are made in some other segment of application system.
2. Determine System requirements remain current
3. Determine System test data and test conditions remain current

21. Use of Requirements Traceability?

A]
1. Tracing requirements to test cases
2. Tracing test cases to requirements
3. Gives test coverage of Requirements
4. Detailed report generation

22. The typical Application Test Lifecycle?

A]
1. Unit testing
2. Module testing
3. Component testing
4. Component integration testing
5. Subsystem testing
6. System testing
7. Functional testing
8. Technical integration testing
9. System integration testing
10. Non-functional testing
11. Integration testing
12. Regression testing
13. Model Office testing
14. User Acceptance testing

23. What are the Test Deliverables?

A] Deliverables are
1. Test Plans
2. Test Script Planner
3. Test Scripts
4. Test Execution Results
5. Defect Reports

24. Why testing is required?

A] Testing is required to check that the application satisfies the requirements.
B] There is another corner for need of testing:
Testing will give confidence for the software development company that the software
will work satisfactorily in client environment. Testing will improve the software quality.
Testing will also reduces the maintenance cost also. Even the client of the software will
get confidence on the software.
C] Testing is required for
1>to produce a quality product
2>a man can't do perform two tasks efficiently at a time i.e for example a developer can't
do two tasks, a)programming b)testing
3>without spend more time and cost we produce quality product
4>Due to psychological behavior of a man is
"a man can recognizing other faults easily"

25. What are the different techniques for writing test cases?
A] The different testing techniques are:
1. Boundary Value Analysis
2. Equivalence Partitioning
3. Error Guessing

26. What is Client Server/Web Server Configuration (ISS?)

A] Client Server: Here the server will have the information data
Business logic The Client will have only tools/interface to connect, access the
information and services of the server. Normally Client server will work in LAN network
of the office. If we come for web server client is any one of the browser and server will
be webserver like apache or IIS or some one else. Web server architecture is an extended
version of the client server architecture. Bowser client can access information from any
part of the world by using a browser like internet explorer/mozilla fire fox/Netscape
navigator.

28. How we do system testing project?

A] System Testing:- System testing is the testing of all the software and hardware
requirements for the project. The software which we are going to develop or we have
developed, require which type of configuration of PC (Hardware)to run or the
configuration which we do have is compatible for the software we want to run on client
PC or our development PC OR tester's PC.
B] System testing is an end to end testing .the environment which is similar to production
like environment
30. What is regression testing?
A] Whenever enhancements added to the existing functionality then only we go for
Regression testing why because new changes are whether effecting the old functionality
or not
(OR)
It is a type of testing. In which already tested functionality is once again tested in two
scenarios.
1. Whenever the defects are identified by the test engineer rectified by the developer and
released to the testing department then the test engineer will once again test the defect
functionality and the related functionality.
2. Whenever the new changes are incorporated by the developer and released to the
testing department the test engineer will once again test the related old functionality in
order to ensure that they remain same.

32. An application is given to you but the requirements and functionalities are missing
what will you do to start the testing?
A] Generally this type of case u can go for ad-hoc testing or monkey testing.
just go thru the whole application try to grap all the important functionalities check all the
results as per your basic knowledge. here in this case company wants u test how far your
knowledge in the domain? how far ur mindset works. try to catch all main and important
functions and write a test cases on it.

33. There are 2 clients for a server and that clients can access the data from the server
only for 10 days. so how will you test this scenario manually?
A] Transfer the system date to
1. -1 of end date and
2, +1 of end date and retrieve the data
in first case it should accept
in second case it shouldn't accept

34. What is error seeding?

A] The error seeding is nothing but the developer wontedly keep some errors in the
coding part to test the tester, whether the tester is doing the work properly can he find that
bug or not.
B] Error Seeding is the process of adding known faults wontedly in a program for
monitoring the rate of detection & removal and also to estimate the total number of faults
remaining in the program.
35. What is the difference between build and release?
A] Release: the modules that which we get for the first time for testing is release
Build: once we have tested and identified the bugs in that module we will send back to
the development side, they will correct and send us back for retesting, at that stage that
module is called as build

38. Explain about Traceability metrics?

A] It is mapping between customer requirements and test cases. Traceability Matrix
ensures that test cases written to test a feature of application are able to trace the customer
requirements. By using Traceability Matrix we can come to the conclusion as when
complete testing be stopped..
B] Traceability Matrix this maps the requirement in to testcases. That means for each
requirement in SRS document there must be atleast one testcase of course there may be
more than one test case per one requirement. And even one requirement may cover in
more than one test case. By using this we can review the testcase coverage. What are the
requirements are not converted into testcases.
what are requirements are tested in each phase of testing everything we can easily the
review the coverage of requirements.
Traceability matrix column names
1. Requirement ID(this will be SRS document)
2. Unit Test Case Id
3. Integration Test Case Id
4. System Test Case Id
5. Remarks

39. What is patch, abbrevate SCD, CAPA?

A] Patch is nothing but --developers send a build to the testing department after coding,
the tester will reject the build, if there is any defects-after rectification
Developers will release the built is called as PATCH.
SCD: Source Code Document
CAPA: Corrective Actions Preventive Actions

40. 1. What is Validation and Verification? 2. What is Severity and Priority?

Give examples for: Severity High and Priority High Severity High and Priority low
Severity low and Priority high Severity low and Priority low 3. What is Test Metrics? 4.
What is Traceability Matrix? 5. What is CAR in Cheque Remittance Project? 6. What are
the tabs in the latest version of Test Director? 7. Explain Development "V" Model? 8.
What will you do first when you are asked to start testing? 9. What will you do if you
find a bug first time? Can i directly report to the developer? 10. Can you connect Load
Runner to Test Director?
A] Verification is the process to assure that, the product in particular phase of
development process is consistence with the requirements.
Validation is nothing but assuring that the final product satisfies the system requirements
Severity is nothing but how seriousness is the defect on the functionality Priority is the
importance of the defect to resolve in terms of customers severity high and priority high
eg: cannot connect to server high severity no date format high priority
eg:incorrect output high severity look of web page not good low priority
Test Metrics:
Metrics is nothing but measurement
there are 3 types of measurement
QAM(Quality Assurance Measurement):This is used to test
where quality is coming or not
TMM(Test Management Measurement):To find how much testing
is completed and how is to test
PCM(Process Capability Measurement):Depending on old project any changes are
required or not
Traceability matrix: defines the mapping between customer requirements to possible test
cases developed to test that requirement
Sorry i have no idea on CAR
In TD we have Requirements tab
Test Plan Tab
Test Lab Tab
Defects
V-Model Stands for Verification and validation this defines mapping between multiple
stages of development stages along with multiple stages of testing

41. What is the bug life cycle? In which part u involved?

A] Status of the bug assigned based on the scenario is bug life cycle. The status
comprises of New, Open or reject,
Reopen, Fixed, Retest and Close. I involve in New, Reopen and Close.

42. 1. Regression& Retesting 2. What is usability testing? 3. Functionality testing

4. On what basis you will write the test cases 5. do you written the test scripts also 6.
where do you store the test cases 7. where do you execute the test cases. 8. Do you
prepare the requirements?
A] 1. Regression: Testing the application/system after the bug fix to check whether the
bug fix affecting the remaining functionality of the application. This test will be
conducted on every build when previous bugs are resolved in that build.
Retesting: Re-execution of all test cases after receiving every build. This will provide
confidence all the good working features of previous build are working fine.
2. Usability Testing: Testing application how user friendly when user using it.
3. Functionality testing: Testing each functionality of the application.
4. Basis to write the test cases: Generally we refer SRS (software requirement document)
to write testcases. To under stand Flow of transactions we will refer the flow diagrams.
To write the GUI test cases we will refer the model screen shots (normally provided in
Design document) For database test cases we will refer the database tables definitions in
SRS document.
5. If the testing is done by Automation tool then we should write or record test scripts
using automation tool.
6. Configuration management tool like VSS or Just we will keep it as share document.
7. Manually one by one by seeing the excel test case document or by using any
automation tool.
8. Normally testers won't involve in requirement preparation.

43. If the bug is reproducible then what is the status that u have given to the developer?
A] If the bug is reproducible, then it is in the Open status and it is re-opened again for the
developer to fix it

44. Tell me the V-model advantages & disadvantages?

A] V-Model advantages:
 • It is also called as verification and validation Model.
• This means the verification and validation will be done side by side.
• It emphasis the strict process flow to develop a quality product.
• The errors occurred in any phase will be corrected in that phase itself.
V-Model disadvantages:
• It needs lot of resources and money.
• It needs an established process to implement.
• It can be implemented by only some big companies.

45. What are the mandatory fields when you rise a bug?
A] The mandatory fields are
1) Title
2) Assigned to field (to the person in charge--developer)
3) Severity and priority
4) Steps to reproduce the bug
B] When u want to log a defect,
1. Check whether someone in your team has raised it earlier or not.
2. Go to Defects tab in Quality Center and Click "New".(If your using a quality center
tool)
3. Give Summary of the Defect
4. Expected Result
5. Actual Result
6. Assigned to(dev)
7. Environment
8. Priority
9. Severity
10. Build Version
11. Steps to Reproduce, finally
12. Screen shot attached

46. How will you test Email field?

A] E-mail address validation
Address = "A@b.c"; -- Valid
Address = "A@b.cnet"; -- Invalid
Address = "A@b.c_"; -- Invalid
Address = "A@bcnn"; -- Invalid
Address = "Ab.cnn"; -- Invalid
Address = "A@bc"; -- Invalid
Address = "A@bat@.cnn"; -- Invalid
Address = "A@bat/.com"; -- Invalid
Must not be too short and too long. Only one @ in email address Only one period ’.’or
two periods. No more than 3 characters after the final period (reverse find is 0 based not 1
based)com/ org/net/mil/gov Should not have an underscored after @ Allowed characters
0-9 A-Z _. @-

47. Give an example for high severity and low priority?

A] Logo is not displaying correctly. But displaying of logo won't affect the remaining
functionality of the application. But it is requirement given by the client.
48. Types of testing?
A] If we classify the testing types on Tester knowledge then the testing types are only
three:
1. White Box testing
2. Black box testing
3. GrayBox Testing
White Box Testing: Means testing the application with coding /programming knowledge.
That means the tester has to correct the code also.
Black box testing: testing the application without coding /programming knowledge that
means the tester doesn't require coding knowledge. Just he examines the application
External functional behavior and GUI features.
Grey box testing is combination of box testing types There are several testing types are
there: I would like list some of the important tests:
1. System Test
2. Regression Test
3. User acceptance test
4. Unit test
5. GUI test
6. Functional test
7. Database test
8. Usability test
9. Integration test
10. Security test
11. Load/stress/Performance test
12. MultiBrowser Compatibility test
13. Alpha Test
14. Beta test
The last Two test type’s i.e. Alpha Test & Beta test are product based test types.
Depending on the type of application testing team chooses some set of test to test the
application.
For example:
If the application is related to E-commerce domain then the following test must conduct
to ensure it's quality
1. Fuctional testing
2. Usability testing
3. Load/performance testing
4. Security testing
5. Database testing.

49. Explain the Stress Testing?

A] Stress testing is a form of testing that is used to determine the stability of a given
software system in abnormal operational conditions. Testing the application behavior
beyond normal operational capacity. For example if a web application can handle 100
users max any point of time. Remember that 100 users is the max handling capacity of
the web application. In stress testing testers will generate scenario to test the application.
as follows:
test-1:110 users
test-2:120 users
test-3:150 users....etc
Then they will observe the Load(user) Vs the response(time) characteristics. this will
give the clear picture of the application under stress conditions.

50. Explain Load testing?

A] Load Testing means Testing to check the maximum Load on the application with out
comparing with the response time dis-proportionality.
B] Load testing is done for 3 reasons:
1. Software Reliability: When the application is loaded with statistical representative
load, load testing is done to ensure whether the application behaves as expected.
2. Performance Testing: When the application is loaded within a range of min to max
load, load testing is to ensure whether the application can sustain without running out of
resources or having transaction suffer excessive delay.
3. Maximum sustainable load: To determine the maximum sustainable load the
application can handle.

51. Explain the performance testing?

A] Performance testing is testing how fast the system performs under a particular
workload.
This will be useful to evaluate the system characteristics like: Scalability Reliability
This also can be used to compare one system with another.

52. Differences Between White box testing and Black box testing?
A] White Box Testing: Means testing the application with coding /programming
knowledge. That means the tester has to correct the code also.
Black box testing: testing the application without coding /programming knowledge that
means the tester doesn't require coding knowledge. Just he examines the application
External functional behavior and GUI features.

53. Explain the V-Model?

A] V-Model advantages:
• It is also called as verification and validation Model
• This means the verification and validation will be done side by side.
• It emphasis the strict process flow to develop a quality product.
• The errors occurred in any phase will be corrected in that phase itself.
V-Model disadvantages:
• It needs lot of resources and money.
• It needs an established process to implement.
• It can be implemented by only some big companies.
54. Software life Cycle models?
A] Software life Cycle models are:
1. Waterfall model
2. Spiral model
3. Iterative development model
4. Prototyping model
5. V-model
6. v-v model

55. What is advantages and disadvantages of the Waterfall Model and V-Model?
A] Waterfall Model advantages:
• It is a linear sequential model
• It is very simple model to implement
• It is the first model.
• It needs very few resources to implement
Disadvantages:
• In this model there is no back tracking.
• For example if any error occurred in any stage of software development, it can’t
be corrected in that build.
V-Model advantages:
• It is also called as verification and validation Model.
• This means the verification and validation will be done side by side.
• It emphasis the strict process flow to develop a quality product.
• The errors occurred in any phase will be corrected in that phase itself.
V-Model disadvantages:
• It needs lot of resources and money.
• It needs an established process to implement.
• It can be implemented by only some big companies.

57. If developer is not agree with your bug then what is your response?
A] If the developer is not agree with the bug that posted by a tester, we should
convenience them to approve the bug by conducting the meeting or we have to take a
screen shot of
the bug occurred in the application and to be posted or shown to the development team.

58. What is the configuration tool is using in your organization?

A] The configuration management tool used in our organization is VSS(visual source
safe)

59. What is the difference between alpha and beta testing?

A] Alpha testing is an internal acceptance testing. This is simulated or actual operational
testing by users/customers or dedicated test team at the developer's site.
Beta testing comes after alpha testing. Versions of developed software called beta
versions are released to limited audience outside of the company. Sometimes these
Versions are released to the public to increase feedback fields for the future users.
60. How to identify the gaps in the system?
A] One can identify the functional gaps in the system at the time of going through the
functional documentation or when they conduct the testing, it all comes on experience.

61. What is Component Testing? How to do Component Level Testing?

A] Component Testing means testing the component of the system. A group of
components is known as module. So a tester always starts his/her testing from the basic
level i.e Component of the application.
Ex: - you have different functionalities (modules/sub modules), those are either satisfying
customer requirements or not. (BRS/SRS/FS)

62. What u will do when u have no sufficient time to test the application build release?
A] If there is no sufficient time then tester will conduct Ad-hoc testing.
In this type of testing no formal testing documents will be there. Here the tester decides
important testing areas and conducts testing on those areas only without any testcases.
Here in this tester common sense and past experience plays very important role in Ad-hoc
testing.

63. What is the difference bug, error, and defect?

A] Error: It is the Deviation from actual and the expected value.
Bug: It is found in the development environment before the
Product is shipped to the respective customer.
Defect: It is found in the product itself after it is shipped to the respective customer.

65. Contents of test plan?

A]
• Test plan consists of
• introduction
• objective
• scope
• features tested and not be tested
• acceptance criteria
• suspension criteria
• testing approach
• tool to be used
• risks and contingencies
• staff and training needs