Tests for error pages

[saulipurhonen]

Description

Test that error situations trigger corresponding error pages.

Related issues

Closes #120

Type of change

• New feature (non-breaking change which adds functionality)

Changes Made

• Intercept 403 and 500 errors
• Check that error pages render

Testing

• Integration Tests

[hannyle]

Cypress tests didn't pass on my local machine. First of them was an error in parseFormSchema in WizardAjvResolver.js. Probably we can try to rebase it on the latest develop branch ?
At least my tests all passed in current develop

[saulipurhonen]

Cypress tests didn't pass on my local machine. First of them was an error in parseFormSchema in WizardAjvResolver.js. Probably we can try to rebase it on the latest develop branch ?
At least my tests all passed in current develop

@hannyle you might need to clear browser cache, also check AJV version that it matches the one in package.json. AJV package update had some breaking changes and on my local the browser cache had to be cleared after npm install.

[hannyle]

Cypress tests didn't pass on my local machine. First of them was an error in parseFormSchema in WizardAjvResolver.js. Probably we can try to rebase it on the latest develop branch ?
At least my tests all passed in current develop

@hannyle you might need to clear browser cache, also check AJV version that it matches the one in package.json. AJV package update had some breaking changes and on my local the browser cache had to be cleared after npm install.

okay, I think I have the correct Ajv version. I also did try reinstall and clear cache, sadly the tests still failed. However when I locally rebased the branch, all the tests passed. :-/

[hannyle]

I will find out more the issue in my local env.
Otherwise the test was nicely done.

[saulipurhonen]

Cypress tests didn't pass on my local machine. First of them was an error in parseFormSchema in WizardAjvResolver.js. Probably we can try to rebase it on the latest develop branch ?
At least my tests all passed in current develop

@hannyle you might need to clear browser cache, also check AJV version that it matches the one in package.json. AJV package update had some breaking changes and on my local the browser cache had to be cleared after npm install.

okay, I think I have the correct Ajv version. I also did try reinstall and clear cache, sadly the tests still failed. However when I locally rebased the branch, all the tests passed. :-/

I think I've found a solution for this. On this branch we have AJV v8 but parseErrorSchema has incorrect propery name dataPath from earlier version. On your local dataPath doesn't correspond to anything and it should be instancePath as stated in AJV changelog.

I'll rebase and push into this branch.

[hannyle]

@hannyle you might need to clear browser cache, also check AJV version that it matches the one in package.json. AJV package update had some breaking changes and on my local the browser cache had to be cleared after npm install.

okay, I think I have the correct Ajv version. I also did try reinstall and clear cache, sadly the tests still failed. However when I locally rebased the branch, all the tests passed. :-/

I think I've found a solution for this. On this branch we have AJV v8 but parseErrorSchema has incorrect propery name dataPath from earlier version. On your local dataPath doesn't correspond to anything and it should be instancePath as stated in AJV changelog.

I'll rebase and push into this branch.

Right, the error was at dataPath in parseErrorSchema function. The rebase did help and my tests smoothly passed. Thanks!