non functional, usability testing

11
Non Functional Testing Day7

Upload: it-online-training

Post on 24-Jul-2015

18 views

Category:

Education


4 download

TRANSCRIPT

Page 1: Non functional, usability testing

Non Functional Testing

Day7

Page 2: Non functional, usability testing

Non-Functional Testing

• Once Functionality of the application is stable, Test Engineers concentrate on non functional aspects.

• There is separate requirements for Non Functional Testing.

Page 3: Non functional, usability testing

Types of Non-Functional Testing Performance testing

Load Testing Stress Testing

Security Testing Authentication Access Control

Recovery Testing Compatibility Testing

Backward/Forward Compatibility OS Compatibility Browser Compatibility (Cross Browser Testing) H/W Compatibility

Configuration Testing Installation Testing Sanitation Testing (Garbage Testing)

Page 4: Non functional, usability testing

Performance Testing

• During performance testing , Test Engineers validate speed of the transaction w.r.t requirement.

• Load – Load means Number of users.– Increasing the load of users and trying to do same

transaction.– Testing an application by simulating real world traffic with

customer accepted load. • Stress

– Increasing/Decreasing the load simultaneously. – Stress testing is to determine the breaking point of the

application under intense conditions

Page 5: Non functional, usability testing

Security Testing

• During Security Testing , Test Engineers tests How secure application is from Un authorized Users or Permissions.– Authentication - Checking application with valid

and invalid users.– Access Control – Checking Permissions of valid

users.• Encryption/Decryption

Page 6: Non functional, usability testing

Recovery Testing

• Testing whether application recover from abnormal state to normal state.– Normal state---> Power-off--> abnormal--> Power-

on --> normal state

Page 7: Non functional, usability testing

Compatibility Testing• Compatibility is to check whether software is capable of running

on different hardware, operating systems or applications. • Backward /Forward compatibility

– Support of older/newer versions of OS ,Hardware Environments.• OS Compatibility

– Support of OS platforms like Windows, Unix ,Linux etc.• Hardware Compatibility

– Support of Hardware Environment ( RAM, Processor ..)– Also called as Configuration Testing

• Browser compatibility(Web based)– Support of browsers (IE, Chrome, Firefox etc...) – Also called as Cross browser testing

Page 8: Non functional, usability testing

Configuration Testing

• The combination of OS compatibility & H/W Compatibility testing.

Page 9: Non functional, usability testing

Installation Testing

• During Installation Testing , Test Engineers validate the following.– Installation process– Installation screens are understandable– Installation space– Un-installation - All the installed files should get

removed.

Page 10: Non functional, usability testing

Sanitation (Garbage) Testing• Testing the application whether it is providing

additional functionality apart from customer requirements.

Page 11: Non functional, usability testing

Usability Testing

• Also called as User Support Testing.• During this testing validates application

provided context sensitive help or not.• Validates User Manuals.