System Testing

System Testing: -
After completion of integration testing, a separate testing team receives a
software build from the development team. This team a set of block box testing
techniques to validate that software build the system testing is satisfied into 3
categories.
1. Usability testing
2. Functional Testing
3. Non Functional Testing
1.Usability Testing:
In general, the separate testing team starts test execution with usability
testing. During this test, the team concentrates on user-friendliness of the software
build screens. The usability testing consists of 2 sub tests.
a) User  Interface Testing
b) Manuals Support Testing
a) User - interface Testing: -
In User Interface Testing software build is tested for
‰ Ease of use (Understandability)
‰ Look & Feel (Attractiveness)
‰ Speed in Interface (Short navigations)
These are applied on every screen in the software build.
b) Manuals Support Testing: -
Also known as Help - documents testing. During this test, the
testing team concentrates on correctness & completeness of Help  Documents /
User Manuals.




2. Functional Testing:

A Moderator testing level during which the testing team
concentrates on customer requirements interms of functionality. During this test,
the testing team applies below sub-tests on the software build.
i) Functionality Testing
ii) Sanitation Testing
i) Functionality Testing: -
During this test, the testing team concentrates on correctness of
every functionality with respect to requirements. In this test, the testing team
follows the below coverage.
‹ GUI Coverage / Behavioral Coverage
(Changes in Properties of Objects in Screen)
‹ Error Handling Coverage
(Preventing incorrect Operations)
‹ Input Domain Coverage
(Taking correct size & type of Inputs)
‹ Manipulations Coverage
(Returning correct output)
‹ Backend Coverage
(The Impact of front-end screens operations on backend tables)
‹ Order of functionalities Coverage
ii) Sanitation testing: -
This is also known as Garbage Testing. During this test, the testing team
identifies extra functionalities in the software build with respect to customer
requirements.
3. Non-Functionality Testing:
A complex level in system testing during which the testing team
concentrates on extra characteristics of the software.
i. Recovery Testing
ii. Compatibility Testing
iii. Configuration Testing
iv. Inter system Testing
v. Installation Testing
vi. Load Testing
vii. Stress Testing
viii. Data Volume Testing
ix. Parallel Testing



Comments

Post a Comment

Popular posts from this blog

Handling of Skew

Handling of Skew ô€‚„ The distribution of tuples to disks may be skewed — that is, some disks have many tuples, while others may have fewer tuples. ô€‚„ Types of skew: ô€ƒŒ Attribute-value skew. ô€‚¾ Some values appear in the partitioning attributes of many tuples; all the tuples with the same value for the partitioning attribute end up in the same partition. ô€‚¾ Can occur with range-partitioning and hash-partitioning. ô€ƒŒ Partition skew. ô€‚¾ With range-partitioning, badly chosen partition vector may assign too many tuples to some partitions and too few to others. ô€‚¾ Less likely with hash-partitioning if a good hash-function is chosen. Handling Skew in Range-Partitioning ô€‚„ To create a balanced partitioning vector (assuming partitioning attribute forms a key of the relation): ô€ƒŒ Sort the relation on the partitioning attribute. ô€ƒŒ Construct the partition vector by scanning the relation in sorted order as follows. ô€‚¾ After every 1/nth of the relation has been read, the value...
Read more

Fragment-and-Replicate Join

Fragment-and-Replicate Join ô€‚„ Partitioning not possible for some join conditions ô€ƒŒ e.g., non-equijoin conditions, such as r.A > s.B. ô€‚„ For joins were partitioning is not applicable, parallelization can be accomplished by fragment and replicate technique ô€ƒŒ Depicted on next slide ô€‚„ Special case – asymmetric fragment-and-replicate: ô€ƒŒ One of the relations, say r, is partitioned; any partitioning technique can be used. ô€ƒŒ The other relation, s, is replicated across all the processors. ô€ƒŒ Processor Pi then locally computes the join of ri with all of s using any join technique. ô€‚„ General case: reduces the sizes of the relations at each processor. ô€ƒŒ r is partitioned into n partitions,r0, r1, ..., r n-1;s is partitioned into m partitions, s0, s1, ..., sm-1. ô€ƒŒ Any partitioning technique may be used. ô€ƒŒ There must be at least m * n processors. ô€ƒŒ Label the processors as ô€ƒŒ P0,0, P0,1, ..., P0,m-1, P1,0, ..., Pn-1m-1. ô€ƒŒ Pi,j computes the join of ri with sj. In ...
Read more

USER INTERFACE DESIGN FOR ANNA UNIVERSITY SYLLABUS

Unit – I Introduction Objective To Understand the definition and importance of User Interface Design To know about the concept, advantages and applications of GUI and Web interface User Interface Design Definition • User interface design is a subset of a field of study called human-computer interaction (HCI). Human-computer interaction is the study, planning, and design of how people and computers work together so that a person’s needs are satisfied in the most effective way. • The user interface is the part of a computer and its software that people can see, hear, touch, talk to, or otherwise understand or direct. The user interface has essentially two components: input and output. • Input is how people communicate his needs to the system using keyboard or any pointing device and output is how the system returns processing result to user through screen or sound. • The best interface is one which has proper design with combination of effective input and output mechanisms. Importance of...
Read more