INPUT SCREENS

1)         THE LOGIN PAGE:

The login page may as well have fields for example Login ID and Password. 

2)         THE REGISTRATION FORM:

The Registration shape might as well have fields for example Login id, Password, Confirm Password, Name, Age, Group send-id and so on. for every bunch of understudies showing up for the test. 

3)         THE TEST START MODULE:

This module may as well furnish the guidelines and regulations to show up for test. 

4)         THE STUDENT SHORTLISTING MODULE:

This module may as well have fields similar to the person name, the bunch code, educator’s name and the undertaking code.

5)         ABOUT THE DEVELOPERS:

6)         CONTACT THE DEVELOPERS: 

THE ADMINISTRATION MODULE:

1)         THE QUESTION ANSWER FORM:

This shape might as well have fields for example Question id, Question, alternatives and so forth. 

2)         THE ADMIN USER MASTER:

This module may as well have fields as User id, User Login name, User Password,

User name, User message-id and so on., all informative data identified with admin. 

3)         THE UTILITIES MODULE:

This module may as well furnish choices to prepare the user to pilot to the Home page, about us, logout and passageway. 

OUTPUT SCREENS::

1) THE VIEW PROFILE MODULE:

This module might as well furnish a view of the enlisted user. The login id, user

Name id, Name, message id, Percentage, Group id and so forth. 

2) THE EDIT PROFILE MODULE:

The Edit profile module might as well have fields for example Login id, Password,

Affirm Password, User name. One can make updates to the information dropped in. 

3)         THE EDIT PASWORD MODULE:

The user can update its watchword through this module. 

4)         THE TESTING MODULE:

This module might as well showcase the time needed to sit down for a bit, time left for the test to get over, length of time of exam. 

Test-Plan (TP)

The test-idea is fundamentally a catalogue of test cases that require to be run on the framework. Some of the test cases might be run autonomously for certain segments (report crop from the database, for instance, might be tested autonomously) and some of the test cases need the entire framework to be available for their execution. It’s preferred to test every segment as and when its primed before joining the parts.