- Afonso Fernandes, 93679, @MrIceHavoc (23041868)
- David Duque, 93698, @ddavness (45321798)
The list of pull requests associated with this feature is:
- OpenEndedAnswerDetails.ts
- OpenEndedQuestionDetails.ts
- OpenEndedStatementAnswerDetails.ts
- OpenEndedStatementCorrectAnswerDetails.ts
- OpenEndedStatementQuestionDetails.ts
- Create Question
- View Question
- Update Question
- Duplicate and Delete Question
These end-to-end tests target common operations the majority of users (i.e. teachers, in this context) would perform. As the name implies, they check everything from the front-end to the back-end of the product/service being developed.
There is one case where an error is expected. Because the "Default Correct Answer" is mandatory, some users may try to "game" the system by filling that field with spaces/newlines/etc. We want to make sure that these attempts are handled correctly.
We also have a test to change the default correct answer, as we feel this is something users would do frequently.
- Diogo Cabral, 93704, diogocabral2000
- Tiago Letra, 84627, TiagoLetra
The list of pull requests associated with this feature is:
- Teacher creates a new multiple choice question
- Teacher can view a new multiple choice question (with button)
- Teacher can view a new multiple choice question (with click)
- Teacher can update title (with right-click)
- Teacher can update content (with button)
- Teacher can duplicate a multiple choice question
- Teacher can delete a multiple choice question
- Teacher creates a multiple choice question with 10 options and 4 options true and with order of relevance
End-to-End tests are defined for the common use cases to test the code from beginning to end, to check that the code runs as expected, making sure that the subsystems work well together, since a problem in one could mean the whole system fails. The tests are made from the point of view of the user to simulate a real scenario of a person using the final product. End-to-End testing brings benefits since it reduces the number of bugs present in the code and ensures the code runs correctly.
- Maria Beatriz Venceslau, ist193734, @BeatrizVenceslau (47870321)
- Carolina Ramos, ist19694, @Carolina-Ramos (56026621)
The list of pull requests associated with this feature is:
- Item.ts
- CombinationItem.ts
- CombinationQuestionDetails.ts
- CombinationItemStatement.ts
- CombinationStatementQuestionDetails.ts
- Create:
- Creates a new item combination question
- View:
- Can view item combination question (with button)
- Can view item combination question (with click)
- Update:
- Can update title (with right-click) on item combination question
- Can update content (with button) on item combination question
- Duplicate:
- Can duplicate item combination question
- Delete:
- Can delete created item combination question
End-to-End tests are defined for the common use cases to test the code from beginning to end, to check that the code runs as expected, making sure that the subsystems work well together, since a problem in one could mean the whole system fails. The tests are made from the point of view of the user to simulate a real scenario of a person using the final product. End-to-End testing brings benefits since it reduces the number of bugs present in the code and ensures the code runs correctly.