Test modules by using page mocks
This article describes how to test modules by using page mocks.
Some modules are built to interact with other modules. You can use page mocks to test those modules together in a local development environment.
Page mock files are stored under the /src/pageMocks directory. They can be loaded by using the URL https://localhost:4000/page?mock=PAGE_MOCK, where PAGE_MOCK is the file name of the mock file, but without the .json file name extension.
Create a new page mock
To create a new page mock, create a blank .json file under the /src/pageMocks directory, such as /src/pageMocks/campaign-page.json.
Example
The following example shows a page mock that adds two instances of the same module to a page but uses different mock data for each instance.
{
"exception": null,
"pageRoot": {
"id": "core-root_0",
"typeName": "core-root",
"modules": {
"body": [
{
"id": "default-page_0",
"typeName": "default-page",
"modules": {
"primary": [
{
"id": "ProductFeature__0",
"typeName": "product-feature",
"config": {
"imageAlignment": "left",
"buttonText": "Buy Now",
"productIds": "68719490621"
}
},
{
"id": "ProductFeature__1",
"typeName": "product-feature",
"config": {
"imageAlignment": "right",
"productIds": "68719498121",
"buttonText": "Buy Now"
}
}
]
}
}
]
}
},
"renderingContext": {
"gridSettings": {
"xs": {
"w": 767
},
"sm": {
"w": 991
},
"md": {
"w": 1199
},
"lg": {
"w": 1599
},
"xl": {
"w": 1600
}
},
"staticContext": {
"staticCdnUrl": "/_scnr/"
},
"locale": "en-us"
},
"statusCode": 200
}
Every page defines a root (core-root in the example above) that controls the page HTML structure with slots for "HTML Head", "Body Begin", "Body" and "Body End". The body then must have a page container module. In this example, the default-page page container is used.
The modules section lists the modules that are included inside the page arranged by named slots. The default-page page container has a slot that is named primary. This container is responsible for laying out the modules that are included inside it. In this example, the productFeature module is rendered two times in a row with the mock data defined in the config section for each.
The preceding example can be accessed by using the following URL: https://localhost:4000/page?mock=campaign-page.
Rendering context mocks
The renderingContext node provides additional mock data that modules can access via the this.props.context.request object. This mock data can include the bootstrap grid breakpoints, the locale, and the user context. For more information, see Request properties object.
Simulate the signed-in state
Some modules might have logic that must check the signed-in state of the user before they take the appropriate action. Typically, a module gets the state from the this.props.context.request.user object. Because business-to-consumer (B2C) sign-in isn't supported in a development environment, the user object can be mocked by using the user node, as shown in the following example.
{
"exception": null,
"pageRoot": {
"id": "core-root_0",
"typeName": "core-root",
"modules": {
"body": [
{
"id": "default-page_0",
"typeName": "default-page",
"modules": {
"primary": [
{
"id": "ProductFeature__0",
"typeName": "product-feature",
"config": {
"imageAlignment": "left",
"buttonText": "Buy Now",
"productIds": "68719490621"
}
}
]
}
}
]
}
},
"renderingContext": {
"gridSettings": {
"xs": {
"w": 767
},
"sm": {
"w": 991
},
"md": {
"w": 1199
},
"lg": {
"w": 1599
},
"xl": {
"w": 1600
}
},
"staticContext": {
"staticCdnUrl": "/_scnr/"
},
"user": {
"token": "<TOKEN>",
"isAuthenticated": true,
"signInUrl": "https://dev.fabrikam.com/fedev/_msdyn365/signin",
"signOutUrl": "https://dev.fabrikam.com/fedev/_msdyn365/signout",
"signUpUrl": "https://dev.fabrikam.com/fedev/_msdyn365/signup",
"editProfileUrl": "https://dev.fabrikam.com/fedev/_msdyn365/editprofile",
"signinName": "<User Name>",
"firstName": "<User First Name>",
"lastName": "<User Last Name>",
"tenantId": "",
"customerAccountNumber": "<User Account Number(HQ)>",
"name": "<User Name>",
"emailAddress": "<User Email Address>"
},
"locale": "en-us"
},
"statusCode": 200
}
Use the following procedure if you must simulate real data or the token that is returned from Commerce Server.
The user information is available in the ___initialData___.requestContext.user global JavaScript variable. While the web browser's developer (F12) tools are open and a user is signed in, you can view the object by opening a console window and entering ___initialData___.requestContext.user.
To simulate real data or the token that is returned from Commerce Server, follow these steps.
Load the e-commerce site page that you're working on, and sign in or create a new account.
Open your web browser's debugging tools. For example, if you're using Google Chrome or Microsoft Edge, you can open the developer tools by selecting the F12 key.
Open a console window, and enter ___initialData___.requestContext.user to view the object. (User information is available in the ___initialData___.requestContext.user global JavaScript variable.)
Add the module that must be tested to a page mock.
In the renderingContext section of the page mock, add the following userContext section.
"userContext": { "token": "<TOKEN>", "isAuthenticated": true, "signInUrl": "https://dev.fabrikam.com/fedev/_msdyn365/signin", "signOutUrl": "https://dev.fabrikam.com/fedev/_msdyn365/signout", "signUpUrl": "https://dev.fabrikam.com/fedev/_msdyn365/signup", "editProfileUrl": "https://dev.fabrikam.com/fedev/_msdyn365/editprofile", "signinName": "<User Name>", "firstName": "<User First Name>", "lastName": "<User Last Name>", "tenantId": "", "customerAccountNumber": "<User Account Number(HQ)>", "name": "<User Name>", "emailAddress": "<User Email Address>" },Update the user information (token, signinName, firstName, lastName, customerAccountNumber, name, and emailAddress) that you obtained from the web browser's debugging tools.
The user information can now be obtained from within the this.props.context.request.user object in the React component.
Create a dynamic page mock from a production e-Commerce page
You can create dynamic page mocks that mimic live e-Commerce site pages and can be used locally to test module interaction. For example, these page mocks can mock the signed-in state and other page contextual properties as required. Therefore, they can be helpful when you locally test pages such as account pages and wishlist pages, or interactions such as order checkout flow.
Save a live e-Commerce page's raw JSON structure
The raw JavaScript Object Notation (JSON) structure of any live e-Commerce page can be captured and saved so that it can be used as a page mock. Open the e-Commerce site page that you want to capture, and sign in if the signed-in state is desired. Next, append the query string parameter ?item=nodeserviceproxy:true to the page URL, and then reload the page to obtain the JSON of the raw page context.
Note
For this operation to work, you must have secure Microsoft Entra access to your production site, and you might be prompted to sign in if you aren't already signed. Use the same Microsoft Entra account that you use to sign in to Commerce site builder.
Next, in your development environment, create a new page mock JSON file under the src/pageMocks directory. Paste in the JSON file that you obtained from the capture and save operation.
The structure of the JSON file should have sections that resemble the sections in the following example. These sections should include the pageRoot section that defines the set of modules for the page and the renderingContext section that includes the user context for signed-in user information.
{
"exception": null,
"pageRoot": {
"id": "core-root_0",
"typeName": "core-root",
"modules": {
}
},
"renderingContext": {
…
"user": {
...
}
},
"statusCode": 200
…
}
To test the page mock locally, start your Node server by using yarn start command. Access the page mock by using the URL format https://localhost:4000/page?mock=PAGE_MOCK, where PAGE_MOCK is the file name of the mock file without the .json file name extension.
You can now modify the page mock as desired.
Additional resources
Add module configuration fields
Test modules by using module mocks
Create a layout container module
Feedback
Coming soon: Throughout 2024 we will be phasing out GitHub Issues as the feedback mechanism for content and replacing it with a new feedback system. For more information see: https://aka.ms/ContentUserFeedback.
Submit and view feedback for