You have designed a graphic user interface (GUI), which now needs to be black-bo

Question

You have designed a graphic user interface (GUI), which now needs to be black-box tested.

Post the following:

Describe a GUI you designed so that others can use it; do not allow them access to the programming (black-box testing).

Identify the functional software requirements for your GUI.

Perform functional tests on at least 2 other designer's GUIs to do the following:

Determine if the program operation matches the functional requirements.

Implement 2–3 of the following tests:

Test data should be representative of the real data sets.

Upper and lower limits (boundary analysis) for data ranges should be tested. These boundary tests should examine the boundary values and also values on either side of the boundaries.

Numeric data input should include zero and negative number tests.

Dates, currency, and other locale-specific inputs and outputs should be tested.

Provisions should be made to allow the tester to enter inputs based on experience and situations of normal program use.

Stress testing should be performed.

Crash testing should be included to determine what situations can cause execution errors in the program.

Provide at least 2 paragraphs of feedback for each program including the following:

Does it meet each of the software requirements?

Results of all functional testing

Any issues you found with the following:

graphic user interface itself

performance ability

capacity

Respond to at least 2 comments on your own GUI regarding either things you learned about your program or things you plan to fix or implement in the next version of it.

Explanation / Answer

Consider the login page with user name and password.

For example if it is a text box, this box should allow us to enter any kind of thing that may be characters. But the thing is this user name should allow us to enter any characters like space, special characters and any kind of stuff. So the test case even it should accept these things also button should be able to click, if you click on checkbox it shouldn’t check again if you click it should make a checkbox.

So here we got 4 GUI test cases to validate the GUI.

GUI testing: (GUI Test Cases)

Test Case 1:

“Username:” Text box should allow us to enter any data.

Precondition: verify the access to application.

Steps:

Attributes:

Textbox: input

Drop down: select

Links: Click

Checkboxes: Click

Radio button: Click

Frames: window with in window

Test Case 2:

Title: “Password:” Text box should allow us to enter any data.

Precondition: verify the access to application.

Steps:

Key words: GUI

Test case 3:

Title: “login” button should allow us to click the button.

Pre-C: execute Test Case2 & 1 before executing this

Steps:

Test Case 4:

Title: On clicking the “Forgot Password” link user should be navigated

Pre-C:

Steps:

Test Case 5:

Title: Check box “keep me logged in unless I log out” should allow us to perform action

Pre-C: Execute test case 1, 2 & 3 prior to this

Steps:

3.Actu R:

4.KW:

BOD(Brief Over view Document) little bit similar

Functionality testing: (Block Box testing) or login functionality

User Story: Login functionality

Detailed information

Cycle: April 2016 to March 2016

Functional Test Cases:

Title: Verify user can login without entering Password

Pre-Condition: Verify the access

Steps:

Ex R: User should not b able to login or Error message “Username or Password is invalid. Please try again.” Should be displayed

Ac Result: “Username or Password is invalid. Please try again.” is displayed / user is unable to login without entering the password.

QF test is a good test with a functional system and load test of the company quality for software best in Germany. It enables automated testing of java into publications and runs cross platform on windows, linux.

Related Questions

Navigate

• Browse (All)
• Browse Y
• Subjects

Integrity-first tutoring: explanations and feedback only — we do not complete graded work. Learn more.