Security Testing

Tags:

There are two forms of integration: Integrating non-incremental: all modules are combined in advance and test the whole program together. Incremental Integration: The program is built and tested in small segments. System Test: Check that each item fits properly and that it reaches the functionality and overall system performance. The test system consists of a series of different tests whose primary purpose is to exercise deep computer-based system. Tests Regression: Regression testing is a testing strategy in which the tests have been conducted previously are re-done in the new amended, to ensure quality after adding the new functionality. The purpose of these tests is to ensure that: The shortcomings identified in the previous execution of the test are corrected.

The changes made have not introduced new defects or re previous defects. Security Testing Security testing attempts to verify that protection mechanisms built into the system will protect, in fact, improper access. Of course, security of the system should be tested in their invulnerability against a frontal attack, but also should be tested in their resistance against attack from the flanks or rear. During the safety test, the head of the test plays the role of an individual who wishes to enter the system. Anything goes! You should try to get the passwords by any means, can attack the system with custom software, designed to break any defense that has been built to block the system, thereby denying service to others, you must cause system errors on purpose, trying to access during recovery or should pry into the unprotected data, trying to find the key system access, etc..

Adequate time and resources, good safety test would eventually enter the system. The system designer’s role is to make the cost of illegal entry is greater than the value of information obtained. Load Testing: The goal of load testing is to determine system performance under load conditions that approximate the expected reality in production. Volume Testing: Finding weaknesses in the system when handling large volumes of data over extended periods of time, the main objective is to determine if the integration platform breaks down or stops working to handle large volumes of data. 2.3 Software Testing Strategies: To achieve the success of the trials during entire life cycle of a Web application, must be divided into the following stages: Planning of the tests. Design of the tests. Implementation of evidence. Implementation of evidence. Evaluation of evidence. Planning Tests. The test phase needs a serious and trustworthy organization. The tests work when they find errors. Planning must be comprehensive. Completion of Tests. The aim of the tests is to find errors, but if no errors are found (this does not mean they do not exist) should follow a termination criterion of testing, the criterion can be: When the test time has expired and all test cases run without error.