Oct 3, 2016 - - SDM Unit Test Scenario Checklist Last Update:. Casualties Zip Hoodie. Basic and other Single-Threaded Apartment (STA) objects (including Scripting.Dictionary) are used only at page scope. 52, Variables are declared within subroutines or functions only (no global variables). 53, Performance. 0 5/30/00 Test Plan (Unit and Integration) Template and Checklist Rev. Establishes testing schedules, and identifies. 2.0 TEST DEFINITION.
A Unit testing is a where smallest part of individual unit / component (called unit) is tested to determine if they are fit for use. The unit test cases writing and execution is done by the developer (not the tester) to make sure that individual units are working as expected. The smallest part of individual components like functions, procedures, classes, interfaces etc. If we take a example of functions, when we pass input parameters to functions then check if the function should return a expected values. The main intention of this activity is to check whether units are working as per design and handling error and exception more neatly.
The both positive and negative conditions should handle properly. The white box testing is used to test the unit testing. This is very first step in level of testing and started before doing integration testing. Unit Testing Test Case Preparation Guidelines: 1. Unit Test Plan/Cases should be made a separate deliverable. It should not be merged with other artifacts. Try to document all the probable test scenarios which encompasses uncommon and alternative flows.
Once a project moves into construction phase, the developers have a tendency to catch only the success situations or the situations which has been coded. Construction and Unit testing need to be made distinct phases and the deliverable need to be scheduled accordingly. 3. If Construction and UT are scheduled as a single phase, Unit testing results need to be made as a separate deliverable – This would help in filtering out any mistakes in the business flows at a nascent stage instead of in the integration testing or system testing which is more expensive. 4. Make use of the count of test cases planned, executed, passed, and failed to apprehend the progress and replicate Unit testing if required. 5. Try to include on-the-fly test cases that are developed while executing a pre-defined set of test cases. Unit Testing Test Cases Preparation Guidelines Checklist: Input Data Validation: This section encompasses a range of checks that may be adopted generally to the data which is entered to an application system.
Security: This constitutes of a set of conditions which helps to verify the security of an application system. • Negative testing- Password is not visible • Access testing- multiple levels • Positive testing- Change Password • Error messages should not reveal any system information • Check if SSL is correctly deployed • Check if Lockout rules is applied • Check if password saved in clear or encrypted? • Verify the application with valid UserId and invalid UserIds • Verify the application with valid password and various invalid passwords • Check for access to the application by directly entering valid URL(s). System should ask for login details. • Ensure Browser(s) does not remember Passwords Logging, audit and trails: This constitutes of a set of conditions which helps to verify the Audit Trails, System Logs, etc. Of an application system. • Check if the logs are saved for the specified period • Check if the logs contain personal data • Check if Admin functions are logged • Check if user Lockout events are logged Business application logic: This constitutes of a set of conditions which helps to verify the application logic and business processing of an application system.