|
Software Testing Methods
Part:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
(Continued from previous part...)
System-Level Test
System-level tests consists of batteris of tests that are designed to fully exercise a program as a whole and check that all elements of the integrated system function properly.
Functional System Testing
System tests check that the software functions properly from end-to-end.
The components of the system include: A database, Web-enable application software modules,
Web servers, Web-enabled application frameworks deploy Web browser software, TCP/IP networking
routers, media servers to stream audio and video, and messaging services for email.
A common mistake of test professionals is to believe that they are conducting system tests while
they are actually testing a single component of the system. For example, checking that the Web server returns a page is not a system test if the page contains only a static HTML page.
System testing is the process of testing an integrated hardware and
software system to verify that the system meets its specified requirements.
It verifies proper execution of the entire set of application components
including interfaces to other applications. Project teams of developers and
test analysts are responsible for ensuring that this level of testing is performed.
System testing checklist include question about:
- Functional completeness of the system or the add-on module
- Runtime behavior on various operating system or different hardware
configurantions.
- Installability and configurability on various systems
- Capacity limitation (maximum file size, number of records, maximum
number of concurrent users, etc.)
- Behavior in response to problems in the programming environment
(system crash, unavailable network, full hard-disk, printer not ready)
- Protection against unauthorized access to data and programs.
"black-box" (or functional) testing
Black Box Testing is testing without knowledge of the internal workings of the
item being tested. The Outside world comes into contact with the test items,
--only through the application interface ,,, an internal module interface, or
the INPUT/OUTPUT description of a batch process.
They check whether interface definitions are adhered to in all situation and
whether the product conform to all fixed requirements. Test cases are created based
on the task descriptions.
Black Box Testing assumes that the tester does not know anything about the application
that is going to be tested. The tester needs to understand what the program should do,
and this is achieved through the business requirements and meeting and talking with users.
Funcional tests: This type of tests will evaluate a specific operating condition using
inputs and validating results. Functional tests are designed to test boundaries. A combination
of correst and incorrect data should be used in this type of test.
Scalability and Performance Testing
Scalability and performance testing is the way to understand how the system will handle the load cause by many concurrent users. In a Web environment concurrent use is measured as simply the number of users making requests at the same time.
Performance testing is designed to measure how quickly the program
completes a given task. The primary objective is to determine whether
the processing speed is acceptable in all parts of the program.
If explicit requirements specify program performance, then performance test
are often performed as acceptance tests.
As a rule, performance tests are easy to automate. This makes sense above
all when you want to make a performance comparison of different system
conditions while using the user interface. The capture and automatic replay
of user actions during testing eliminates variations in response times.
This type of test should be designed to verify response and excution time.
Bottlenecks in a system are generally found during this stage of testing.
(Continued on next part...)
Part:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
| 