Skip to content

Enhance e2e testing

Gregory Giapa requested to merge giapa/universis-students:enhance-e2e-testing into master

Adding tests to the following cases:

  • Login page cases:
    • Title check
    • Unsuccessful login
    • Language change
    • Successful login
  • Dashboard page
    • Title check
    • Change language
    • Change language back
  • Profile page
    • Title check
  • Registrations page
    • Title check (Registration list only)
  • Grades page
    • Title check (Recent, All, Theses categories)
  • Messages page
    • Title check
  • Support page
    • Title check

The tests are following the Page Object Model. *.po.ts contains the selectors of elements *.e2e-spec.ts contains the jasmine tests

protractor.conf.js is changed to run all the tests mentioned above and configure properly the webdriver. Also, there were HTML reports added for the tests containing information about the tests and screenshots of the failing ones.

Developer Checklist

  • I have successfully run the code of this merge request locally

  • I have verified locally that my changes work for all necessary screen sizes

  • I have tried out the changes of this MR with different users to identify bugs

  • Coding is in progress, and I have marked the MR as WIP

  • Coding is completed and the MR is ready for review

  • My branch is up-to-date with the upstream master branch

  • My MR follows the contribution guidelines

  • I have added a comment with screenshots of the code running locally

Tech review Checklist

Have you verified that what is supposed to happen, actually does, and what is not supposed to happen, indeed does not?

  • The MR accurately describes the changes and has a relevant title/description
  • The MR does what it is supposed to according to its title, description and related issues/links
  • I have successfully run the changes locally, and tried the new code

Overall review Checklist

  • The MR references related issues/MRs
  • The MR provides links to screens and screenshots
  • The commits of the MR describe the changes, have proper wording, and follow the guidelines
  • I have successfully run the changes locally, and tried the new code
  • The MR is ready for merge (rebased, commit squashed if needed, etc)
Edited by Gregory Giapa

Merge request reports