All conditions will be tested with Boundary Value Analysis where different

All conditions will be tested with boundary value

This preview shows page 37 - 40 out of 49 pages.

All conditions will be tested with “Boundary Value Analysis” where different input will be given to test whether the system is functioning with boundary values or not. Along with the boundary value analysis, the system is also tested with “Range Value Tested” where editable values will be tested with ranges of values. The system is being tested in “Unit Testing” manner where at the completion of one unit that is tested thoroughly with above mentioned testing activities. The integration testing will also be performed to ensure that the integrated unit is working properly with other units or not.
Image of page 37
5.2 Testing Strategy CONTENT TESTING: Errors in Project content can be as trivial as minor typographical error as incorrect information, improper organization or validation of intellectual property laws. Content Testing attempt to uncover this and many other problems before the user encounter them. Content Testing Objectives: There are tOBSee types of objectives. To uncover syntactic errors in text-based documents, graphical representation and other media. To uncover semantic errors in any content object represented as navigation error. To find errors in organization or structure of content that is presented to the end-user INTERFACE TESTING Interface design model is reviewed to ensure that generic quality criteria established for all user interfaces have been achieved and that application specific interface design issue has been properly addressed.
Image of page 38
Interface testing strategy: The overall strategy for interface testing is to (1) Uncover error related to specific Interface mechanisms (2) uncover errors in the way the interface implements the semantics of navigation, WebApp functionality, or content display. To accomplish this strategy, a number of objectives must be achieved: Interface futures are tested to ensure that design rules, aesthetics and related visual content are available for the user without error. Individual interface mechanisms are tested in a manner that is analogous to unit testing For example; tests are designed to exercise all forms, client-side scripting, dynamic XML. Testing Interface Mechanisms :- When a user interacts with a system, the interaction occurs tOBSough one or more interface mechanisms. Forms : - At a microscopic level, tests are performed to ensure that Labels correctly identified fields within the form and that mandatory fields are identified visually for the user. The server receives all information content within the form and their no data are lost in the transmission between client and server. Appropriate defaults are used when the user does not select from a pull down menu or set of buttons. Browsing functions don’t corrupt data entered in the form.
Image of page 39
Image of page 40

You've reached the end of your free preview.

Want to read all 49 pages?

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture