This blog post contains the link to my power-point presentation on How to prepare a Internship Report for BScCSIT final semester of Tribhuvan University. You can download the slide here.
M.Sc. Graduate with research interest in Natural language processing, machine learning and pattern recognition.Currently Working as Lecturer at Central Department of Computer Science and IT in Tribhuvan University, Kathmandu.
Monday, December 31, 2018
Monday, August 27, 2018
How to Create a Test Plan and Test Cases: A Simplified View
Acknowledgement: Most of the content of this post are based on the Book " Advanced Software Project Management" by Andrew Stellman and Jennifer Greene. However Errors if any are due to me and I apolozie for them.
Fig: Sample format of Test Plan

The goal of test planning is to establish the list
of tasks which, if performed, will identify all of the requirements that have
not been met in the software.
The main work product is the test plan.
– The test plan documents the overall approach to the
test. In many ways, the test plan serves as a summary of the test activities
that will be performed.
– It shows how the tests will be organized, and
outlines all of the testers’ needs which must be met in order to properly carry
out the test.
– The test plan should be inspected by members of the
engineering team and senior managers.
– The bulk of the test planning effort is focused on
creating the test cases.
• A test case is a description of a specific
interaction that a tester will have in order to test a single behavior of the
software.
• Test cases are very similar to use cases, in that
they are step-by-step narratives which define a specific interaction between
the user and the software.
– A typical test case is laid out in a table, and
includes:
• A unique name and number
• A requirement which this test case is
exercising
• Preconditions which
describe the state of the software before the test case (which is often a
previous test case that must always be run before the current test case)
• Steps that
describe the specific steps which make up the interaction
• Expected Results which
describe the expected state of the software after the test case is executed
• Test cases must be repeatable.
– Good test cases are data-specific, and describe each
interaction necessary to repeat the test exactly.
• The requirement specified on chapter 6- how a search-and-replace function must deal
with case sensitivity. One part of that requirement said, “If the original text
was all lowercase, then the replacement
text must be inserted in all lowercase.”
Fig: Test Case Sample
Subscribe to:
Comments (Atom)
Blog Archive
-
►
2021
(1)
- ► 07/11 - 07/18 (1)
-
►
2019
(1)
- ► 05/19 - 05/26 (1)
-
►
2017
(24)
- ► 10/15 - 10/22 (1)
- ► 09/10 - 09/17 (1)
- ► 08/13 - 08/20 (1)
- ► 08/06 - 08/13 (1)
- ► 07/30 - 08/06 (4)
- ► 07/23 - 07/30 (4)
- ► 07/09 - 07/16 (1)
- ► 06/25 - 07/02 (1)
- ► 04/16 - 04/23 (1)
- ► 04/09 - 04/16 (1)
- ► 03/26 - 04/02 (1)
- ► 03/12 - 03/19 (1)
- ► 02/26 - 03/05 (1)
- ► 02/19 - 02/26 (4)
- ► 02/12 - 02/19 (1)
-
►
2016
(8)
- ► 08/14 - 08/21 (1)
- ► 07/31 - 08/07 (1)
- ► 05/22 - 05/29 (1)
- ► 04/24 - 05/01 (1)
- ► 02/28 - 03/06 (2)
- ► 02/14 - 02/21 (1)
- ► 01/31 - 02/07 (1)