Halliburton Testing Exercise - GigaChat

Get Started. It's Free
or sign up with your email address
Rocket clouds
Halliburton Testing Exercise - GigaChat by Mind Map: Halliburton Testing Exercise - GigaChat

1. Test Techniques

1.1. Functional Testing

1.1.1. Run

1.1.1.1. Subsequent Runs

1.1.1.1.1. Recall data/cache (or clear up each start)?

1.1.1.2. First Run

1.1.1.2.1. Initial data creation

1.1.2. Private Chat feature

1.1.2.1. Is this available all the time?

1.1.2.2. Is this a "premium" feature, that must be unlocked for only certain licenses?

1.1.2.3. Does the Private Chat feature use encryption?

1.1.2.4. Does private chat history get logged?

1.1.3. Chat module ("Simple Chat with WCF" window)

1.1.3.1. Basic Functions

1.1.3.1.1. Action Menu

1.1.3.1.2. Main activity window/chat log (top-left panel)

1.1.3.1.3. User List (top-right panel)

1.1.4. Do user levels exist (e.g. admin, mods, generic chatter, observer, etc.)

1.2. Domain Testing

1.2.1. Chat server IP entry limitations?

1.2.1.1. Alpha

1.2.1.2. Numeric

1.2.1.2.1. Limited octets (0-255)

1.2.2. DOC: "Don’t delete or manually edit any file under ChatServer folder"

1.2.2.1. Why? What happens if I...

1.2.2.1.1. ...Modify them?

1.2.2.1.2. ...Delete them

1.2.2.1.3. ...Move them

1.2.2.2. If clients have access to this, then can we better protect these files somewhere else? (let's remove the sharp stick)

1.2.2.2.1. Perhaps in a container?

1.2.3. Usernames and Passwords are stores in clear text

1.3. Stress Testing

1.4. Flow Testing

1.5. Scenario Testing

1.5.1. Single-user

1.5.1.1. Public chat in main channel

1.5.1.2. Private chat with self (possible?)

1.5.2. Two users

1.5.2.1. Public chat in main channel

1.5.2.2. Private chat (A to B)

1.5.2.3. Private chat (B to A)

1.5.3. Limit users (1,000?)

1.5.3.1. Public chat in main channel (as multiple users)

1.5.3.2. Private chat with individual users

1.5.3.3. Private chat with multiple users (possible?)

1.6. Claims Testing

1.7. User Testing

1.8. Risk Testing

1.8.1. Unhandled Exception is thrown if the server process is terminated during an active chat session (may be as designed, but UX expectations of many chat users these days may require friendly error message notification/UI be created)

1.9. Automatic Checking

2. Quality Criteria

2.1. Capability

2.1.1. Sign-up process

2.1.1.1. Web based?

2.1.1.2. Local credentials (DB)?

2.1.1.3. Username limitations (e.g. no special chars?)

2.1.1.4. Password limitations (e.g. no special chars?)

2.1.1.5. The sign-up process appears and allows user entry, even when the server is not running. Is this normal/expected behavior or should we prompt the user for server start before they spend the time attempting to sign-up?

2.1.2. Users are allowed to send blank messages (this may be as designed, but is inconsistent with Comparable Products)

2.1.3. User must use the "Send" button, and cannot use "Enter" to reliably send messages.

2.1.3.1. If Enter is used, the activity monitor quickly flashes the new message, then blanks out the screen and all history is lost (not scrollable either)

2.1.3.2. When the "Send" button is used, the activity window shows as expected (based on the 'Comparable Product' oracle via FEWHICCUPPS product consistency model)

2.1.4. User Account expiry

2.1.4.1. e.g. Does a user account get auto-deleted in 'n' (30, 60, 90) number of days if they have not logged in recently?

2.1.5. Sprint 1 (Explicit)

2.1.5.1. US1: As an IT administrator, I would like user to login with the tool before he/she can use any function, so that only authorized user can use the tool.

2.1.5.1.1. AC1: The tool should provide user login dialogue with user name and password before start using other functions

2.1.5.1.2. AC2: Failed login will be alerted to user, and the account will be locked after 5 times of failed-retry.

2.1.5.2. US2: As a new user, I would like to be able to register my account with the tool, so that I don’t need to go through system admin.

2.1.5.2.1. AC1: Login dialogue should provide user registration function

2.1.5.2.2. AC2: The tool requires user name and password to register a user

2.1.5.2.3. AC3: The tool should acknowledge the success/failure of user registration

2.1.5.3. US3: As an Engineer, I would like to create and edit memo with this tool, so that I can record my ideas quickly without searching for pen and paper.

2.1.5.3.1. AC 1: User should be able to create memo at any time while using the tool

2.1.5.3.2. AC 2: Each memo has a limit of 300 characters

2.1.5.4. US4: As an engineer, I would like to be able to save my memo at any time, from any machine, using this tool, so that I can record my idea conveniently.

2.1.5.4.1. AC 1: User should be able to save his/her memo using the tool during editing any anytime

2.1.5.4.2. AC2: If saving fails, the tool should alert user about the failure and prompt user to save to note separately.

2.1.5.5. US5: As an Engineer, I would like to access saved memo from anywhere, any machine using this tool connected to network, so that I don’t need to remember where I saved it.

2.1.5.5.1. AC 1: User should be able to retrieve the relevant memo using the tool

2.1.5.5.2. AC2: User should be able to see the list of memos he/she created

2.1.5.5.3. AC3: User should not see memos saved by other users

2.1.5.6. US6: As an IT administrator, I would like the tool not to save any copy of memos into local machines, so that information security can be ensured.

2.1.5.6.1. AC 1: The tool should not save any temp copy into local machine when user working with a memo

2.1.5.7. US7: As an Engineer, I would like to be able to publish message to all users online, so that I can make announcement easily.

2.1.5.7.1. AC2: Max message length is 140 characters

2.1.5.7.2. AC1: User should be able to publish message at any time

2.1.5.7.3. AC4: All recipients online should be able to view or ignore the published message

2.1.5.7.4. AC3: All recipients online should receive alert about the published message event before open the message

2.1.6. Sprint 2 (Explicit)

2.1.6.1. US8: As a new user, I would like the tool to bring me to registration dialogue if I login wrongly, so that I do not need to manually go back to login page and click on register button.

2.1.6.1.1. AC1: Alert message box should be displayed to remind user to register whenever login fail

2.1.6.1.2. AC2: User should be brought to registration page if responses ‘OK’ on the alert dialogue, and stay in login page if provide other responses.

2.1.6.2. US9: As an IT administrator, I would like the tool to support Server configuration, so that I can easily setup multiple servers for back up purpose.

2.1.6.2.1. AC1: User should be able to specify the server address for the chatting tool.

2.1.6.2.2. AC2: Tool will alert user if the server is not reachable

2.1.6.2.3. AC3: Once connection failed to current server, user should be able to point to different server without restart application.

2.1.6.3. US10: As an Engineer, I would like to do one-one chat with a selected user, so that our communication remain private between the selected user and I only.

2.1.6.3.1. AC1: User should be able to selected an online user to request private chat

2.1.6.3.2. AC2: During the private chat session, only requestor and recipient can see the message

2.1.6.3.3. AC3: One user can do private chat with different users at the same time

2.1.6.4. US11: As an Engineer, I would like to be able to ignore private chat request, so that I won’t receive annoying messages while I am focusing on my work.

2.1.6.4.1. AC1: User shouldn’t be able to send private message unless recipient actively accept the request

2.1.6.4.2. AC2: User shouldn’t be able to send private message if recipient quit from the chat session

2.1.7. Product Backlog

2.1.7.1. US12: As a manager, I would like to be able to view other engineer’s memo so that I can keep track each employee’s performance by knowing what they are doing.

2.1.7.1.1. AC1: User should be able send out a request on selected online user to view their memos

2.1.7.1.2. AC2: Users should be able to reject request of viewing their memos

2.1.7.1.3. AC3: User should be able to open others’ memo if request granted

2.1.7.1.4. AC4: Memos viewed by non-author are read-only

2.1.7.2. US13: As an Engineer, I should be able to start private group chat, so that I can conduct online discussion within our project group.

2.1.7.2.1. AC1: User should be able to create private chat session with multiple selected user online

2.1.7.2.2. AC2: The chat message should be visible to recipients who accept the private group chat request

2.1.7.2.3. AC3: Quit of individual user in the private group chat should not end up the complete chat session

2.2. Reliability

2.2.1. Risks if 'server' product not run as Administrator?

2.2.1.1. Port 12345 will not instantiate?

2.2.1.2. Is R/W access to file system needed?

2.2.1.2.1. Which folders contain writable data, log files, etc?

2.3. Usability

2.3.1. Keyboard shortcuts not available inside chat client (using the mouse to manually select, copy, paste, etc does work)

2.3.1.1. e.g. CTRL+A does not Select All

2.3.1.2. e.g. CTRL+C does not copy

2.3.1.3. e.g. CTRL+V does not paste

2.3.1.4. etc.

2.3.2. No scrollbar within chat activity window (user must use arrow keys)

2.4. Charisma

2.4.1. UI

2.4.1.1. Color palletes

2.4.1.1.1. Red/Black

2.4.1.1.2. Others?

2.4.1.2. OS DPI/scaling

2.4.1.2.1. Many times, when Windows scaling is used (e.g. anything other than 100%) then apps that otherwise function can become unusable.

2.4.1.3. Window scaling (chat window does not scale responsively)

2.4.2. Chat window footer text not legible ("....Work Sample")

2.4.3. Initial login window says "Gigachat" but chat window says "GigaChat". This is a charisma bug, as it conflicts with consistent product branding practices.

2.5. Security

2.5.1. DOC: "Make sure port 12345 is available on your system."

2.5.1.1. NetBus Trogan Horse (and other viruses) uses this port. If this is used in production, product security and reliability could be compromised.

2.5.1.1.1. Randomize the port?

2.5.1.1.2. Choose a port that is not as easily guessed?

2.6. Scalability

2.7. Compatibility

2.7.1. Reliant upon any 3rd parties?

2.7.1.1. APIs

2.7.1.2. DBs (local or remote)

2.7.1.3. Web services (e.g. Google fonts)

2.7.1.4. Asset caches (e.g. Akami)

2.7.1.5. If any supporting services are not running...

2.7.1.5.1. ...what is the risk to the customer?

2.7.1.5.2. ...what error messages need to be displayed?

2.7.1.5.3. ...what state does this put the software in?

2.7.2. OS Support?

2.7.2.1. Consumer: Win XP, 7, 8, 8.1, 10, etc.

2.7.2.2. Server: 2000, 2008, 2012, etc.

2.8. Performance

2.8.1. How many concurrent clients can run for a single server instance?

2.8.2. User creation limit?

2.8.3. Message size limitations?

2.9. Installability

2.9.1. Potable app/zip only or installer available?

2.10. Development

2.10.1. Two products w/in Gigachat

2.10.1.1. Chat Server

2.10.1.2. Chat Client

3. Testing Priorities

3.1. High (large amount of testing effort)

3.2. Medium (moderate amount of testing effort)

3.3. Low (little to no testing effort)

4. Product Elements

4.1. Structure

4.2. Function

4.3. Data

4.4. Interfaces

4.5. Platform

4.6. Operations

4.7. Time

5. Consistency

5.1. Familiarity

5.2. Explainability

5.3. World

5.4. History

5.5. Image

5.6. Comparable Products

5.7. Claims

5.8. Users’ Desires

5.9. Product

5.10. Purpose

5.11. Statutes and Standards