(Translated by https://www.hiragana.jp/)
es20al_19-project/P4.md at develop · afonsocrg/es20al_19-project · GitHub
Skip to content

Latest commit

 

History

History
396 lines (272 loc) · 30 KB

P4.md

File metadata and controls

396 lines (272 loc) · 30 KB
Raw

ES20 P4 submission, Group 19

Feature PPA

Subgroup

  • Afonso Gonçalves, ist189399, afonsocrg

  • Daniel Seara, ist189427, Beu-Wolf

    • Tasks / Issues assigned:
      • F6: Service (#212), Spock Tests (#211), Web Service (#209), JMeter Tests (#207), Frontent (#204), Cypress use case Tests (#202)
      • F7.1: Service (#241), Spock Tests (#242), Web Service (#243), JMeter Tests (#244), Frontent (#245), Cypress use case Tests (#246)
      • F7.2: Service (#271), Spock Tests (#272), Web Service (#273), JMeter Tests (#274), Frontent (#275), Cypress use case Tests (#276)
      • F8: Service (#290), Spock Tests (#291), Web Service (#292), JMeter Tests (#293), Frontent (#294), Cypress use case Tests (#295)

Pull requests associated with this feature

The list of pull requests associated with this feature is:

Listed features

Below, we list only the implemented features. For each feature, we link the relevant files and we mark which are requested parts are completed.

F4: Uma questão aprovada pode passar a fazer parte do conjunto de perguntas disponíveis

  • Service (Reused already defined service. A promotion is still an evaluation)

  • Spock tests

  • JMeter feature tests (Since F4 and F5 were very similar, it was used the same file to test them)

    • Screenshots:

      Test results

  • Cypress use case test (Since F4 and F5 were very similar, it was used the same file to test them)

    • Screenshot:

      Test results

F5: Um docente pode alterar uma pergunta aprovada antes de a colocar como fazendo parte do conjunto de perguntas disponíveis

  • Service (Reused already defined service. A promotion is still an evaluation)

  • Spock tests

  • JMeter feature tests (Since F4 and F5 were very similar, it was used the same file to test them)

    • Screenshots:

      Test results

  • Cypress use case test (Since F4 and F5 were very similar, it was used the same file to test them)

    • Screenshot:

      Test results

F6: Uma pergunta rejeitada pode ser alterada e resubmetida pelo aluno

F7: Existe um dashboard do aluno onde é apresentada informação acerca do seu número de perguntas propostas e aprovadas

NOTE: In order for the feature to run, a sql script needs to be loaded to add stats to already created users.

F8: O aluno decide se esta informação no seu dashboard deve ser pública ou privada

NOTE: In order for the feature to run, a insert_stats.sql needs to be loaded to add stats to already created users.

Additional features

Notes The student question evaluation specification changed a little: An Approved question can now be Rejected (F11). Altough it had a name of a feature, it's not considered a new feature. It only needed some verification tweaks and test correction.

Feature DDP

Subgroup

  • André Breda, ist189409, abread

    • Tasks / Issues Assigned:
      • F4: Service (#214), Spock Tests (#215), Web Service (#216), JMeter Tests (#217), Frontent ()#218, Cypress use case Tests (#219)
      • Refactoring

  • Mariana Oliveira, ist189504, tpoliveira-mariana

    • Tasks / Issues Assigned:
      • F5: Service (#220), Spock Tests (#221), Web Service (#222), JMeter Tests (#223), Frontend (#224), Cypress use case Tests (#225)
      • F6: Service (#228), Spock Tests (#229), Web Service (#230), JMeter Tests (#231), Frontend (#232), Cypress use case Tests (#233)
      • F7: Service (#249), Spock Tests (#250), Frontend (#253), Cypress use case Tests (#254)
      • F8: Service (#305), Spock Tests (#306), Web Service (#307), JMeter Tests (#308), Frontend (#309), Cypress use case Tests (#310)
      • Dashboard Creation: #241, #243, #245

    NOTE: Issues #251 and #252 exist, but required nothing to be done.

Pull requests associated with this feature

The list of pull requests associated with this feature is:

Listed features

Below, we list only the implemented features. For each feature, we link the relevant files and we mark which are requested parts are completed.

F4: O aluno pode pedir esclarecimentos adicionais

F5: O docente pode tornar a questão e o seu esclarecimento disponível para os outros alunos

F6: Um aluno, após responder a uma pergunta, pode consultar, se existirem, os pedidos de esclarecimento sobre essa pergunta e as respostas dadas

F7: Existe um dashboard do aluno onde é apresentada informação acerca de quantos pedidos de esclarecimento efetuou e quantos deles foram lhe foram creditados

NOTE: In order for the feature to run, a sql script needs to be loaded to add stats to already created users.

Feature number 8: O aluno decide se esta informação no seu dashboard deve ser pública ou privada

NOTE: In order for the feature to run, a sql script needs to be loaded to add stats to already created users.

Feature TDP

Subgroup

  • Lourenço Ramos Duarte, ist197023, LourencoPonces
    • Tasks / Issues Assigned:
      • F4: Service (#257), Spock Tests (#258), Web Service (#259), JMeter Tests (#260), Frontend (#261), Cypress use case Tests (#262)
      • F7: Service (#278), Spock Tests (#279), Web Service (#280), JMeter Tests (#281), Frontend (#282), Cypress use case Tests (#283)
      • F8: Service (#347), Spock Tests (#348), Web Service (#349), JMeter Tests (#350), Frontend (#351), Cypress use case Tests (#352)
      • F9: Service (#234), Spock Tests (#235), Web Service (#236), JMeter Tests (#237), Frontend (#238), Cypress use case Tests (#239)
  • Marcelo Santos, ist189496, tosmarcel
    • Tasks / Issues Assigned:
      • F5: Service (#263), Spock Tests (#264)
      • F6: Service (#312), Spock Tests (#313), Web Service (#314), JMeter Tests (#315), Frontend (#316), Cypress use case Tests (#317)
      • F11: Service (#332), Spock Tests (#333), Web Service (#334), JMeter Tests (#335), Frontend (#336), Cypress use case Tests (#337)

Pull requests associated with this feature

The list of pull requests associated with this feature is:

Listed features

Below, we list only the implemented features. For each feature, we link the relevant files and we mark which are requested parts are completed.

F4: O aluno que criou o torneio pode cancelá-lo

F5: Se o número de alunos inscritos, incluindo o criador do torneio, for superior a 1, o sistema gera o quiz associado ao torneio

F6: Os alunos participantes respodem às perguntas no período definido para o torneio

F7: Existe um dashboard do aluno onde é apresentada informação acerca dos torneios em que participou e qual a sua pontuação & F8: O aluno decide se esta informação no seu dashboard deve ser pública ou privada

NOTE: In order for the feature to run, a sql script needs to be loaded to add stats to already created users.

Additional features

F9: Os alunos podem aceder aos seus torneios criados

F11: Os alunos podem aceder aos torneios em que estão inscritos e estão em execução