Upgrade to remove ads
INF 115 Week 3
Terms in this set (24)
software testing goals:
to show the presence of errors in the software product, identifying the inputs that make the outputs to be different from those ones expected and specified.
software testing principles
the degree to which a system or component facilitates the establishment of test criteria and the performance of test to determine whether those criteria have been met
how hard it is to find faults in the software
how easy it is to observe the behavior of a program in terms of its outputs, effects on the environment and other hardware and software components
how easy it is to provide a program with the needed inputs, in terms of values, operations, and behaviors
does the software meet the requirement specification
are we building the software right?
does the system meet the user's real needs?
are we building the right software?
it represent the initial testing stage where the smallest, though functional, software units are tested
objective: to reveal failures in one small software part working independently from the whole system.
stage concerned with the software structure building, performing, at the same time, test to reveal failures in the interfaces
from the units (modules) previously tested, to build the program structure as it has been designed (described in the design model)
top-down integration testing
when you develop the project plan you must consider the way integration of components will happen in such way all needed components will e available in the right time.
bottom-up integration testing
integration eliminates the need for complex "stubs"
to execute, the system under the end user perspective, looking for failures in all functionalities and quality characteristics
testing should be executed in similar end user daily conditions (environment, systemic interfaces and amount of data)
changes in the software planning or testing planning will promote re-testing regardless the user testing strategy
represents an important strategy to reduce "side effects"
basically, for each new software version or development cycle, all previously applied test cases must be re-applied to the software
similar to exploratory testing
exercise most major functionality, ensure that everything still looks OK
questions such as:
- does the program compile
- does it run
- does the main window appear
- does it execute on the client's hardware and environment
it represents a formal testing performed to identify whether the system satisfies or not the acceptance criteria and to allow the stakeholders to say if they can accept or not the system.
criteria: the functionalities or other characteristics are in accordance with the requirements. Therefore, they can be accepted.
Acceptance Testing techniques -
alpha and beta testing
configuration review (acceptance testing)
assure all configuration software elements have been previously developed, catalogued and present the right level of detail to be used in the software life cycle
alpha and beta testing
performed by the client/stakeholder in the development environment
performed in the client/stakeholder installation by one or more end user
it consists in the installation of software in the end users places
focus: system's integrity and;
to verify if some functional/non-functional characteristics has been affected by the operational environment conditions
Software testing process
objective: to organize a set of activities to be executed during the software testing
software testing process roles
test managers, test designer, tester
a general document for the entire project defining the scope, approach to be taken, and schedule of test as well as identifying the items of test for the entire testing process and the personnel responsible for playing the different roles in the testing activities.
test units, features to be tested, testing approach
YOU MIGHT ALSO LIKE...
ISTQB Syllabus- Chapter 2
Software Testing Interview Questions
ISTQB: CTFL: Chapter 2 - Terminology
OTHER SETS BY THIS CREATOR
MGMT 107 CH10
MGMT 107 Week 8
MGMT 107 Chapter 9
chapter 7 processes, organziations and IS