Coding labs is a powerful feature of Fermion. Using coding labs in your platform, you can increase user retention, provide hands-on experience to them, and make them learn-by-doing. Let’s take a look at how you can setup a HTML/CSS/JS interactive coding lab in this guide.

​
Step 1 - Creating the Lab

  • Add a new item lab in your course curriculum page
  • A new lab item gets added. Edit the lab using the controls:
  • A lab item in a course can be attached to an existing lab you created in the past. If not, you can create a new lab with this Edit interface:
  • You should now be able to write a quick lab name and press on “Create Lab” button. Once you do, press on Attach to course item button. Once that is done, click the three dots again and click on “Edit” to edit the lab.

​
Step 2 - Lab Instructions

Once you click on Edit button a new page will open. On this page you need to setup instructions for lab. These instructions would be visible to the user when they’re attempting the lab. Therefore, include all the helper material, lab setup instructions here.

​
Step 3 - Lab Defaults

Lab defaults section include how your lab environment boots. It is one of the most important parts because a wrong default environment might confuse your students. Therefore it is important to set it up properly.
We recommend forking this repository: HTML playground starter.
The repository also includes a .cdmrc file, a critical configuration file for Fermion labs. Familiarize yourself with the .cdmrc guide to understand how it works before proceeding.

​
Step 4 - Evaluation Script

Evaluation script is actually what runs when the user on the playground clicks on “Run Tests” button. Since we have already written a pure evaluation script that runs and finally writes the JSON result to the UNIT_TEST_OUTPUT_FILE environment, all we have to do is trigger that script via Node.js. The full path of the script is made available at run-time with another environment variable called TEST_FILE_NAME. Therefore, all we have to do is write the following in the evaluation script area: 
#!/bin/bash
set -e 1

# create a folder for test
mkdir -p /home/damner/code/.labtests

# move to the folder
cd /home/damner/code/.labtests

# move test file here
mv $TEST_FILE_NAME nodecheck.spec.js

# mark this as module
cat > package.json << EOF
{
    "type": "module"
}
EOF

# write playwright config file
cat > playwright.config.ts << EOF
import { defineConfig, devices } from '@playwright/test'
import puppeteer from 'puppeteer'

export default defineConfig({
	timeout: 10_000,
	maxFailures: 0,
	testDir: '.',
	fullyParallel: false,
	forbidOnly: true,
	retries: 0,
	workers: 1,

	// Reporter to use
	reporter: [['list'], ['json', { outputFile: './report.json' }]],

	use: {
		baseURL: 'http://localhost:1337/',
		trace: 'off',
		launchOptions: {
			headless: true,
			executablePath: puppeteer.executablePath(),
			chromiumSandbox: false
		}
	},

	projects: [
		{
			name: 'chromium',
			use: { ...devices['Desktop Chrome'] }
		}
	]
})
EOF

# `puppeteer` is installed via NPM in playgrounds. Use preinstalled dependency
npm link puppeteer
bun install @playwright/test@1.40.1 playwright@1.40.1

bunx playwright test || true

# process results file
cat > process-results.js << EOF
import fs from 'fs'
const payload = JSON.parse(fs.readFileSync('./report.json', 'utf-8'))
const answers = payload.suites[0].suites[0].specs.map(spec => spec.ok === true && spec.tests.every(t => t.status === 'expected'))
fs.writeFileSync(process.env.UNIT_TEST_OUTPUT_FILE, JSON.stringify(answers))
EOF

node process-results.js
This will make sure we run the full Node.js script and write the results properly for the playground IDE to read. It would look like the following: Note: You can setup a full testing environment in this block of evaluation script (installing more packages, etc. if you want). However, your test file will be timed out after 60 seconds. Therefore, make sure, all of your testing can happen within 60 seconds.

​
Step 5 - Test file

In the same Evaluation tab, you’ll see another section called “Custom test file”. You can use this test file to add custom code for testing user work. When you click on it, a new window will open. This is a test file area. You can write anything here. Whatever script you write here, can be executed from the Test command to run section inside the evaluation tab we were in earlier. The point of having a file like this to provide you with a place where you can write your evaluation script. For HTML/CSS labs, you can use the default test file for playwright: 
import { expect, test } from '@playwright/test'

test.describe.serial('Test', () => {
	test.beforeEach(async ({ page }, testInfo) => {
		console.log(`Running ${testInfo.title}`)
		await page.goto('/')
	})

	test('Stylesheet is linked', async ({ page }) => {
		const linkElement = page.locator('link[rel="stylesheet"]')
		expect(linkElement).toBeDefined()
		expect(await linkElement.getAttribute('href')).toEqual('style.css')
	})
})
This completes your evaluation script for the lab. Your lab is now almost ready for users.

​
Step 6 - Add challenges

Finally, in the UI below, add friendly name of challenges that must be visible to the user. Note that the order of challenges is important here and must match the boolean array you write using the bash script + test file above.