Files

Mole 94774113f6 V11: Fix InMemoryAuto modelsbuilder mode (#13107 )

* POC of a solution that works

* Add razor reference manager

* Ensure the compilation options are correct

* Move InMemory classes to its own namespace

These are all internal, so it should be fine.

* Throw proper exceptions when compilation fails

* Add CheckSumValidator

* Clear the ViewCompiler cache when models changed

This means we no longer need the RefreshingRazorViewEngine \o/

* Remove unused constructor injection

* Make UmbracoAssemblyLoadContext non internal

* Add WIP

* Clear the RazorViewEngine cache when generating new models

This uses reflection, which isn't super nice, however, the alternative is to clone'n'own the entire RazorViewEngine, which is arguably worse

* Fix circular dependency

* Remove ModelsChanged event

This is no longer necessary

* Fix precompiled views path

We need to normalize these paths to ensure they matches with the keys in _precompiledViews

* Clean

* Fix content tests

* Add logging

* Update the comment in UmbracoBuilderDependencyInjectionExtensions to reflect changes

* Remove RefreshingRazorViewEngine as its no longer needed

* Remove unused ViewEngine hack from DI

* Fix langversion

This is required since dotnet 7 is still in preview

* Add modelsbuilder tests

* Add more tests

* fixed comment

Co-authored-by: Bjarke Berg <mail@bergmania.dk>

2022-10-07 10:42:32 +02:00

fixtures/mediaLibrary

v11: Merge v10/feature/project-cleanup into v11/dev (#13112 )

2022-10-05 12:14:43 +02:00

misc

Merge branch 'v10/dev' into v11/merge/merge-v10-to-v11

2022-10-05 14:29:41 +02:00

tests

V11: Fix InMemoryAuto modelsbuilder mode (#13107 )

2022-10-07 10:42:32 +02:00

config.js

v11: Merge v10/feature/project-cleanup into v11/dev (#13112 )

2022-10-05 12:14:43 +02:00

createTest.js

v11: Merge v10/feature/project-cleanup into v11/dev (#13112 )

2022-10-05 12:14:43 +02:00

package-lock.json

v11: Merge v10/feature/project-cleanup into v11/dev (#13112 )

2022-10-05 12:14:43 +02:00

package.json

v11: Merge v10/feature/project-cleanup into v11/dev (#13112 )

2022-10-05 12:14:43 +02:00

playwright.config.ts

v11: Merge v10/feature/project-cleanup into v11/dev (#13112 )

2022-10-05 12:14:43 +02:00

postinstall.js

v11: Merge v10/feature/project-cleanup into v11/dev (#13112 )

2022-10-05 12:14:43 +02:00

README.md

v11: Merge v10/feature/project-cleanup into v11/dev (#13112 )

2022-10-05 12:14:43 +02:00

README.md

Umbraco Acceptance Tests

Prerequisites

NodeJS 16+
A running installed Umbraco on url: https://localhost:44331 (Default development port)
- Install using a SqlServer/LocalDb as the tests execute too fast for Sqlite to handle.

Getting started

The tests are located in the project/folder as Umbraco.Tests.AcceptanceTests. Make sure you run npm ci & npx playwright install in that folder, or let your IDE do that.

The script will ask you to enter the username and password for a superadmin user of your Umbraco CMS.

Executing tests

There are two npm scripts that can be used to execute the test:

npm run test
- Executes the tests headless.
npm run ui
- Executes the tests in a browser handled by a playwright application.

In case of errors it is recommended to use await page.pause() so you can step through your test.

Environment Configuration

The environment configuration is begin setup by the npm installation script. This results in the creation of this file: .env. This file is already added to .gitignore and can contain values that are different for each developer machine.

The file has the following content:

UMBRACO_USER_LOGIN=email for superadmin
UMBRACO_USER_PASSWORD=password for superadmin
URL=https://localhost:44331

You can change this if you like or run the config script to reset the values, type "npm run config" in your terminal.