You coud deploy your latest version of the code in Staging and there run your Cypress tests, if they pass you could then deploy to production. You should create an AppBuilder project with multiple workspaces, Production and Staging by default. I am not familiar with Cypress, but from a quick read-over the docs, I would go with the following strategy. Most template on AIO comes with some basic testing: unit testing with mocks that can be run anywhere and end-to-end testing with the deployed app in the e2e folder. Using jest for testing is pretty effective. The way to provide the user context is the Unified Shell.ģ. Accessing directly your localhost app, you will be able to access only content that do not require an IMS access token, like if you use only public APIs or provide your own credentials for a 3rd party service.Ģ.

The Unified Shell is indeed connected to our Identity Manager (IMS) which will inject your access token to you application. You are correct, the localhost server is only here to provide the files for the Unified Shell (). How could we automate testing apps build for App builder? I just wonder how could we set up Cypress or any other framework along with App builder site.ġ. Is there a way to provide user context to the local env ?ģ. How should I work with this locally? Should I only use the app via url ?Ģ. When I open the app via domain I have the IMS profile available (I am logged in to the site) and the app works fine but when I access the app via localhost this is not available which means that I can not work on the app this way.ġ. When I run this app with aio app run it shows me two options to view my deployed application: via localhost and via This app is using IMS profile and allows to create user todo list. I am researching Adobe App Builder and I am working with a sample ToDo app tutorial:

Adobe app builder icon