Software Testing and Implementation Guide
Translated by
ScribdTranslationsSoftware Testing and Implementation Guide
Translated by
ScribdTranslationsENGINEERING OF
SOFTWARE
TEAM 4:
• CortesEscobedoFelixdeJesus
• VILLANUEVA EPIGMENIO KARLA ESTEFANIA
THEMEIV:
TESTING AND IMPLEMENTATION
4.1 Test case design
4.2 Component Testing
4.3 System Tests
4.4 Documentation of test results
4.5 System delivery and user training
4.6 Delivery of technical and user documentation of the system
FUNDAMENTALS OF THE
SOFTWARE TESTING
The goal of testing is to find errors, and a good test is one that has
a high probability of finding one. Therefore, a system based on
A computer or a product must be designed and implemented with the mind on the
"probability." At the same time, the tests themselves must show a
set of characteristics that achieve the goal of finding the highest number of
errors with minimum effort.
4.1 TEST CASE DESIGN
In software engineering, through the test case, the analyst
it will determine whether an application or a feature of it is partial or
completely satisfactory.
To carry out a test case, it is necessary to define the following steps:
Define scenarios.
Identify entry conditions
• Definir clases de equivalencia
• Execute test cases
4.2 COMPONENT TESTING
These types of tests are normally executed by the development team.
they basically consist of carrying out activities that allow you to verify
developer that the unit components are coded under conditions
of robustness, that is, supporting the entry of erroneous or unexpected data and
thus demonstrating the ability to handle errors in a controlled manner.
Additionally, tests on unit components are usually referred to
module tests or class tests. Finally, it is important that all the
the functionality of each unit component is covered by at least two
test cases, which must focus on testing at least one functionality
a positive and a negative.
4.3 SYSTEM TESTING
Why try?
Software failures cause serious
economic losses; these range from 100 to 1000
times more expensive to find and repair
after the construction.
Avoid missed deadlines and budgets,
dissatisfaction and poor quality in software
produced and finally the loss of customers.
Automating the testing process achieves
reductions of up to 75% in the cost of the
maintenance phase
WHO SHOULD TEST
WHAT SHOULD BE TESTED?
•Each test case must define the expected output result
•The programmer should avoid testing their own programs, as they want to
(consiente o inconscientemente) demostrar que funcionan sin problemas.
•Each test result must be carefully inspected, thus, to be able
discover possible symptoms of defects.
•When generating test cases, both valid input data and
expected as invalid and unexpected.
•The tests should focus on two objectives:
•Test if the software does not do what it is supposed to do.
•Try to see if the software does what it shouldn't do, that is, if it causes
adverse side effects.
4.4 DOCUMENTATION OF
TEST RESULTS
Documentation is usually classified based on the people or groups to whom it is addressed.
who it is directed to:
Documentation for developers
User documentation
Documentation for administrators or technical support
The documentation for developers is that which is used for the developer themselves.
product development and, above all, for its future maintenance. It
documentation to communicate the structure and behavior of the system or of its
parts, to visualize and control the system architecture, to understand
better the same and to control the risk, among other things. Obviously, the more
the more complex the system, the more important the documentation is.
•User documentation is everything that a user needs.
user for the installation, learning and use of the product.
It can consist of installation guides, user guides,
reference manuals and message guides. A large part of the
Documentation for users can begin to be generated.
since the system requirements study begins.
•The documentation for administrators or technical support, to
sometimes called the operations manual, contains all the
information about the finished system that does not make use of
an end user. It is necessary to have a description of the
possible system errors, as well as the procedures for
recovery.
4.5 DELIVERY OF SYSTEM
TRAININGFORUSERS
They are all the activities necessary to convert the old system to the new system.
The adaptation of the current system or the implementation of a new system entails
modifications in the business processes of the company or organization, which may impact
the business results. That is why it is extremely important to plan adequately the
change processes. A successful implementation does not guarantee (by itself) improvement.
from the organization using the new system, but inadequate installation will prevent it.
Computer Equipment. The implementation of a new system can bring along the
incorporation of new computer equipment, changes and improvements in hardware.
Physical Facilities (Physical changes, of the building, of the environment).
System analysts are involved in an educational process with users that is
called training. Throughout the system development life cycle, users have
state involved, so now the analyst must have an appropriate assessment of the
users who need to be trained. All individuals who will have primary or secondary use
The system must be trained. This includes everyone, from data capture personnel
even those who would use the output to make decisions without personally using one.
computer.
4.6 DELIVERY OF
TECHNICAL DOCUMENTATION
SYSTEM USER
The Project Team must incorporate the generated documentation associated with
the delivery in the reserved workspace in the document manager. The space
work associated with the project should have been created at the start of the project,
using the previously defined templates for each type of project.
Once the delivery (software and documentation) has been made, the Project Manager
You must communicate it to the Project Manager so that they can begin the review.
of the delivery.
The Project Technical Director or the Project Manager shall, in
First, check that all products are available.
requested. Secondly, you should review the documentation
delivered, ensuring that the agreed objectives are met.
Finally, you must communicate the result of the review to the Chief of
Testing Project or Team as applicable.
The testing team will conduct the corresponding tests for each
one of the agreed services. In case of detecting
nonconformities, will record the appropriate defects. In addition,
will prepare a final report with the results of the tests
carried out. In case of a blockage situation, it will be updated.
Delivery request to communicate the resubmission proposal.
it will consider a blockage situation when testing detects errors in
the execution of one of the basic services, which will prevent the
provision of the remaining agreed services.
PLAN OF
TESTS
DE
SOFTWARE
PLAN OF
TESTS
DE
SOFTWARE
PLAN OF
TESTS
DE
SOFTWARE