Acceptance test cases

Acceptance test case 1

Test case ID: TC-1

Use Case ID: UC-1

Main success scenario tests

• Initial system state/inputs
  • The user (not logged in to the system) chooses to open proof #1 in the system.
  • Proof #1 exists in the system.
• Expected system state/outputs
  • Proof #1 is displayed for the user.
  • The user has the option to expand and collapse the sections of proof #1.
  • The user can close proof #1.

Alternative scenario tests

• Initial system state/inputs
  • The poweruser (logged in to the system) chooses to open proof #1 in the system.
  • Proof #1 exists in the system.
• Expected system state/outputs
  • Proof #1 is displayed for the poweruser.
  • The poweruser has the option to expand and collapse the sections of proof #1.
  • The poweruser can close proof #1.
  • The poweruser can delete proof #1 from the system.
  • The poweruser can start editing proof #1.

Acceptance test case 2

Test case ID: TC-2

Use Case ID: UC-2

Main success scenario tests

• Initial system state/inputs
  • There are 5 proofs in the system, the id of the proof added latest is 5.
  • The poweruser adds a new proof to the system by
    • adding all or some of the sections to the proof and
    • saving the proof.
• Expected system state/outputs
  • The number of proofs in the system is 6.
  • The id of the proof added latest is 6.
  • The system displays proof #6 for the poweruser.

Alternative scenario tests

• Initial system state/inputs
  • There are 5 proofs in the system, the id of the proof added latest is 5.
  • The poweruser adds a new proof to the system by
    • adding all or some of the sections to the proof and
    • not saving the proof.
• Expected system state/outputs
  • The number of proofs in the system is 5.
  • The id of the proof added latest is 5.
  • The system displays the main page for the poweruser.
• Initial system state/inputs
  • There are 5 proofs in the system, the id of the proof added latest is 5.
  • The user is not logged in to the system and goes manually to the proof creation page
• Expected system state/outputs
  • A message is displayed asking the user to log in in order to create a theorem.

Acceptance test case 3

Test case ID: TC-3

Use Case ID: UC-14

Main success scenario tests

• Initial system state/inputs
  • The user is not logged in to the system.
  • The user has a valid GitHub account.
  • The user uses their GitHub account to sign in to the system.
• Expected system state/outputs
  • The user is logged in to the system.
  • A button with the text 'Sign out' is present on the page of the system.

Alternative scenario tests

• Initial system state/inputs

  • The user does not have a GitHub account.
  • The user tries to sign in to the system.

• Expected system state/outputs

  • The user is directed to the page where they can enter GitHub credentials
  • There is also an option to create a GitHub account
  • The user is not signed in to the system

• Initial system state/inputs

  • The user has a GitHub account.
  • The user tries to sign in to the system, but inserts either the username or password incorrectly

• Expected system state/outputs

  • There is a message saying that the credentials were not correct.
  • The user can try signing in again.

• Initial system state/inputs

  • The user has a GitHub account.
  • The user signs in to the system.
  • The user signs out from the system.

• Expected system state/outputs

  • The user is signed out from the system.
  • A button with the text 'Sign in' is present on the page.

Acceptance test case 4

Test case ID: TC-4

Use Case ID: UC-4

Main success scenario tests

• Initial system state/inputs
  • The poweruser is logged in to the system and is creating a new theorem.
  • The poweruser types in the following theorem claim: No three positive integers $a,b,$ and $c$ satisfy the equation $a^n+b^n=c^n.$
• Expected system state/outputs
  • The input is rendered in the theorem preview part as shown in the image below:

Alternative scenario tests

• Initial system state/inputs
  • The poweruser is logged in to the system and is creating a new theorem.
  • The poweruser types in the following theorem claim: No three positive integers $a,b,$ and $c$ satisfy the equation $$a^n+b^n=c^n.$$
• Expected system state/outputs
  • The input is rendered in the theorem preview part as shown in the image below:

Acceptance test case 5

Test case ID: TC-5

Use Case ID: UC-7

Main success scenario tests

• Initial system state/inputs
  • The poweruser is logged in to the system and is creating a new theorem.
  • The poweruser uses the following inputs:
    • claim: Theorem claim
    • step1: This is the first step of the theorem.
    • step2: As shown in step ##1## which is the first step of the theorem.
    • step3: That was already shown in step ##2##.
• Expected system state/outputs
  • In the theorem preview part the number 1 is coloured differently and hovering over it changes the background of step1.
  • In the theorem preview part the number 2 is coloured differently and hovering over it changes the background of step2.

Alternative scenario tests

• Initial system state/inputs
  • The poweruser is logged in to the system and is creating a new theorem.
  • The poweruser uses the following inputs:
    • claim: Theorem claim
    • step1: This is the first step of the theorem.
    • step2: As shown in step ##1## which is the first step of the theorem.
    • step3: That was already shown in step ##4##.
• Expected system state/outputs
  • In the theorem preview part the number 1 is coloured differently and hovering over it changes the background of step1.
  • In the theorem preview part the number 4 is coloured differently but hovering over it does not change the background of any of the steps.