Yes, @mcoh in template component, find the head section (mostly -> head.html) where you notice the following line of code or something similar  <title data-sly-test.pageTitle="${page.title}">${pageTitle}</title> replace it with  <sly data-sly-test.editOrDesign="${wcmmode.edit || wcmmode.design}"/> ...

@YuSheng  You can rely on AssetReferenceSearch to get the assets used in the page to publish them. Example snippet:  Node pageJcrContentNode = pageJcrContentResource.adaptTo(Node.class);Map<String,Asset> assetReferencesMap = new AssetReferenceSearch(pageJcrContentNode, "/content/dam", resourceResolv...

@KajalInamdarEy  Isn't the following line setting up the contentFragment field value in test?    PrivateAccessor.setField(underTest, "contentFragment", coreCf); I can run the test class you provided and noticed that the contentFragment value is set, but getting a different error though - java.lang.I...

@Veena_Karnik   Try the following two methods and see if they fix the issue:  Run complete deployment of both projects one after the other If the first doesn't work, try refreshing the bundle in System Console with id - Day Communique 5 WCM Core Implementation (com.day.cq.wcm.cq-wcm-core)

@dylanmccurry  Here are a few checks you can do to troubleshoot & fix the issue -  What is the target path specified within the embed configuration in pom.xml? Do you have a filter set in META-INF/vault/filter.xml for the same to install the package in AEM through deployment if the path is not cover...

@nikita24tailor Check if the property with selected value is persisted to JCR when you submitted the dialog in CRXDE -  http://localhost:4502/crx/de/index.jsp#/content/PAGE_PATH/jcr:content/COMPONENT_PATH 

@kritikagoyal Have you added the cq:dialog to your component with authoring fields?   You can refer to this document - https://experienceleague.adobe.com/docs/experience-manager-65/developing/components/developing-components.html?lang=en#creating-a-new-dialog 

@janhavi_singh Yes, you can load the response json using the context.load.json() and return that json using the Mockito stubbing. 

@bhavi50 , You've to write test cases for negative/exception cases to get coverage for the uncovered lines. If you notice, the lines that are not covered in code coverage are the cases where you encounter the exception or when the path doesn't start with "/content".  Add a new test case by creating ...

@S__k__Agarwal    You can use a Single Program with Multiple code repositories, where you will have a Single Stage and Production environment with a production pipeline and multiple dev environments with non-production pipelines.   You mentioned you have a common/shared repository and multiple brand...