verify-with-oql

Verify with OQL Skill

This skill documents how to verify microflow side effects and data changes using OQL queries against a running Mendix app.

When to Use This Skill

Use this when:

• You've deployed changes and want to verify data was created/updated/deleted correctly
• You need to confirm a microflow produced the expected side effects
• You're combining Playwright UI tests with backend data verification
• You want a fast feedback loop: deploy, trigger, verify

The Pattern

The core verification workflow is:

1. Deploy — apply MDL changes and rebuild
2. Trigger — execute the action (via UI, microflow call, or API)
3. Verify — query the database with OQL to confirm the result

# 1. Deploy
mxcli exec changes.mdl -p app.mpr
mxcli docker build -p app.mpr --skip-check
mxcli docker reload -p app.mpr   # or: mxcli docker up -p app.mpr --fresh --wait

# 2. Trigger (example: call a microflow that creates test data)
# This could be via Playwright, a rest call, or manual interaction

# 3. Verify
mxcli oql -p app.mpr "select Name, Email from MyModule.Customer where Name = 'Jane Doe'"

OQL Verification Examples

Check data was created

# Verify a customer was created
mxcli oql -p app.mpr "select Name, Email from Sales.Customer where Name = 'Test Customer'"

# count records
mxcli oql -p app.mpr "select count(*) as Total from Sales.Order"

Check data was updated

# Verify status was changed
mxcli oql -p app.mpr "select OrderNumber, status from Sales.Order where OrderNumber = 'ORD-001'"

Check data was deleted

# Verify record no longer exists (should return empty)
mxcli oql -p app.mpr "select count(*) as Total from Sales.Customer where Name = 'Deleted Customer'"

Check associations

# Verify an association was set (join query)
mxcli oql -p app.mpr \
  "select o.OrderNumber, c.Name from Sales.Order o join o/Sales.Order_Customer/Sales.Customer c where o.OrderNumber = 'ORD-001'"