Skip to content

New localtest architecture #150

@martinothamar

Description

@martinothamar

Description

Over time there has become significant drift between localtest components and the original services it is based on:

  • altinn-authentication
  • altinn-authorization
  • altinn-storage
  • ...

Team Apps/Studio is the primary owner of localtest since app developers DevEx falls within our domain/product. Still, to be able to offer a local development experience for this product we need a fully working (though limited) Altinn 3 replica running locally.

Currently all the other teams don't consider localtest a part of their "definition of done" when developing products that are also embedded in localtest.
We rely on Apps/Studio developers to replicate all work that is being done across teams in Altinn. This is not sustainable and also leads to faulty implementations due to lacking domain knowledge.

We should think of a way to govern and maintain localtest to ensure that it stays viable to develop apps locally for Altinn Studio.

In scope

No response

Out of scope

No response

Additional Information

No response

Tasks

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    status/draftStatus: When you create an issue before you have enough info to properly describe the issue.

    Type

    Projects

    Status

    No status

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions