Scribd
Upload
75 views

Software Testing 8

System testing involves testing a software system in its operational environment to evaluate its performance, reliability, and other quality attributes. Key aspects of system testing include testing performance under different loads, volumes of data, number of users, security, localization, usability, recovery from failures, documentation, compatibility with different configurations, and reliability over time. Various types of testing are done including performance, volume, stress, security, localization, usability, recovery, documentation, configuration, compatibility, and regression testing.

Uploaded by

vinitajenny
Copyright
© Attribution Non-Commercial (BY-NC)
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
75 views

Software Testing 8

System testing involves testing a software system in its operational environment to evaluate its performance, reliability, and other quality attributes. Key aspects of system testing include testing performance under different loads, volumes of data, number of users, security, localization, usability, recovery from failures, documentation, compatibility with different configurations, and reliability over time. Various types of testing are done including performance, volume, stress, security, localization, usability, recovery, documentation, configuration, compatibility, and regression testing.

Uploaded by

vinitajenny
Copyright
© Attribution Non-Commercial (BY-NC)
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
You are on page 1/ 20

System Testing

• Test the software in the real environment in which it is to


operate. (hardware,people,information,etc.)

• Observe how the system performs in its target environment,


for example in terms of speed, with volumes of data, many
users, all making multiple requests.
System Testing
• Test how secure the system is and how can the system recover
if some fault is encountered in the middle of procession

• System Testing, by definition, is impossible if the project has


not produced a written set of measurable objectives for its
product.
System Testing
Types of System Testing
– Performance
– Volume
– Stress
– Security
– Localization
– Usability
– Recovery
– Documentation
– Configuration
– Compatibility
– Reliability
– Installation
Performance Testing
• Many Programs have specific performance or efficiency
objectives like response time & throughput rates under certain
workload & configurable conditions.
• Necessary to measure the resource utilization (e.g processor
cycles).
• Tested under a variety of operating conditions, configurations
and loading.
Performance Testing
• To ensure that the system is responsive to user interaction
and handles extreme loading without unacceptable operational
degradation.
• To test response time and reliability by increased user traffic.
• To identify which components are responsible for
performance degradation and what usage characteristics cause
degradation to occur.
Volume Testing

• Tests the performance & behavior of software under large


volume of data in the database.
• In Volume Testing - Application response time, & general
performance parameters can be checked.
Load Testing

Following variables define a set of test conditions


• N, the number of concurrent users
• T, the number of on-line transactions per user per unit time
• D, the data load processed by the server per transaction
Stress Testing

• In Stress testing a considerable load is generated as quickly as


possible in order to stress the application and analyze the
maximum limit of concurrent users the application can
support.
• Stress tests executes a system in a manner that demands
resources in abnormal quantity,frequency, or volume.
Stress Testing
Tests should answer the following questions
• Does the system degrade gently or does the server shut down?
• Are appropriate messages displayed ? – Server not available.
• Are transactions lost as capacity is exceeded?
• Are certain functions discontinued as capacity reaches the 80
or 90 percent level?
Security Testing

• Security Testing verifies that protection mechanisms built into


the system will protect it from improper penetration.
• Security testing is the process of executing test cases that
subvert the program’s security checks.
• Test cases should be designed to exercise firewalls,
authentication, encryption and authorization
Localization Testing

• Localization translates the product UI and occasionally changes


some settings to make it suitable for another region
• The test effort during localization testing focuses on
– Areas affected during localization, UI and content
– Culture/locale-specific, language specific and region
specific areas
Usability Testing- Human
Computer Interactions

Usability is
• The effectiveness, efficiency and satisfaction with which
specified users can achieve specified goals in a particular
environment ISO 9241-11
• Effective–- Accomplishes user’s goal
• Efficient-- Accomplishes the goal quickly
• Satisfaction–- User enjoys the experience
Usability Testing- Human
Computer Interactions
Test Categories and objectives

- Interactivity ( Pull down menus, buttons)


- Layout
- Readability
- Aesthetics
- Display characteristics
- Time sensitivity
- Personalization
Usability Testing- Human
Computer Interactions

• Using specialized Test Labs a rigorous testing process is


conducted to get quantitative and qualitative data on the
effectiveness of user interfaces
• Representative or actual users are asked to perform several
key tasks under close observation, both by live observers and
through video recording.
• During and at the end of the session, users evaluate the
product based on their experiences
Recovery Testing
• A system test that forces the software to fail in variety of ways
, checks performed
- recovery is automatic ( performed by the system itself)
- reinitialization
- checkpointing mechanisms
- data recovery
- restarts are evaluated for correctness
Documentation Testing

• This testing is done to ensure the validity and usability of the


documentation
• This includes user Manuals, Help Screens, Installation and
Release Notes
• Purpose is to find out whether documentation matches the
product and vice versa
• Well-tested manual helps to train users and support staff
faster
Configuration test
• Attempts to uncover errors that are specific to a particular
client or server environment.
• Create a cross reference matrix defining all probable operating
systems, browsers, hardware platforms and communication
protocols.
• Test to uncover errors associated with each possible
configuration
Regression Testing

• Regression Testing is the testing of software after a


modification has been made to ensure the reliability of each
software release.

• Testing after changes have been made to ensure that changes


did not introduce any new errors into the system.
Regression Testing
• It applies to systems in production undergoing change as well
as to systems under development.
• Re-execution of some subset of test that have already been
conducted.
• Test suite contains
- Sample of tests that will exercise all software functions
- Tests that focus on software functions that are likely to be

affected by the change


- Tests for software components that have been changed
User Acceptance Testing
• A test executed by the end user(s) in an environment
simulating the operational environment to the greatest
possible extent, that should demonstrate that the developed
system meets the functional and quality requirements

• Not a responsibility of the Developing Organization.

You might also like