Professional Documents
Culture Documents
Manual Testing With Ans
Manual Testing With Ans
fail to perform its required function. If a bug or defect is encountered during the
execution phase of the software development, it can cause the component or the
system
to fail. On the other hand, an error is a human error, which gives rise to
incorrect
result.
4. What is a Review?
A review is an evaluation of a said product or project status to ascertain any
discrepancies from the actual planned results and to recommend improvements to
the said product. The common examples of reviews are informal review or peer
review,
technical review, inspection, walkthrough, management review.
12. What is meant by functional defects and usability defects in general? Give
appropriate example.
We will take the example of ‘Login window’ to understand functionality and
usability
defects. A functionality defect is when a user gives a valid user name but invalid
password and the user clicks on login button. If the application accepts the user
name and password, and displays the main window, where an error should have been
displayed. On the other hand a usability defect is when the user gives a valid user
name, but invalid password and clicks on login button. The application throws up an
error message saying “Please enter valid user name” when the error message should
have been “Please enter valid Password.”
test case life cycle is identifying the test scenarios either from the
specifications
or from the use cases designed to develop the system. Once the scenarios have been
identified, the test cases apt for the scenarios have to be developed. Then the
test
cases are reviewed and the approval for those test cases has to be taken from the
concerned authority. After the test cases have been approved, they are executed.
When the execution of the test cases start, the results of the tests have to be
recorded.
The test cases which pass are marked accordingly. If the test cases fail,
defects have to be raised. When the defects are fixed the failed test case has to
be executed again.
28. What is Agile testing and what is the importance of Agile testing?
Agile testing is software testing, which involves the testing of the software from
the customer point of view. The importance of this testing is that, unlike normal
testing process, this testing does not wait for development team to complete the
coding
first and then doing testing. The coding and testing both goes simultaneously.
It requires continuous customer interaction.
It works on SDLC (Systems Development Life Cycle) methodologies, it means that the
task is divided into different segments and compiled at the end of the task.
35. What are the five common solutions for software developments problems?
• Setting up the requirements criteria, the requirements of a software should
be complete, clear and agreed by all
• The next thing is the realistic schedule like time for planning, designing,
testing, fixing bugs and re-testing
• Adequate testing, start the testing immediately after one or more modules
development.
• Use rapid prototype during design phase so that it can be easy for customers
to find what to expect
• Use of group communication tools
47. While testing stored procedures what are the steps does a tester takes?
The tester will check the standard format of the stored procedures and also it
checks the
fields are correct like updates, joins, indexes, deletions as mentioned in the
stored procedure.
48. How would you know for database testing, whether trigger is fired or not?
On querying the common audit log you would know, whether, a trigger is fired or
not. It is in audit log where you can see the triggers fired.
49. In data base testing, what are the steps to test data loading?
Following steps need to follow to test data loading
• Source data should be known
• Target data should be known
• Compatibility of source and target should be checked
• In SQL Enterprise manager, run the DTS package after opening the
corresponding DTS package
• You have to compare the columns of target and data source
• Number of rows of target and source should be checked
• After updating data in the source, check whether the changes appears in the
target or not.
• Check NULLs and junk characters
53. what is test plan document and explain the contents briefly.
Ans- The Test Plan document is derived from the Product Description, Software
Requirement Specification SRS, or Use Case Documents.
The Test Plan document is usually prepared by the Test Lead or Test Manager and the
focus of the document is to describe what to test, how to test, when to test and
who will do what test.
54. what are the different types of testing life cycle models, which type of
testing model does your project follow?
have you worked in agile methodology in any of your project?
Ans- Types- Waterfall, Spiral/Iterative/Cycle, Prototype Model, Agile.
My project is using Agile methodology.
a. Introduction:
Provide an overview of the test plan.
Specify the goals/objectives.
Specify any constraints.
b. References:
List the related documents, with links to them if available, including the
following:
Project Plan
Configuration Management Plan
c. Test Items:
List the test items (software/products) and their versions.
d. Features to be Tested:
List the features of the software/product to be tested.
Provide references to the Requirements and/or Design specifications of the
features to be tested
e. Features Not to Be Tested:
List the features of the software/product which will not be tested.
Specify the reasons these features won’t be tested.
f. Approach:
Mention the overall approach to testing.
Specify the testing levels [if it’s a Master Test Plan], the testing types,
and the testing methods [Manual/Automated; White Box/Black Box/Gray Box]
g.Item Pass/Fail Criteria:
Specify the criteria that will be used to determine whether each test item
(software/product) has passed or failed testing.
h.Suspension Criteria and Resumption Requirements:
Specify criteria to be used to suspend the testing activity.
Specify testing activities which must be redone when testing is resumed.
i. Test Deliverables:
List test deliverables, and links to them if available, including the
following:
Test Plan (this document itself)
Test Cases
Test Scripts
Defect/Enhancement Logs
Test Reports
j.Test Environment:
Specify the properties of test environment: hardware, software, network etc.
List any testing or related tools.
h.Estimate:
Provide a summary of test estimates (cost or effort) and/or provide a link to
the detailed estimation.
i.Schedule:
Provide a summary of the schedule, specifying key test milestones, and/or
provide a link to the detailed schedule.
j.Staffing and Training Needs:
Specify staffing needs by role and required skills.
Identify training that is necessary to provide those skills, if not already
acquired.
k.Responsibilities:
List the responsibilities of each team/role/individual.
l.Risks:
List the risks that have been identified.
Specify the mitigation plan and the contingency plan for each risk.
m.Assumptions and Dependencies:
List the assumptions that have been made during the preparation of this plan.
List the dependencies.
n.Approvals:
Specify the names and roles of all persons who must approve the plan.
Provide space for signatures and dates. (If the document is to be printed)