Regression test

[nkylstad]

Description

Regression test before deploy w11

Additional Information

No response

Tasks

Dashboard

To test in dev.altinn.studio before prod deploy.

• [x] Log in - Covered by Playwright tests
• [x] Select Testdepartementet as org - Covered by Playwright tests
  • [x] See that only Testdepartementet apps are shown - Covered by Playwright tests
  • [x] Should be possible to sort list by name and last changed - Covered by Playwright tests
  • [x] Search for app frontend-test, and see that (at least) one app for Testdepartementet is shown - Covered by Playwright
  • [x] Click Gitea-logo and see that you are taken to the repo page for the app. Return to dashboard - Covered by Playwright
  • [x] Click Edit-app-logo and see that you are taken to the app-development pages for the app. Return to dashboard - Covered by Playwright

Create new app

• [x] Go to create new app page - covered by Playwright tests
  • [x] Try to create app with name 123-reg-test, see that there is a validation error on the name and app is not created - covered by Playwright
  • [x] Create app with name ´reg-test-new`, see that you get validation error that app already exists - covered by Playwright
  • [x] Add suffix to reg-test-new and create a new app - covered by Playwright
  • [x] Change the name of the app on the overview page to Regression test - covered by Playwright
  • [x] Check that the name is also updated in the text editor - Covered by Playwright
• [x] Go to Datamodels tab - Covered by Playwright
  • [x] upload an XSD, see that it is uploaded ok - Covered by Playwright
  • [x] Delete the uploaded data model, and see that it is deleted - Covered by Playwright
  • [x] Create a new data model named datamodel - Covered by Playwright
  • [x] Add an object and rename it to test - Covered by Playwright
  • [x] Add two string fields (name: text1 and text2) and one integer field (name: number1) to the newly added object - Covered by Playwright
  • [x] Click "Generate models" button and see that models are created OK - Covered by Playwright
• [x] Go to Lage tab - Covered by Playwright
  • [x] Add a new page - Covered by Playwright
  • [x] Add a header component to page and configure: - Covered by Playwright
  • [x] Add a header text This is a header and close - Covered by Playwright
  • [x] Add 2 input components and configure: - Covered by Playwright
  • [x] Select data model binding. If field in data model is required, see that the required checkbox is checked. - Covered by Playwright
  • [x] Add a label text - Covered by Playwright
  • [x] Add a description text - Covered by Playwright
  • [x] Re-open to see that configurations are auto-saved as expected - Covered by Playwright
  • [x] Push the changes - Covered by Playwright
  • [x] Open the layout file in repos and see that the configuration looks as expected - Covered by Playwright
  • [x] Re-name the page to `01-intro``` - Covered by Playwright
  • [x] Add a new page and rename to 02-page. - Covered by Playwright
  • [x] See that both pages now have a navigation component - Covered by Playwright
  • [ ] Delete 02-pageand see that navigation component on 01-intro is removed (known issue: #11563)
• [x] Go to Texts tab - Covered by Playwright
  • [x] See that texts added from components are shown - Covered by Playwright
  • [x] Change the id of one of the texts added from component - Covered by Playwright
  • [x] Navigate back to the Lage tab and see that the text is still shown for the component - Covered by Playwright
  • [x] open component edit mode and select edit on the text, see that the updated id is shown. - Covered by Playwright
  • [x] Navigate back to the Texts tab - Covered by Playwright
  • [x] Add a new text - Covered by Playwright
  • [x] Delete the newly added text - Covered by Playwright
  • [x] Add a new language - Covered by Playwright
  • [x] Select the new language so that both languages are shown next to each other - Covered by Playwright
  • [x] Add translations - Covered by Playwright
  • [x] Push changes and see that the respective language files are updated as expected in repo - Covered by Playwright
• [x] Create a new app for Testdepartementet
• [x] Make some changes to the application
• [x] Go to Publish tab
  • [x] Type a build version into the text field and click Build. Wait for the app to finish building
  • [x] Select the version from deploy dropdown in at23 env and deploy the app. Wait for deployment to finish
  • [x] See that URL to the environment is available
  • [x] Click the url, and log in
  • [x] See that the app looks and acts as expected

Cleanup

• [x] Go to pipelines, select altinn-apps/altinn-studio-decomission-app pipeline and run with app/org name and at23 as env to un-deploy the app
• [x] Go to Gitea and delete the app repository

[mirkoSekulic]

When changing the name should we also rename the name of the repo? It stays the same now. @nkylstad

[standeren]

I did not have access to deploy app to at23. Deployed to tt02 instead

[nkylstad]

When changing the name should we also rename the name of the repo? It stays the same now. @nkylstad

No, from the "Oversikt" tab we only change the display name (text), repo name stays the same.

[nkylstad]

I did not have access to deploy app to at23. Deployed to tt02 instead

@standeren Not a problem, but if you do need deploy access to one of the other environments at some point, you should be able to just add yourself to the relevant team in gitea.