Test Plan and Cases (TPC)
Project Fokcus
Team 08
Name
Role
Steven Holland
Requirements Engineer, Prototyper, Feasibility Analyst
Arik Oganesian
Operation Concept Engineer, Software Architect, Prototyper
Marco Alvarez
Feasibility Architect, Software Architect, Requirements Engineer
Pin-Chih (Bill) Lin
Prototyper, Software Architect, Project Manager
Tatsuhiko (Tats) Tomita
Lifecycle Planner, Software Architect, Requirements Engineer
Hamed Sadeghi
Project Manager, Prototyper
Dennis Xiang
IIV&V, Quality Focal
Feb. 12, 2017
Version History
Date
Author
Version
Changes made
Rationale
12/04/2016
DX
1.0
 Initial revision
 N/A
12/04/2016
TT
1.1
 Modify schedule and resources
 Section 4
2/12/2017
MA
1.2
 Modify schedule
 Modified after first milestone in the
second semester to show progress
Table of Contents
TEST PLAN AND CASES (TPC) ..................................................................................... I
VERSION HISTORY ....................................................................................................... II
TABLE OF CONTENTS ................................................................................................. III
TABLE OF TABLES ...................................................................................................... IV
TABLE OF FIGURES ......................................... ERROR! BOOKMARK NOT DEFINED.
1.
Introduction .......................................................................................................................................................7
2.
Test Strategy and Preparation ............................................................................................................................8
3.
4.
2.1
Hardware preparation ................................................................................................................................8
2.2
Software preparation ..................................................................................................................................8
2.3
Other pre-test preparations.........................................................................................................................8
2.4
Requirements Traceability .........................................................................................................................8
Test Identification ..............................................................................................................................................9
3.1
Test Identifier.............................................................................................................................................9
3.2
Test Identifier........................................................................................................................................... 13
3.3
Test Identifier........................................................................................................................................... 15
3.4
Test Identifier........................................................................................................................................... 21
3.5
Test Identifier........................................................................................................................................... 24
3.6
Test Identifier........................................................................................................................................... 29
Resources and schedule ................................................................................................................................... 33
4.1
Resources ................................................................................................................................................. 33
4.2
Staffing and Training Needs .................................................................................................................... 34
4.3
Schedule................................................................................................................................................... 34
Table of Tables
Table 1: Requirements Traceability Matrix ...................................................................................................................8
Table 2: TC-01-01 Empty text message input ................................................................................................................9
Table 3: TC-01-02 Special character input test .......................................................................................................... 10
Table 4: TC-01-03 Unicode text message input .......................................................................................................... 10
Table 5: TC-01-04 Message notification test............................................................................................................... 11
Table 6: TC-01-05 Message with link input test .......................................................................................................... 12
Table 7: TC-02-01 Successful Account Creation......................................................................................................... 13
Table 8: TC-02-02 Failed Account Creation ............................................................................................................... 13
Table 9: TC-02-03 Create Account With Invalid Name .............................................................................................. 14
Table 10: TC-02-04 Create Account Over Capacity ................................................................................................... 14
Table 11: TC-02-06 Login Account Fail With No User............................................................................................... 15
Table 12: TC-02-07 Login Account Fail With Invalid Password ................................................................................ 15
Table 13: TC-03-01 Matchings produced for entrepreneur ........................................................................................ 16
Table 14: TC-03-02 Attribute field “help” left empty for entrepreneur ...................................................................... 17
Table 15: TC-03-03 No mentors in database .............................................................................................................. 18
Table 16: TC-03-04 No mentors available for matching ............................................................................................. 19
Table 17: TC-03-05 Connection with database lost, can’t access information ........................................................... 20
Table 18: TC-04-01 Profile Completeness, check profile for completeness ................................................................ 21
Table 19: TC-04-02 Profile Correctness, check profile for correctness ...................................................................... 22
Table 20: TC-04-03 Erroneous Input, check profile/questionnaire with erroneous input........................................... 22
Table 21: TC-04-04 Incomplete Input, check profile/questionnaire with incomplete input ........................................ 23
Table 22: TC-04-05 Successful Update, check database for updated profile data. If the data successfully make it to
the database ................................................................................................................................................................. 23
Table 23: TC-05-01 Cannot Enter Invalid Curriculum Item ....................................................................................... 24
Table 24: TC-05-02 Create a Curriculum Item ........................................................................................................... 25
Table 25: TC-05-03 Create Multiple Curriculum Items .............................................................................................. 26
Table 26: TC-05-04 Delete Curriculum Items ............................................................................................................. 26
Table 27: TC-05-05 Mentor Can View Status of Current Curriculum Items ............................................................... 27
Table 28: TC-05-06 Edit Curriculum Items................................................................................................................. 28
Table 29: TC-05-07 Entrepreneur Can View Status of Current Curriculum Items ..................................................... 29
Table 30: TC-06-01 Forum Functionality User Access............................................................................................... 30
Table 31: TC-06-02 Forum Functionality User Contribution ..................................................................................... 30
Table 32: TC-06-03 Forum Functionality Post Editing .............................................................................................. 31
Table 33: TC-06-04 Forum Fuctionality Post Deletion .............................................................................................. 31
Table 34: TC-06-05 Forum Functionality Content Variety ......................................................................................... 31
Table 35: Testing Schedule.......................................................................................................................................... 34
Test Plan and Cases (TPC)
Version 1.2
Table of Figures
Figure 1: Project Plan...................................................................................................................................33
Test Plan and Cases (TPC)
Version 1.2
1. Introduction
The purpose of this document is to delineate the testing procedures and test cases in order to ensure that the
delivered product is of high quality. The test cases listed below will perform unit testing, integration
testing, as well as system and requirements testing. All test cases are traced to a win-condition
(requirement) negotiated with the client, ensuring that all features are delivered to the client in the final
deliverable.
Test Plan and Cases (TPC)
Version 1.2
2. Test Strategy and Preparation




Code subject to unit testing will employ agile test-first methodology to ensure unit quality prior to
integration testing.
We will use continuous integration testing to ensure that each feature added to the product works
correctly in the scope of the system.
Tests will be prioritized based on risk level and value added.
Requirements will be traced for each test; test cases will reflect any requirement changes/updates.
2.1 Hardware preparation
Aside from personal computers which each team member has, no additional hardware will be necessary to
perform the necessary tests.
2.2 Software preparation


Jenkins will be used to manage integration testing. Testing is automated and triggered whenever
code is pushed to the repository. Only team members will have access to Jenkins.
Not all team members have a mac which is needed to run Xcode and its unit testing capabilities.
VMWare/VirtualBox will be loaded on windows machines in order to run Mac OS X to allow all
members to contribute.
2.3 Other pre-test preparations
None
2.4 Requirements Traceability
Table 1: Requirements Traceability Matrix
Core Capability
Core Capability
Customized User Profile
User Defined Curriculum
Mentor-Mentee Matching
Communication Channel
Win Condition
Win Condition(s)
WC_4081,
WC_4080
WC_3972,
WC_4017,
WC_4082,
WC_4096,
WC_4095,
WC_4084
WC_4094,
WC_4018
WC_4146,
WC_4142,
WC_4083
Test Suite
Test Suite(s)
TS-02 & TS-04
TS-05
TS-03
TS-01 & TS-06
Test Plan and Cases (TPC)
Version 1.2
All requirements will be verified via testing.
Test suites:
•
•
•
•
•
•
TS-01: User Text Messaging
TS-02: Account Services
TS-03: Mentor-Entrepreneur Matching
TS-04: User Profile Customization
TS-05: Curriculum Delivery and Content
TS-06: Community Forum
3. Test Identification
3.1 Test Identifier 01
TS-01: Communication Channel - Private Messaging.
3.1.1
Test Level
System Performance
3.1.2
Test Class
Test classes include both erroneous input text testing and erroneous user behavior input.
3.1.3
Test Completion Criteria
When one user sends a text message to the other user, both the local and remote user has to be able to see
the message appear in the chat log and with expected UI layout, text output and in right order.
3.1.4
Test Cases
Table 2: TC-01-01 Empty text message input
Test Case Number
Test Item
Test Priority
Pre-conditions
Post-conditions
TC-01-01 Empty text message input
Testing if private messaging feature in Fōkcus
app can handle empty input messages
correctly.
Must have
User has to enter chat room (i.e. in the chat
room page)
No message should show in the chat log on
both end users’ device
Test Plan and Cases (TPC)
Version 1.2
Input Specifications
Expected Output Specifications
Pass/Fail Criteria
Assumptions and Constraints
Dependencies
Traceability
In the text field, type an empty string (i.e. “ ”)
and send the message
Since the text message is an empty string, the
message should not be sent and no message
should appear on the chat log cell.
Pass:
After sending an empty string, nothing
should happen and no message should appear
in the chat log on both device.
Fail:
After sending an empty string, a message
appears in the chat log on both device.
End user device is connected with internet and
logged in to the system.
N/A
WC_4083 Communications System - As a
user, I can send/receive messages within the
app
Table 3: TC-01-02 Special character input test
Test Case Number
Test Item
TC-01-02 Special character input test
Testing if private messaging feature in Fōkcus
app can handle special text input correctly.
Test Priority
Pre-conditions
Must have
User has to enter chat room (i.e. in the chat
room page)
Message including the special characters should
be displayed properly in the chat log on both
device.
Special characters like:
`~@#$%^&*()/\[]{}+=<>|”’?_These special characters should be displayed
properly on both side of the device.
Pass:
After sending these characters, each end
user should be able to see the correct message.
Fail:
App crash or not showing the expected
message is considered to be a failure.
End user device is connected with internet and
logged in to the system.
Post-conditions
Input Specifications
Expected Output Specifications
Pass/Fail Criteria
Assumptions and Constraints
Dependencies
Traceability
N/A
WC_4083 Communications System - As a user,
I can send/receive messages within the app
Table 4: TC-01-03 Unicode text message input
Test Case Number
TC-01-03 Unicode text message input
Test Plan and Cases (TPC)
Version 1.2
Test Item
Test Priority
Pre-conditions
Post-conditions
Input Specifications
Expected Output Specifications
Pass/Fail Criteria
Assumptions and Constraints
Dependencies
Traceability
Testing if the messaging system can handle
Unicode properly, in other words, users
should be able to send message in different
language and also emoji without crashing the
system or see unexpected output.
Must have
User has to enter chat room (i.e. in the chat
room page)
Message that being sent appeared properly on
both devices.
Different Unicode input like: こんにちは
(Japanese), 你好(Traditional Chinese), etc. Or
emoji like <3, , and so on.
All output on both devices should be exactly
like the input text. For example, showing the
correct format of foreign language not just
some random encoding.
Pass:
After sending these characters, each end
user should be able to see the correct message.
Fail:
App crash or not showing the expected
message is considered to be a failure.
End user device is connected with internet and
logged in to the system.
N/A
WC_4083 Communications System - As a
user, I can send/receive messages within the
app
Table 5: TC-01-04 Message notification test
Test Case Number
Test Item
Test Priority
Pre-conditions
Post-conditions
Input Specifications
Expected Output Specifications
Pass/Fail Criteria
TC-01-04 Message notification test
Testing if the notification triggered/appeared
when the other user sends a message to the
chat room
Must have
User who sends the message has to be in the
chat room page while the other user can be in
any application or with phone locked.
Message that being sent appeared properly as
a notification on the device that received this
message.
Input can be any string.
Expected output should be the same as input
string.
Pass:
The user who received this message
should see a system-wise notification and this
message also appeared properly in terms of
format and UI in the chat room page in the
Fōkcus app.
Test Plan and Cases (TPC)
Version 1.2
Fail:
The notification does not appear on the
device that received this message or the
message appeared in an unexpected format or
the message does not appear in the message
log in the chat room.
Assumptions and Constraints
Dependencies
Traceability
End user device is connected with internet and
logged in to the system.
N/A
WC_4083 Communications System - As a
user, I can send/receive messages within the
app
Table 6: TC-01-05 Message with link input test
Test Case Number
Test Item
Test Priority
Pre-conditions
Post-conditions
Input Specifications
Expected Output Specifications
Pass/Fail Criteria
TC-01-05 Message with link input test
Test when input message contains a web link,
the link should be interpreted as a clickable
link.
Must have
User has to enter chat room (i.e. in the chat
room page)
Message that being sent appeared properly on
both devices.
Any legal web link, such as www.google.com
Output should be exactly the same as input
and also become clickable (i.e. can be tapped).
Pass:
Input message appeared properly in the
chat log and can be clicked (or tapped). Once
the user tapped on the link, system should
open up browser and take user to that
particular address.
Fail:
Input message does not appear properly in
terms of UI and format. Also even though the
message looks the same as input but if it’s not
clickable, this is considered as a failure as
well.
Assumptions and Constraints
Dependencies
Traceability
End user device is connected with internet and
logged in to the system.
N/A
WC_4083 Communications System - As a
user, I can send/receive messages within the
app
Test Plan and Cases (TPC)
Version 1.2
3.2 Test Identifier 02
TS-02: CreateAccount
3.2.1
Test Level
Software item level
3.2.2
Test Class
Function test
3.2.3
Test Completion Criteria
This test for create account will be completed when
-
3.2.4
The system creates a new account; and
The user log in to the system as the new account
Test Cases
Table 7: TC-02-01 Successful Account Creation
Test Case Number
Test Item
Test Priority
Pre-conditions
Post-conditions
Input Specifications
Expected Output
Specifications
Pass/Fail Criteria
TC-02-01-CreateAccountAndSuccess
As a user, create a new account and success
M (Must have)
There is no user name, “newuser” in this system
Note: “newuser” could be another name which cannot be used by
general users
A new user, “newuser” is created
- Username “newuser”
- Password
A new user account will be created in the database.
Pass
-
“newuser” account is created in database
The user can see the top page of this application and see the
tutorial.
Fail
Assumptions and Constraints
Dependencies
Traceability
- “newuser” account is NOT created in database.
The device of iOS is connected to the database by internet
None
WC_3993: “Account” As a user, I can sign up for the application.
Table 8: TC-02-02 Failed Account Creation
Test Case Number
Test Item
Test Priority
TC-02-02-CreateAccountAndFail
As a user, trys to create a new account but fails
M (Must have)
Test Plan and Cases (TPC)
Version 1.2
There is already a user name, “newuser” in this system
Note: “newuser” could be another name which is already used by
another one
No change in database
- Username “newuser”
- Password
The user goes back to sign-up page
Pre-conditions
Post-conditions
Input Specifications
Expected Output
Specifications
Pass/Fail Criteria
Pass
-
The user sees error message that shows the “newuser” is
already used
Fail
Assumptions and Constraints
Dependencies
Traceability
- “newuser” account is created in database.
The device of iOS is connected to the database by internet
TC-02-01-CreateAccountAndSuccess
WC_3993: “Account” As a user, I can sign up for the application.
Table 9: TC-02-03 Create Account With Invalid Name
Test Case Number
Test Item
TC-02-03-CreateAccountWithInvalidName
As a user, trys to create a new account but fails since they use
characters which are not allowed to use, for example, “ “, “?”, “{“
M (Must have)
None
No change in database
- Username “n ewuser”
- Password
The user goes back to sign-up page
Test Priority
Pre-conditions
Post-conditions
Input Specifications
Expected Output
Specifications
Pass/Fail Criteria
Pass
-
The user sees error message that shows the invalid character
is used
Fail
Assumptions and Constraints
Dependencies
Traceability
- “n ewuser” account is created in database.
The device of iOS is connected to the database by internet
None
WC_3993: “Account” As a user, I can sign up for the application.
Table 10: TC-02-04 Create Account Over Capacity
Test Case Number
Test Item
Test Priority
Pre-conditions
Post-conditions
Input Specifications
Expected Output
Specifications
Pass/Fail Criteria
TC-02-04-CreateAccountOverCapacity
As a user, trys to create a new account but fails since there are already
limited number of users in the system
C (Could have)
There are limited number of users in the database, for example,
100,000 users
No change in database
- Username “user”
- Password
The user goes back to sign-up page
Pass
-
The user sees error message that shows the system can no
longer have a new user
Test Plan and Cases (TPC)
Version 1.2
Fail
Assumptions and Constraints
Dependencies
Traceability
- “user” account is created in database.
The device of iOS is connected to the database by internet
None
WC_3993: “Account” As a user, I can sign up for the application.
Table 11: TC-02-06 Login Account Fail With No User
Test Case Number
Test Item
Test Priority
Pre-conditions
Post-conditions
Input Specifications
Expected Output
Specifications
Pass/Fail Criteria
Assumptions and Constraints
Dependencies
Traceability
TC-02-06-LogInAccountFailWithNoUser
Log in with invalid account
M (Must have)
There is not a user account with “newuser” name in this system
Note: “newuser” could be another name which is not created yet
None
- Username “newuser”
- Password
The user sees error message that shows such user name is not in the
system.
Pass
- The user sees sign in page again
Fail
- The user sees home page
The device of iOS is connected to the database by internet.
None
WC_3993: “Account” As a user, I can sign up for the application.
Table 12: TC-02-07 Login Account Fail With Invalid Password
Test Case Number
Test Item
Test Priority
Pre-conditions
Post-conditions
Input Specifications
Expected Output
Specifications
Pass/Fail Criteria
TC-02-07-LogInAccountFailWithInvalidPassword
Log in with invalid password
M (Must have)
There is a user account with “user” name in this system
Note: “user” could be another name which is already created
None
- Username “user”
- InvalidPassword
The user sees error message that shows the password is invalid
Pass
-
The user sees sign in page again
Fail
Assumptions and Constraints
Dependencies
Traceability
- The user sees home page
The device of iOS is connected to the database by internet.
TC-02-01-CreateAccountAndSuccess
WC_3993: “Account” As a user, I can sign up for the application.
3.3 Test Identifier 03
TS-03: Mentor-Entrepreneur Matching
Test Plan and Cases (TPC)
3.3.1
Version 1.2
Test Level
Unit level testing
3.3.2
Test Class
Erroneous testing and simulated testing
3.3.3
Test Completion Criteria
The test for mentor-entrepreneur matching will be completed when:
a. Entrepreneur JSON file attributes are filled, at least “help” attribute is filled
b. Algorithm pulls mentor data from database
c. Compares each mentor attributes with entrepreneur attributes to calculate best mentor
d. Top mentor matchings returned to application
3.3.4
Test Cases
Table 13: TC-03-01 Matchings produced for entrepreneur
Description: This test will test the code path of the algorithm. By going through all the code, correct
matches for the entrepreneur will be made. This is important because we want to see if the algorithm will
produce a correct matching will mentors based on the attributes of the entrepreneurs and mentors. Thus, we
will have simulated data that will go through entire algorithm to produce matching.
Test Case Number
TC-03-01 Matchings produced for entrepreneur
Test Item
Test the algorithm to make sure matches are made for entrepreneurs. This
tests that the algorithm can run successfully and produce matchings
correctly.
Test Priority
M
Pre-conditions
- Data for mentors exist in database
- Entrepreneur required data is filled, JSON file of required fields have
information
- Connection with database established
Post-conditions
- Top matchings with mentors correctly produced based on entrepreneur
data
- Return JSON files of top mentors
Input Specifications
- JSON file of entrepreneur is filled, no attributes left blank
Expected Output
Specifications
- Top mentors produced by matching
- System exit successfully
Test Plan and Cases (TPC)
Pass/Fail Criteria
Version 1.2
Pass Criteria:
- System exit successfully
- Top mentor matchings returned
Fail Criteria:
- System fail
- No matchings produced
Assumptions and
Constraints
- Connection with database is stable
- Mentors exists in database and have attributes in their JSON files filled
- Result sent back to application successfully
Dependencies
N/A
Traceability
WC-4018: As an admin, I will use an algorithm that will match entrepreneur
and mentors
Table 14: TC-03-02 Attribute field “help” left empty for entrepreneur
Description: This test will be testing a boundary value, from equivalence partitioning technique. This field
cannot be left blank because it is important for entrepreneur to have the “help” attribute filled to be able to
be matched with entrepreneur that can help them with that problem. So this will test a certain condition in
the code. This test is important because without the field being filled out, then no matches can be produced,
causing an error. This is why we must test and make sure the code can handle such erroneous input.
Test Case Number
TC-03-02 Attribute field “help” left empty for entrepreneur
Test Item
Test that algorithm will handle erroneous input of missing “help” attribute
for entrepreneur. Tests a code path that checks if the “help” attribute exists.
Test Priority
M
Pre-conditions
- Entrepreneur JSON file filled except for “help” attribute, which is left
blank
- Data for mentors exist in database
- Connection with database established
Post-conditions
- Error thrown by algorithm
- No matchings produced
- System exists with error
Input Specifications
- JSON file with entrepreneur data filled except for “help” attribute
Expected Output
Specifications
- System exit with error (“help” attribute is blank)
Test Plan and Cases (TPC)
Pass/Fail Criteria
Version 1.2
Pass Criteria:
-
Error thrown by algorithm
No matchings produced
System exits with error
Application notified of error
Fail Criteria:
- System exists successfully
- Matchings produced and returned
Assumptions and
Constraints
- Database is stable (can be accessed)
- No other erroneous input, except for the one specified above
- Error sent to application successfully
Dependencies
N/A
Traceability
WC-4094: As an entrepreneur, I can have a mentors matched after filling out
the questionnaire/quiz.
Table 15: TC-03-03 No mentors in database
Description: I am testing a boundary case with this test case, thus traversing a code path in the algorithm.
This test is important because if there are no mentors in the database, the algorithm will not be able to
produce matchings. Thus, the algorithm should handle this special rainy day scenario.
Test Case Number
TC-03-03 No mentors in database
Test Item
Test algorithm when there are no data for mentors in the database to produce
a matching for entrepreneur. This will test the matching algorithm.
Test Priority
M
Pre-conditions
- Entrepreneur JSON file attributes all filled
- No mentor data in database
- Connection with database established
Post-conditions
- Error thrown by algorithm
- Algorithm stops
Input Specifications
- Entrepreneur JSON file with filled attributes
Expected Output
Specifications
- System exists with error (no mentors exist in database)
Test Plan and Cases (TPC)
Pass/Fail Criteria
Version 1.2
Pass Criteria:
-
Error thrown by algorithm
System exists
No matchings made
Application notified of error
Fail Criteria:
- System exists successfully
- Matchings made and returned
Assumptions and
Constraints
- Database connection stable (can be accessed)
- Error sent to application successfully
Dependencies
N/A
Traceability
WC-4094: As an entrepreneur, I can have a mentors matched after filling out
the questionnaire/quiz.
Table 16: TC-03-04 No mentors available for matching
Description: Testing a boundary case from equivalence partitioning technique. The test case is important
because there can be a point where no mentors are available for matchings, so they shouldn’t take in more
entrepreneurs. This would be the case when mentors have taken their maximum number of entrepreneurs
they can help. Algorithm should handle when this special case happens. This can be considered a sunny day
scenario. This will be tested with simulated data, where mentors are not able to accept more entrepreneurs.
Test Case Number
TC-03-04 No mentors available for matching
Test Item
Test the matching algorithm to handle mentors not being able to accept more
entrepreneurs because of their “capacity” attribute being at the limit.
Test Priority
S
Pre-conditions
- Entrepreneur JSON file with filled attributes
- Mentors in database have “capacity” attribute full
- Connection with database established
Test Plan and Cases (TPC)
Version 1.2
Post-conditions
- Message returned to application
- No matchings made
Input Specifications
- Entrepreneur JSON file with filled attributes
Expected Output
Specifications
- Message sent to application (No matchings possible at this time)
Pass/Fail Criteria
Pass Criteria:
- Application notified through message
- No matchings made
Fail Criteria:
- Matching made and returned
Assumptions and
Constraints
- Database is stable (can be accessed)
- Message successfully received by application
- No erroneous input received by algorithm
Dependencies
N/A
Traceability
WC-4094: As an entrepreneur, I can have a mentors matched after filling out
the questionnaire/quiz.
Table 17: TC-03-05 Connection with database lost, can’t access information
Description: This test case is a boundary case, ‘rainy day scenario’. This test case is important to check
because we can’t control when the database will be active or not. So if the database is not reachable, then
algorithm should be able to handle this case, and not hang, trying to compute a matching. This will test a
code path in the algorithm, that will handle this test case.
Test Case Number
TC-03-05 Connection with database lost, can’t access information
Test Item
Test the matching algorithm to handle connection loss with database.
Test Priority
S
Pre-conditions
- Entrepreneur JSON file with filled attributes
Post-conditions
- System exists with error message
Input Specifications
- Entrepreneur JSON file with filled attributes
Expected Output
Specifications
- System error
- Error thrown, error message sent
Test Plan and Cases (TPC)
Pass/Fail Criteria
Version 1.2
Pass Criteria:
- Error message sent (Connection with database can’t be established)
- No matchings made
Fail Criteria:
- Algorithm doesn’t exit
- System hang, nothing is happening
Assumptions and
Constraints
- Database is down
- Message successfully received by application
- No erroneous input received by algorithm from user
Dependencies
N/A
Traceability
WC-4094: As an entrepreneur, I can have a mentors matched after filling out
the questionnaire/quiz.
3.4 Test Identifier 04
TS-04: Custom Profile
3.4.1
Test Level
Unit level testing
3.4.2
Test Class
Erroneous testing
3.4.3
Test Completion Criteria
The test will be completed when:
1. The system generates a complete and correct custom profile.
2. The system successfully updates the profile data in the database.
3. The custom profile is properly displayed on the app screen.
3.4.4
Test Cases
Table 18: TC-04-01 Profile Completeness, check profile for completeness
Realizing that we must see all the user information, it is vital to show all the information that belongs in the
user profile because the users’ user profile because other users will access it in order to learn more about
the client.
Test Case Number
Test Item
Test Priority
TC-04-01 Profile Completeness
This Custom User Profile is tested with incomplete data.
Must Have
Test Plan and Cases (TPC)
Pre-conditions
Post-conditions
Input Specifications
Expected Output Specifications
Pass/Fail Criteria
Assumptions and Constraints
Dependencies
Traceability
Version 1.2
The JSON data was fetched from the database.
The profile data is displayed fully.
The input is JSON of the profile data we fetched.
At least one of the variables that get its value from
the input should be empty.
Pass: At least one of variables that get its value
from the input is empty.
Fail: None of the variables that got their values
from the input are empty.
The database contains information about the user
profile.
N.A
WC_4081
Table 19: TC-04-02 Profile Correctness, check profile for correctness
Not only do we have to show all the user information, but also it has to be the correct data. Hence, I think it
is vital to show the correct information on the users’ user profile because other users will access it in order
to learn more about the client.
Test Case Number
Test Item
Test Priority
Pre-conditions
Post-conditions
Input Specifications
Expected Output Specifications
Pass/Fail Criteria
Assumptions and Constraints
Dependencies
Traceability
TC-04-02 Profile Correctness
Custom user profile is tested with correct data.
Must Have
JSON file is fetched from the database
 The JSON doesn’t set the variables that
make up the custom user profile.
 Error about bad input file is thrown
The input is JSON of the profile data we fetched.
All the data in the input should match the data in
the database for the specific user.
Pass: All The data in the input does match the data
in the database for the specific user.
Fail: At least one of the data files in the JSON file
doesn’t match the JSON file in the Database.
The database contains information about the user
profile.
TC-04-01
WC_4081
Table 20: TC-04-03 Erroneous Input, check profile/questionnaire with erroneous input
It is vital that the user fills out all the information since this information will be fed to the to the matching
algorithm.
Test Case Number
Test Item
TC-04-03 Erroneous Input
Custom user profile is tested with erroneous data.
Test Plan and Cases (TPC)
Test Priority
Pre-conditions
Post-conditions
Input Specifications
Expected Output Specifications
Pass/Fail Criteria
Assumptions and Constraints
Dependencies
Traceability
Version 1.2
Must Have
All the variables are of the correct data type.
 The user profile data isn’t saved locally.
 Error is thrown for bad input
The variable that pertains to the user profile’s data
field
At least on of the input’s value shouldn’t be of the
correct format and type.
Pass: At least one of the variable’s value isn’t of
the correct format and type.
Fail: All the variable’s values are of the correct
format and type.
All the variables exist in for the user profile.
N.A
WC_4080
Table 21: TC-04-04 Incomplete Input, check profile/questionnaire with incomplete input
From the equivalence partitioning technique, I am testing the boundary values for the input. This is
important because we must have well-formatted and correct information supplied to the matching
algorithm.
Test Case Number
Test Item
Test Priority
Pre-conditions
Post-conditions
Expected Output Specifications
Pass/Fail Criteria
TC-04-04 Incomplete Input
Custom user profile is tested with incomplete data.
Must Have
All the variables for the user profile exist
 User profile isn’t saved to the JSON
 An error is thrown
 The JSON file isn’t sent to the database
The variable that pertains to the user profile’s data
field in the JSON
The input shouldn’t have a value
Pass: The input doesn’t a value
Assumptions and Constraints
Dependencies
Traceability
Fail: The input has a value
There’s a controller for the Custom User Profile.
N.A
WC_4080
Input Specifications
Table 22: TC-04-05 Successful Update, check database for updated profile data. If the data
successfully make it to the database
I came up with this test because I realized that it is important to make sure that data the user input gets
successfully saved. It is vital to know whether the information we just filled was successfully sent and
saved to the database because this enables other users to see your profile and it is necessary for the
matching algorithm.
Test Plan and Cases (TPC)
Test Case Number
Test Item
Test Priority
Pre-conditions
Version 1.2
Expected Output Specifications
Pass/Fail Criteria
TC-04-05 Successful Update
Custom user profile is tested with correct data.
Must Have
The user has a function that sends a JSON to the
database. Also, the user has a variable for the
JSON he/she is going to pass.
The gathered data should appear in the DB with
correct format and values.
The JSON file that holds all the data the user
finished filling out that pertains to his user profile.
The input should appear in the database
Pass: The input does appear in the database
Assumptions and Constraints
Dependencies
Traceability
Fail: The input doesn’t appear in the database.
There exists a database
TC-04-03
WC_4080
Post-conditions
Input Specifications
3.5 Test Identifier 05
TS-05: Curriculum Content
3.5.1
Test Level
Software level testing
3.5.2
Test Class
Erroneous testing and simulated testing
3.5.3



3.5.4
Test Completion Criteria
The system connects to our database backend and retrieves the current list of curriculum items for
each entrepreneur assigned to the current mentor. These are displayed in the application
appropriately.
System is capable of handling add/edit/delete functionality of these curriculum items by the
mentor of the respective entrepreneur.
System does not crash during testing.
Test Cases
Table 23: TC-05-01 Cannot Enter Invalid Curriculum Item
Description: This item involves testing that a mentor cannot assign an empty string as a curriculum item for
an entrepreneur. This is a boundary condition that will need to be tested for the text input for entering
curriculum items for entrepreneurs.
Test Plan and Cases (TPC)
Version 1.2
Test Case Number
TC-05-01 Cannot Enter Invalid Curriculum Item
Test Item
Testing that mentor cannot assign an empty string as an action item.
Test Priority
M: Must have
Pre-conditions
You must be logged in to the application as a mentor and you must have
entrepreneurs assigned to you.
An error message is displayed asking the user to please try again as the
entry was an invalid format.
The mentor clicks to add a curriculum item and tries entering an empty
string.
The system will not allow the user to enter an empty string as input for
a curriculum item. It will display an error message asking the user to try
again.
System passes if the user is stopped from entering an empty string as
input for a curriculum item and the respective error message is
displayed. System fails if the user can enter the empty string as a
curriculum item.
System has a working connection to the database backend and can
retrieve and store information.
This application does not crash when opened and the database backend
server can accept requests. User can enter text into the text box to add
additional curriculum items.
WC_4082: As a mentor, I can create new lesson/curriculum content.
Post-conditions
Input Specifications
Expected Output
Specifications
Pass/Fail Criteria
Assumptions and
Constraints
Dependencies
Traceability
Table 24: TC-05-02 Create a Curriculum Item
Description: This item involves testing the ability of a mentor to create and assign a curriculum item to an
entrepreneur. This test case satisfies MC/DC criterion because there is a clearly defined entry and exit point
(input and output), the decision considers every possible outcome (either the item is added, or it isn’t), and
the decision tested is will be shown to impact the outcome of the decision.
Test Case Number
TC-05-02 Create a Curriculum Item
Test Item
Testing the ability of a mentor can create and assign a curriculum item
to an entrepreneur.
M: Must have
Test Priority
Pre-conditions
Post-conditions
Input Specifications
Expected Output
Specifications
Pass/Fail Criteria
You must be logged in to the application as a mentor and you must have
entrepreneurs assigned to you.
A success message will be displayed letting the mentor know that this
new curriculum item has been added.
The mentor clicks to add a curriculum item and enters text. The mentor
cannot enter an empty string (this is covered in another test case).
The system will allow the mentor to add a curriculum item for their
respective entrepreneur. The system will display a message indicating
that this new item has been added.
System passes if the mentor can enter text input, resulting in a new
curriculum item. This new curriculum item is now displayed
Test Plan and Cases (TPC)
Assumptions and
Constraints
Dependencies
Traceability
Version 1.2
respectively with the entrepreneur it is assigned to. The system fails if
the curriculum item is not added.
System has a working connection to the database backend and can
retrieve and store information.
This application does not crash when opened and the database backend
server can accept requests. User can enter text into the text box to add
additional curriculum items.
WC_4082: As a mentor, I can create new lesson/curriculum content.
Table 25: TC-05-03 Create Multiple Curriculum Items
Description: This item involves testing the ability of a mentor to create and assign a curriculum item to an
entrepreneur. This test case is an extension of the last test case. We need to be able to assign multiple
curriculum items to an entrepreneur. As such, it satisfies MC/DC criterion because there is a clearly defined
entry and exit point (input and output), the decision considers every possible outcome (either the item is
added, or it isn’t), and the decision tested is will be shown to impact the outcome of the decision.
Test Case Number
TC-05-03 Create Multiple Curriculum Items
Test Item
Testing the ability of a mentor can create and assign multiple
curriculum items to an entrepreneur.
M: Must have
Test Priority
Pre-conditions
Post-conditions
Input Specifications
Expected Output
Specifications
Pass/Fail Criteria
Assumptions and
Constraints
Dependencies
Traceability
You must be logged in to the application as a mentor and you must have
entrepreneurs assigned to you. There must already be a curriculum item
assigned to the entrepreneur who the new item will be assigned to.
A success message will be displayed letting the mentor know that this
new curriculum item has been added.
The mentor clicks to add a curriculum item and enters text. The mentor
cannot enter an empty string (this is covered in another test case).
The system will allow the mentor to add an additional curriculum item
for their respective entrepreneur. The system will display a message
indicating that this new item has been added.
System passes if the mentor can enter text input, resulting in a new
curriculum item. This new curriculum item is now displayed
respectively with the entrepreneur it is assigned to. The system fails if
the curriculum item is not added.
System has a working connection to the database backend and can
retrieve and store information.
This application does not crash when opened and the database backend
server can accept requests. User can enter text into the text box to add
additional curriculum items.
WC_4082: As a mentor, I can create new lesson/curriculum content.
Table 26: TC-05-04 Delete Curriculum Items
Description: This item involves testing the ability of a mentor to delete curriculum items that they have
assigned to their respective entrepreneur. This test case satisfies MC/DC criterion because there is a clearly
Test Plan and Cases (TPC)
Version 1.2
defined entry and exit point, the decision considers every possible outcome (either the item is deleted, or it
isn’t), and the decision tested is will be shown to impact the outcome of the decision.
Test Case Number
TC-05-04 Delete Curriculum Items
Test Item
Testing the ability that a mentor can delete curriculum items that they
have assigned to their respective entrepreneur.
M: Must have
Test Priority
Pre-conditions
Post-conditions
Input Specifications
Expected Output
Specifications
Pass/Fail Criteria
Assumptions and
Constraints
Dependencies
Traceability
You must be logged in to the application as a mentor and you must
have entrepreneurs assigned to you. There must already be a curriculum
item assigned to the entrepreneur, as you will need an item to delete.
A success message will be displayed letting the mentor know that this
curriculum item has been deleted from the list assigned to the current
entrepreneur.
The mentor clicks to delete the curriculum item from the respective
entrepreneur.
The system will allow the mentor to delete a curriculum item for their
respective entrepreneur. The system will display a message indicating
that this item has been deleted from the current list assigned to the
entrepreneur.
System passes of the mentor can delete the curriculum item. The list of
curriculum items will now not display the deleted item. The system
fails if the curriculum item is not removed from the list, or deleted from
the database backend.
System has a working connection to the database backend and can
retrieve and store information.
This application does not crash when opened and the database backend
server can accept requests. Mentor has a delete button available for
curriculum items they have assigned to their respective entrepreneur.
As a mentor, I can delete curriculum items currently assigned to my
respective entrepreneurs.
Table 27: TC-05-05 Mentor Can View Status of Current Curriculum Items
Description: This item involves testing the ability of a mentor to view current curriculum items that have
been assigned to their respective entrepreneur, and see the statuses relative to these items. This test case
satisfies MC/DC criterion because there is a clearly defined entry and exit point, the decision considers
every possible outcome (either the item and status is displayed, or it isn’t), and the decision tested is will be
shown to impact the outcome of the decision.
Test Case Number
TC-05-05 Mentor Can View Status of Current Curriculum Items
Test Item
Testing the ability of a mentor to view current curriculum items that
have been assigned to their respective entrepreneur and see the statuses
relative to these items.
M: Must have
Test Priority
Pre-conditions
Post-conditions
You must be logged in to the application as a mentor and you must
have entrepreneurs assigned to you. There must already be a curriculum
item assigned to the entrepreneur, as you will need an item to check.
A mentor will be able to view all curriculum items currently assigned to
the entrepreneur, and the status of each of these items.
Test Plan and Cases (TPC)
Input Specifications
Expected Output
Specifications
Pass/Fail Criteria
Assumptions and
Constraints
Dependencies
Traceability
Version 1.2
A mentor will be able to click to view the status of any of the
curriculum items currently assigned to their respective entrepreneur.
The curriculum items and status will be displayed in the application.
The system passes of the mentor can view all curriculum items and
statuses of those items that they have assigned to their respective
entrepreneur. The system fails if not all items that have been assigned
by the mentor, or their statuses, are displayed.
System has a working connection to the database backend and can
retrieve and store information.
This application does not crash when opened and the database backend
server can accept requests.
WC_4084: As a mentor, I can assign, track, and review homework.
Table 28: TC-05-06 Edit Curriculum Items
Description: This item involves testing the ability of a mentor to edit curriculum items that they have
assigned to their respective entrepreneur. This test case satisfies MC/DC criterion because there is a clearly
defined entry and exit point, the decision considers every possible outcome (either the item is edited, or it
isn’t), and the decision tested is will be shown to impact the outcome of the decision.
Test Case Number
TC-05-06 Edit Curriculum Items
Test Item
Testing the ability that a mentor can edit curriculum items that they
have assigned to their respective entrepreneur.
M: Must have
Test Priority
Pre-conditions
Post-conditions
Input Specifications
Expected Output
Specifications
Pass/Fail Criteria
Assumptions and
Constraints
Dependencies
Traceability
You must be logged in to the application as a mentor and you must
have entrepreneurs assigned to you. There must already be a curriculum
item assigned to the entrepreneur, as you will need an item to edit.
A system success message will be displayed indicating that the
curriculum item was successfully edited.
The mentor clicks to add a curriculum item and enters text. The mentor
cannot enter an empty string.
The system will allow the mentor to edit a curriculum item they have
assigned to their respective entrepreneur. The system will display a
message indicating that this new item has been edited.
System passes if the mentor can enter text input, resulting in an edited
curriculum item. This new curriculum item is now displayed
respectively with the entrepreneur it is assigned to. The system fails if
the new curriculum item is not edited in the database backend, and not
displayed in the application.
System has a working connection to the database backend and can
retrieve and store information.
This application does not crash when opened and the database backend
server can accept requests. Mentor has an edit button available for
curriculum items they have assigned to their respective entrepreneur.
As a mentor, I can edit curriculum items currently assigned to my
respective entrepreneurs.
Test Plan and Cases (TPC)
Version 1.2
Table 29: TC-05-07 Entrepreneur Can View Status of Current Curriculum Items
Description: This item involves testing the ability of an entrepreneur to view curriculum items that are
currently assigned to themselves. This test case satisfies MC/DC criterion because there is a clearly defined
entry and exit point, the decision considers every possible outcome (either the item and status is displayed,
or it isn’t), and the decision tested is will be shown to impact the outcome of the decision.
Test Case Number
TC-05-07 Entrepreneur Can View Status of Current Curriculum Items
Test Item
Testing the ability of an entrepreneur to view curriculum items
currently assigned to themselves.
M: Must have
Test Priority
Pre-conditions
Post-conditions
Input Specifications
Expected Output
Specifications
Pass/Fail Criteria
Assumptions and
Constraints
Dependencies
Traceability
You must be logged into the application as an entrepreneur. You must
also have curriculum item(s) assigned to you, as you will need items to
view.
An entrepreneur will be able to view all curriculum items currently
assigned to themselves, and the status of each of these items.
An entrepreneur will be able to click to view the status of any of the
curriculum items currently assigned to themselves.
The curriculum items and status will be displayed in the application.
The system passes of the entrepreneur can view all curriculum items
and statuses of those items that are currently assigned to themselves.
The system fails if not all items, or their statuses, are displayed.
System has a working connection to the database backend and can
retrieve and store information.
This application does not crash when opened and the database backend
server can accept requests.
WC_4017: As an entrepreneur, I will have access to an individualized
curriculum.
3.6 Test Identifier 06
TS-06: Forum Functionality
3.6.1
Test Level
System Testing
3.6.2
Test Class
Erroneous testing and simulated testing
3.6.3
Test Completion Criteria
All test cases should pass.
Test Plan and Cases (TPC)
3.6.4
Version 1.2
Test Cases
Table 30: TC-06-01 Forum Functionality User Access
Description: Forum functionality – user must be able to see all forum posts available to them. Test verifies
a core functionality requirement.
Test Case Number:
Test Item:
Test Priority:
Pre-conditions:
Post-conditions:
Input Specifications:
Expected Output
Specifications:
Pass/Fail Criteria:
Assumptions &
Constraints:
Dependencies:
Traceability:
TC-06-01
Forum functionality – user access
Want to have – medium priority
Tester should have access to multiple active account profiles, both regular
and admin users
All users (regular and admin) must be able to view all public forum posts, and
no private posts for other users
A valid and active user account
User should be able to browse through all public forum topics and see all
posts. Private forum topics should not be visible.
PASS: Results match expected output, otherwise FAIL
Test assumes user accounts are set up and working properly
TC-03
WC_4146 – As a user, I can access the community forum
Table 31: TC-06-02 Forum Functionality User Contribution
Description: Forum functionality – user must be able to post on public topics and private topics he/she is a
member of. Test verifies a core functionality requirement.
Test Case Number:
Test Item:
Test Priority:
Pre-conditions:
Post-conditions:
Input Specifications:
Expected Output
Specifications:
Pass/Fail Criteria:
Assumptions &
Constraints:
Dependencies:
Traceability:
TC-06-02
Forum functionality – user contribution
Want to have – medium priority
Tester should have access to multiple active account profiles, both regular
and admin users. Forum should have a couple of public topics as well as a
couple of private ones for each test user.
All users (regular and admin) must be able to post in all public forum topics,
and only in private topics for the users is a member of.
A valid and active user account
See post conditions. As in TC-06-01, users should not be able to see forum
topics not available to them.
PASS: successful posts in all expected forum topics, otherwise FAIL
Test assumes user accounts are set up and working properly
TC-03, TC-06-01
WC_4142 – As a user, I can post on the general forum
Test Plan and Cases (TPC)
Version 1.2
Table 32: TC-06-03 Forum Functionality Post Editing
Description: Forum functionality – user must be able to edit their own posts. Test verifies a core
functionality requirement.
Test Case Number:
Test Item:
Test Priority:
Pre-conditions:
Post-conditions:
Input Specifications:
Expected Output
Specifications:
Pass/Fail Criteria:
Assumptions &
Constraints:
Dependencies:
Traceability:
TC-06-01
Forum functionality – post editing
Want to have – medium priority
Tester should have access to multiple active account profiles, both regular
and admin users, and a couple of posts already on the forum
All users (regular and admin) have at least one post edited
A valid and active user account
All edited posts should have the updated content, and should have a
notification indicating that the post was edited with a timestamp.
PASS: Results match expected output, otherwise FAIL
Test assumes user accounts are set up and working properly, and users are
able to post on the forum
TC-03, TC-06-01, TC-06-02
WC_4142 – As a user, I can post on the general forum
Table 33: TC-06-04 Forum Fuctionality Post Deletion
Description: Forum functionality – user must be able to delete their own posts. Admins should have the
ability to delete any post. Test verifies a core functionality requirement.
Test Case Number:
Test Item:
Test Priority:
Pre-conditions:
Post-conditions:
Input Specifications:
Expected Output
Specifications:
Pass/Fail Criteria:
Assumptions &
Constraints:
Dependencies:
Traceability:
TC-06-01
Forum functionality – post deletion
Want to have – medium priority
Tester should have access to multiple active account profiles, both regular
and admin users, and a couple of posts already on the forum
All users (regular and admin) have at least one post deleted, at least one
admin has deleted another user’s post
A valid and active user account
Deleted posts should have their entire content removed and have a “deleted
post” notification in the place of the original content. Database should still
have an entry for the post except with the content removed and an additional
timestamp for when the post was deleted.
PASS: Results match expected output, otherwise FAIL
Test assumes user accounts are set up and working properly, and users have a
couple of posts on the forum
TC-03, TC-06-01, TC-06-02, TC-06-03
WC_4142 – As a user, I can post on the general forum
Table 34: TC-06-05 Forum Functionality Content Variety
Description: Forum functionality – user should be able to post a variety of content in the forums, including
various images and even embedded videos.
Test Case Number:
TC-06-05
Test Plan and Cases (TPC)
Test Item:
Test Priority:
Pre-conditions:
Post-conditions:
Input Specifications:
Expected Output
Specifications:
Pass/Fail Criteria:
Assumptions &
Constraints:
Dependencies:
Traceability:
Version 1.2
Forum functionality – content variety
Want to have – medium priority
Tester should have access to at least one valid user account
All content desired in posts are shown correctly on the forum
A valid and active user account, and the following post content to test:
1) Blank post
2) Post with only white space
3) Post with a large number of ASCII characters
4) Embedded image
5) URL hyperlink to another site
6) Embedded video
Corresponding expected outputs:
1) Should not allow user to submit post
2) Should not allow user to submit post
3) Should show all the text
4) Should show image in post
5) Should display valid hyperlink to desired website
6) Should show the video in the post
PASS: Results match expected output, otherwise FAIL
Test assumes user accounts are set up and working properly
TC-03, TC-06-01, TC-06-02
WC_4142 – As a user, I can post on the general forum
Test Plan and Cases (TPC)
Version 1.2
4. Resources and schedule
Updated
Milestones and Products
Oct-16 Nov
As of 2/14/2017
Dec
Jan-17
Feb
March
April
3w 4w 1w 2w 3w 4w 1w 2w 3w 4w 1w 2w 3w 4w 1w 2w 3w 4w 1w 2w 3w 4w 1w 2w 3w 4w 5w
Milestone
DCR
RDCR
Description
iOS App core capability
Prototype for overall architecture
Input profile data
Document
Connect to Web Server
Code Review CCD
Pilot
Key features
Match users
Homework
Algorithm prototype
Forum, Feed
4PM
DCR
TRR
RDCR
OCR
Assess qualityCodeReview
Legend
Done
TRR
CCD
Plan
OCR
3PM
Architecture
Analyze for key usecase scenario
3PM
Key mechanisms
Quality assessment
1PM
Assess COTS (budget, performance, security, etc)
iOS App
Maintenance guide
…
Sample matching algorithm
8PM
Connect to Backend service
Key features
GUI implementation
4PM
Backend
Server
4PM
Test case scenario/ Regression Test
Implement algorithm
Tune-up algorithm
SECTION TITLE | 2
Stress/Scalability Test
2PM
4PM
3PM
PM: Person-Month (Total: 36PM, Left: 27PM)
Figure 1: Project Plan
We plan to execute Stress / Scalability testing during 3rd milestone (CCD), if possible. Finally, we will
assess the quality of our system and report it to the client by the end of 4 th milestone (TRR); testing should
be completed by this milestone, testing all core capabilities.
4.1 Resources
4.1.1
Data set




Mentor data (10,000 order)
Matching sample
o Including correct mentor matching candidates with a mentee information (10 - 100
order)
Mentee data (10,000 order)
o These data are used for scalable test that all the mentee use this application at the
same time
Curriculum data (10 – 100 order)
Test Plan and Cases (TPC)
4.1.2
Version 1.2
Software
- Unit Test
- Xcode (for iOS application)
- This IDE has a feature of code coverage
- UnitJS (for backend server)
- Integration Test
- Jenkins
4.2 Staffing and Training Needs
- Test Manager & Designer
- Tatsuhiko (Tats) Tomita
- Test Designer & Preparation
- Hamed Sadeghi
- Test Executer & Reviewer & Resolver
- All of developers
- Test Authorizer
- Kurling (Client)
4.3 Schedule
Table 35: Testing Schedule
Date
Test Identifier
03/13/17
TS-01: Communication
Channel - Private
Messaging.
TS-02: CreateAccount
TS-03: MentorEntrepreneur Matching
2/10/17
03/13/17
2/10/17
03/13/17
03/13/17
TS-04: Custom Profile
TS-05: Curriculum
Content
TS-06: Forum
Functionality
Responsible
person
Arik Oganesian
Resources
Training needs
Junit
N/A
Hamed Sadeghi
Dennis Xiang
Junit
JUnit
Mentor/Mentee data
set
Junit
Junit
Curriculum data
Junit
N/A
Hamed Sadeghi
Marco Alvarez
Steven Holland
N/A
N/A
N/A