Difference between revisions of "IS480 Team wiki: 2018T1 Kaki&Kin/Documentations/Testing"
Jump to navigation
Jump to search
Line 40: | Line 40: | ||
<tr> | <tr> | ||
<td>-Feedback was recorded from a questionnaire</td> | <td>-Feedback was recorded from a questionnaire</td> | ||
+ | </tr> | ||
+ | <tr> | ||
+ | <td>Proposed system was rated as easier to use than current system</td> | ||
</tr> | </tr> | ||
Line 60: | Line 63: | ||
<br> | <br> | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
<br> | <br> | ||
<table border: 1px;> | <table border: 1px;> |
Revision as of 12:45, 22 September 2018
Acceptance User Testing
Overview |
---|
-Conducted at KeyReply’s office on 14 August 2018 |
-Four test subjects had to do a series of tasks on the prototype new system |
-Feedback was recorded from a questionnaire |
Proposed system was rated as easier to use than current system |
Test subjects from KeyReply |
-CTO |
-Chatbot Trainer |
-Developer |
-UI/UX Designer |
Task | Recommendation | Average Rating (1 - very easy, 6 very hard) |
---|---|---|
Uploading a text file into the system | 1. More explanation of the types of accepted files
2. Show indication of upload progress |
1.75 |
Finding a generated intent | 1. Font too small
2. Hard to click 3. Graph lines small and redundant |
3 |
Editing a sentence related to an intent | 1. Should tell users that enter key can be used
2. Guide the users to the empty fields 3. Unclear that variations can be deleted |
2 |
Adding alternative sentences for an intent | 1. Should tell users that enter key can be used
2. Guiding text is too lengthy 3. No clear indication that fields are for variations 4. Have a button to ‘Add’ new fields |
2.25 |
Adding a chatbot response/answer to an intent | 1. Guiding text is too lengthy and unclear
2. Have a button to ‘Add’ answer 3. Not obvious where to input answer |
2.5 |
Mid-Terms User Testing
Finals User Acceptance Testing
Pre-Acceptance: General back-End/NLP
Bug Description | Frontend / Backend | Tester | Date Found | Severity | Points Allocation | Resolved? | Cause | Action | Debugged By | Debugged Date | Current Points |
---|---|---|---|---|---|---|---|---|---|---|---|
CORS concerns on backend that does not allow front end to connect | Backend | Aaron | 8-Aug-18 | High Impact | 8 | Resolved | Allow(*) for cors, removed subscription option, false for websockets only | Went down to KR to understand how they set up graph QL | LiXuan | 9-Aug-18 | 0 |
Deployment to heroku unsuccessful | Backend | Li Xuan | 10-Aug-18 | High Impact | 8 | Resolved | server.js not found | Need to commit js files, not ts! Added a procfile | LiXuan, Zachery | 13-Aug-18 | 0 |
Pre-Acceptance: Upload Module
Bug Description | Frontend / Backend | Tester | Date Found | Severity | Points Allocation | Resolved? | Cause | Action | Debugged By | Debugged Date | Current Points |
---|---|---|---|---|---|---|---|---|---|---|---|
GraphQL runs on run time | Frontend | Eugene | 16-Aug-18 | High Impact | 5 | Resolved | Codes were executed on runtime | Execute the 'Skip' method in export function of GraphQL | Aaron | 16-Aug-18 | 0 |
Error thrown when read text file contents | Backend | Eugene | 16-Aug-18 | High Impact | 5 | Resolved | The uploaded object was not read as a text object | JSON.stringify() | Aaron | 16-Aug-18 | 0 |
Upon reading file, variables were not updated | Frontend | Eugene | 16-Aug-18 | High Impact | 5 | Resolved | The GraphQL server skip() function was not used | - | Aaron | 16-Aug-18 | 0 |
GraphQL not receiving string Object in Query | Front | Eugene | 16-Aug-18 | High Impact | 5 | Resolved | The variable required was not converted into a JSON object | Convert the variable into JSON object first | Aaron | 16-Aug-18 | 0 |
Pre-Acceptance: Edit Visualisation
Bug Description | Frontend / Backend | Tester | Date Found | Severity | Points Allocation | Resolved? | Cause | Action | Debugged By | Debugged Date | Current Points |
---|---|---|---|---|---|---|---|---|---|---|---|
Error in data structure of flattened data returned | Frontend | Eugene | 14-Aug-18 | High Impact | 5 | Resolved | Parsing and converting to string for JSON | Fixed the issues in the JSON template | Zachery | 16-Aug-18 | 0 |
Error on JSON file used for testing | Frontend | Eugene | 14-Aug-18 | High Impact | 5 | Resolved | Wrong assignment of variable | Changed the assignment of variable | Zachery | 16-Aug-18 | 0 |
Pre-Acceptance Manage Content Node
Bug Description | Frontend / Backend | Tester | Date Found | Severity | Points Allocation | Resolved? | Cause | Action | Debugged By | Debugged Date | Current Points |
---|---|---|---|---|---|---|---|---|---|---|---|
Table not updated | Frontend | Eugene | 14-Aug-18 | Critical Impact | 10 | Resolved | JSON object deep freezed. | Requires parsing and stringify of return object | Zachery | 16-Aug-18 | 0 |
Pre-Acceptance: Review Visualisation
Bug Description | Frontend / Backend | Tester | Date Found | Severity | Points Allocation | Resolved? | Cause | Action | Debugged By | Debugged Date | Current Points |
---|