Test property for resources

[TheTechArch]

Description

We need test property for resources

Additional Information

When returning data from Altinn 2 from ACN and TTD set test = true in list api

Tasks

No response

Acceptance Criterias

No response

[sorensensig]

Problem

Some test-resources show up in the production environment, arguably due to the service owner wanting to live-test in production. As a side effect of test-services showing up for every user in the production environment the first 3.5 pages of "delegating single rights" contains only test-services and no real services, resulting in poor user experience when browsing through services to delegate. Moreover, it poses the question: are we certain that users won't be able to access content they should not be able to using these services?

Example:

Figure 1: Showing page four of the user interface, where the first real service is located when browsing

Suggestion

If service owners wish to live-test their services in production, we might have to look into providing them with A/B split-testing, feature-flag capabilities and segmentation so that test-services in production only target specific users for testing purposes and remains invisible to everyone else.

As a short term fix a simple opt-in might suffice. However, we might risk ending up in the same territory if service owners decide to opt-in (enable) their service for testing-purposes and then abandon the service without cleaning up or opting out. In that case, a A/B with segmentation setup would be the far safer choice. Example product that contains such functionality (open link).

[Alxandr]

I would like to suggest we don't make this a bool Test. If it has to be a boolean, at least call it something like IsTest - though I would rather suggest a flags enum of ResourceFlags or somesuch.