-
-
Notifications
You must be signed in to change notification settings - Fork 57
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add Playwright tests for project creation workflow #1355
Comments
A good option for this is to use Playwright to test the project creation workflow. I propose we implement this on the frontend. |
We have just got started with playwright, will keep you updated on this further @spwoodcock |
Oh very nice, I was just about to do the same - I'll leave you to it! Let me know if I can help with the dependencies part - we could make a config to run the tests via docker with all dependencies bundled by default (browsers etc) 👍 |
Looks like Playwright needs some system dependencies:
|
@spwoodcock my playwright install is showing weird issue do you know anything about this ? |
Any Linux distribution apart from Ubuntu is not 'officially' supported, but should probably work fine. |
hmm yeah it worked but kept giving warning but thats fine i guess. Thanks sam |
Is your feature request related to a problem? Please describe.
The purpose of a test case is to determine if different features within a system are performing as expected and to confirm that the system satisfies all related standards, guidelines and customer requirements. The process of writing a test case can also help reveal errors or defects within the system.
We have very limited test cases in the platform, which is making the platform unstable with every release.
Describe the solution you'd like
Here are the list of the test case scenario, relevant conditions they need to pass and the expected results out of the test cases.
https://docs.google.com/spreadsheets/d/1z4ctAquRcpXRam5Sb0cnqXT6asAzkwe42MPhV8szH6U/edit#gid=0
How can you start writing down the test cases?
A comprehensive demo of what is in the sheet is outlines with a an example.
Step 1: There is a test case scenario in the Test Case Scenario column:
Eg: Uploading project boundary during project creation
Step 2: You can manually replicate the condition as viewed in Test Steps column:
Eg:
Step 3: The condition you need to pass for the test is viewed in Pre-condition column:
Eg: User should be able to upload the file with .geojson format only. Please check if the file loads well with geojson.io before uploading the geojson.
Step 4: The expected result after you pass for the test is in Expected Result column:
Eg: The input should throw error "File format is not supported" if the user uploads any other file except .geojson format.
Step 5: You may write down the actual results after you run the test cases you prepare that is an exception to that of expected result
Step 6: The status column defines if the test case is passed or failed
The text was updated successfully, but these errors were encountered: