AEM Bite: Testing Users and Groups with Chrome Profiles | AEM Community Blog Seeding

[#1]

AEM Bite: Testing Users and Groups with Chrome Profiles by Achim Koch

Abstract

Adobe Experience Manager (AEM) allows fine-grained control of user privileges. For developers and other technical team members who need to test a variety of user roles or user groups for the correct system access, Chrome browser profiles can save us time and effort.

Adobe Experience Manager (AEM) allows fine-grained control of user privileges.

This is not just required to control access to the content. Privileges are also leveraged to determine what UI features are made available for the current user — for example, which buttons users see and what workflows they can execute.

The downside is that this makes the system more complex. Two users with different privileges can have… a quite different user experience.

Privileges are also applied to internal resources. For example, when a certain function needs to access a configuration resource and the logged-in user does not have access to that resource, the function fails — often with nondescriptive error messages.

These are the types of errors that often occur late in the development sprint. The typical developer might focus more on developing the business requirements — working as “admin” on their local machines. So, the feature works for them — and fails in test with users that have more restricted privileges.

Don’t use the anonymous mode or impersonate
Ok, so we have realized that the feature is working for the admin but not for user U.

In that case, you log out from your admin account, log in as user U and test. Log in again as admin, make changes and so forth. Quite a pain in the back. I bet we’ve all been there at some point in time.

So, you might want to use an anonymous window to have an admin session and a user session open in parallel. Better. But what if you not only have one user to test — but dozens?

Chrome Profiles
Use Chrome Profiles instead. A Chrome Profile behaves like a completely separate browser, with its own history, bookmarks, and cookies. You can log in with as many users in parallel as required.

Most importantly, each profile can be displayed with a distinct color, and each profile has its own password safe.

Read Full Blog

AEM Bite: Testing Users and Groups with Chrome Profiles

Q&A

Please use this thread to ask the related questions.