UI test setup

[S-Panta]

Set up UI test in Moodle that uses oCIS as the repository.

• Setup PlayWright for running tests locally. playwright setup and implementation of listFolder Step #14
• Setup test in CI.

One of the preconditions of the test is to make sure your Moodle gets access to oCIS. After Oauth2 access is granted, one has to log in to the oCIS once when they select oCIS for upload and choose allow when it asks for permission to read files from oCIS. Note: This process should be done only once.

[PhMemmel]

Like described in #24 I very much recommend to use the moodle behat framework. Everything is already prepared including pipeline setup etc., one just has to write the feature files including the scenarios. The pipeline will spawn up a complete blank and preconfigured moodle instance, you can then configure the settings for your UI test directly in the feature file. See https://moodledev.io/general/development/tools/behat

[amrita-shrestha]

@nirajacharya2 is there more tests to add? please make list of scenario if there is any

[nirajacharya2]

• uploading resource to moodle
  - from personal space adding behat ui test #34
  - from shares adding test for file upload in share space #90
  - from project space UI test for creating file in project space #88
• does the refresh button show latest state of ocis (open file picker with ocis selected, add file in ocis click refresh button does the file show? ) adding test for refresh button #106
• navigating using the links in file picker adding test for navigating using links in file picker #108
• enable/disable sync of shared resource added feature file and step definition for enabling and disabling sync of share #107 [enable sync on stable branch has some bug, this scenario is skipped on stable branch [https://github.com/enabling sync of share gives empty filename as response ocis#8961]
  plugin setting related tests
• Disabling spaces changing visibility of a drive in plugin setting #89
  - personal space
  - shares
  - project space
• setting image for spaces adding tests for setting thmbnail for spaces #100
  - personal space
  - shares
  - project space
• adding ocis oAuth setting not needed because not part of the app

[S-Panta]

Should the steps in feature file be written like this? These steps can be found in many feature files that are inside moodled. I suggest we write these things clearly and inside step definition we call the function that this steps is calling?
For example we can write When I click on Personal drive instead of When I click on "//*[@class='fp-filename-field']/p[text()='Personal']" "xpath_element"
@individual-it @amrita-shrestha @phil-davis @nirajacharya2

[individual-it]

I think I would prefer to have the xpath hidden in the php function (inside a page object) and not written out in the feature file

[phil-davis]

I think I would prefer to have the xpath hidden in the php function (inside a page object) and not written out in the feature file

I agree.

Do "the moodle people" allow us to create our own step definitions with human-friendly words?
Or do we have to use the steps-for-technical-nerds that moodle already has?

[individual-it]

I think for our own steps we can do whatever we want, but should be still consistent with the moodle way.
I just feel having the xpath in the step definition will get us into trouble

[S-Panta]

This issue can be closed as the UI test for moodle is completed.