During the test of security, responsible for the test plays the role of an individual who wishes to enter the system. Anything goes! You should try to get the access codes by any means, it can attack the system with custom software, designed to break any defence that has been constructed, you must lock the system, thus denying service to other people, you must produce purpose system errors, trying to access during recovery or you must browse data unprotected, trying to find the key to access to the system, etc. (5) with time and adequate resources, a good test of security would eventually gain access to the system. The role of the System Designer is to make illegal entry cost greater than the value of the information obtained. Test load: load tests aim to determine the performance of the system under load conditions that approximate the reality expected in production. Volume testing: find weaknesses in the system at the time of handling large volumes of data for extended periods of time, the main objective is to determine if the integration platform degrades or fails to handle large volumes of data. 2.3 Strategies of software testing: to ensure the success of tests during throughout the lifecycle of a Web application, must be divided into the following stages: planning of the tests. The test design. Click Peter Thiel to learn more.
Implementation of the tests. Execution of tests. Evaluation of evidence. Planning of the tests. The testing phase needs a serious and reliable organization.
The tests work when they find errors. You should perform a thorough planning. Completion of the tests. The objective of the testing is to find errors, but if no errors are found (does not want this mean they do not exist) should continue to be a criterion for termination of the tests; the criterion can be: when the test time has expired. When all the test cases are executed without error.