Skip to content

Testing

Jump to bottom
Chadwick A. Spradling edited this page Mar 25, 2016 · 6 revisions

Unit Test Scenarios:

  1. Log in / out

    A. Entry into text boxes:

     + No username input, valid / invalid password

 + No password input, valid / invalid username

 + Valid username, valid / invalid password

 + SQL injection ’OR 1=1 --  into username, invalid password (sanitizing input?)

 + Input exceeding character limit for database storage

    B. Execute logout function then use back button in browser (clearing browser cache?)

    C. Log in with a browser. Log in with another browser.

     + If logged in with both browsers, log out with one and navigate to restricted page to current access level with the other

  2. Registering

    A. Pressing SUBMIT multiple times for one form

    B. Submitting blank fields

    C. Submitting SQL to erroneously edit database

    D. Register two accounts with username and password

  3. Delete Account

    A. Delete one of two accounts that have identical username and password

  4. File Upload

    A. Upload format: jpg, obj, docx, pdf, c, php, mp3, wav

    B. Upload php file and navigate to it via address bar (is php executed?)

    C. Upload very large file and abort midway through

    D. Upload very small file ; upload blank file

    E. Upload corrupt file and see how it’s displayed

    F. Submit form with no file

    G. Submit directory to be uploaded

    H. Select file to upload, delete file, then submit form with file that no longer exists

  5. Account Access Restriction

    A. Navigate via URL to page restricted to current access level

    B. Navigate via URL to page unrestricted to to current access level

  6. Site Search

    A. Enter blank search parameters

    B. Enter *, other SQL

    C. Enter relevant search parameters

    D. Enter nonsensical search parameters

Regression Testing Plan: Regression testing shall be performed individually by each participant in creation of new code with the following procedure: 1. Create a new account 2. Check integration of system with newly implemented addition 3. Cry if it fails.

Integration Testing Plan: Integrative testing shall be performed in conjunction with regressive testing. Integrative testing shall include assurance that the database, user interface, and mediating php performs in accordance with requirement fulfillment. At the discretion of the author of newly implemented code, any combination of unit tests may be performed in order to ascertain whether or not 1. newly implemented code has broken system functionality, system component functionality, or system-system functionality and 2. the system as a whole performs in accordance with requirement fulfillment.

Clone this wiki locally