Archive for February 2020

Utilize Playwright together with Jest to cross-browser E2E test your solutions

On my journey to select the best tool for our end-to-end tests for our teams, I tested out the recently announced Playwright tool from Microsoft. This tool is the new version of Puppeteer (as the core team members moved to Microsoft). Info: The benefits of E2E tests are that it validates if your features work (or keep working when implementing changes), and also provides a more code-driven approach of documenting the features and user flows.

Read more

Quick tip: How to use dynamic variable groups in Azure DevOps YAML pipelines

The preferred way to implement pipelines these days in Azure DevOps is via YAML. Which makes the pipeline part of your code and is automatically version controlled. When you were used to the classic way of creating release pipelines, you might have used environment scoped variables. These scoped variables were great to specify to which environments you wanted to provision/install/deploy/… your solutions.

Read more

Best practice: specify the Local SharePoint results source ID to gain search control

When creating solutions based on SharePoint search, you best always define the source ID of the Local SharePoint results source with each call. By providing that source ID with each request, you make sure that the results you expect for your solutions are always the same. Which ID? The Local SharePoint results source ID you are looking for is: 8413cd39-2156-4e00-b54d-11efd9abdb89.

Read more
Back to top