Create a web application

The same holds true for a web application.

Of course you will be placing screenshots in your final document which is fine. Inclusion of a running application and/or a URL that runs your application or website is far,far, far, far better.

Dr. Elliott

I have started the writing of testing, not sure it makes a lot of sense just yet. I am continuing to build a strong tests procedure. 

Vulnerability testing is the most difficult one while you are testing your final product before implementation. While doing useful testing it is conceivable to make exchange offs in assets and scope. As a major aspect of the arranging stage, the test investigator can limit the extent of testing by concentrating on those parts of the application that are most basic from a business perspective, in addition to those that are generally much of the time utilized. A trapdoor can may cause obscure for a compromising application.

While performing the testing it is considered either the application will continue its application while going through testing or not?  A security analyzer, then again, must consider all the ways that a client may resolutely harm the application under test. Normally, these outcomes in a complex increment in the quantity of regions that will be considered and taken under consideration in security testing.

Black Box Testing

Discovery test exercises all around include the utilization of instruments to help analyzers distinguish potential security vulnerabilities inside a framework. Among the current accessible toolsets, there are subsets of apparatuses that concentrate on particular regions, including system security, database security, security subsystems, and web application security.

White Box Testing

White box testing obliges access to the source code. Despite the fact that white box testing can be played out whenever in the life cycle after the code is produced, it is a decent practice to perform white box testing amid the unit testing stage.

White box testing requires realizing what makes programming secure or uncertain, how to think like an aggressor, and how to utilize diverse testing instruments and methods. The initial phase in white box testing is to appreciate and examine accessible plan documentation, source code, and other important advancement antiques, so recognizing what makes programming secure is a crucial necessity. Second, to make tests that adventure programming, an analyzer must think like an assailant.

Professor’s Comments

While you have listed several testing methodologies, are these the only ones that you will employ?

Apparatuses distinguish security vulnerabilities in particular subsystems. While the beforehand examined apparatuses are utilized after the framework has been produced, these instruments are utilized amid the execution cycle to test whether security-basic subsystems have been planned and actualized appropriately. For instance, these instruments test for right operation of arbitrary number generators (e.g., NIST Statistical Test Suite for irregular number era), cryptographic processors, and other security-basic part

User Acceptance Testing

“The acceptance test suite may need to be performed multiple times, as all of the test cases may not be executed within a single test iteration”. (Acceptance Testing, 2016)

The acceptance test suite is run utilizing predefined acknowledgment test strategies to guide the analyzers which information to utilize, the well-ordered procedures to take after and the normal outcome taking after execution.

What other testing do you recommend? I still have to figure out what other companies have used that were unsuccessful with testing or if the testing failed where did the project go wrong.

Techopedia explains Cloud Testing

Cloud computing poses some challenges, such as manageability, reliability and security. Generally, organizations document a test strategy prior to actual cloud testing.  Key cloud testing elements include:

· Identifying relevant testing types

· Understanding cloud characteristics and conducting a risk/challenge analysis

· Setting up a cloud testing environment

· Simulating real-world challenges by selecting the right testing strategy

Cloud models such as software as a service (SaaS), platform as a service (PaaS) and infrastructure as a service (IaaS) are key cloud testing strategy components.  Cloud testing strategy components include:

· Performance and Load Testing (longevity testing): Ensure that a cloud solution meets business requirements specific to cloud computing

· Stress Testing and Recovery Testing: Ensure data recovery after a hardware crash

· Security Testing: Ensures that a cloud solution meets data security requirements

· System Integration Testing (SIT): Covers functional aspects

· User Acceptance Testing (UAT): Ensures that the cloud solution meets the documented needs of the business.

· Interoperability and Compatibility Testing: Ensures cloud service and vendor migration