Testing: SysTest & Task Recorder

SysTest Framework

[SysTestTargetAttribute(classStr(CustomerValidator), MethodStr(CustomerValidator, validate))]
public class CustomerValidatorTest extends SysTestCase
{
    public void setUp() { super(); }
    public void tearDown() { super(); }

    [SysTestMethodAttribute]
    public void testValidExistingCustomer()
    {
        CustomerValidator v = CustomerValidator::construct("1001");
        this.assertTrue(v.validate(), "Should pass for existing customer");
    }

    [SysTestMethodAttribute]
    public void testInvalidCustomer()
    {
        CustomerValidator v = CustomerValidator::construct("FAKE999");
        this.assertFalse(v.validate(), "Should fail for non-existent");
    }
}

Assert methods

Method	Purpose
assertTrue	Value should be true
assertFalse	Value should be false
assertEquals	Two values equal
assertNotNull	Not null/empty

Transaction modes

Default: test runs in a transaction that auto-rolls back — test data disappears. Use SysTestTransaction::NotInTransaction for integration tests that need persistent data.

🎓 Sophie: “Carl made me write tests first. When my CoC broke form validation, the unit test caught it instantly.”

💡 Exam tip: SysTestTransaction

Default mode rolls back. NotInTransaction persists data. The exam asks which mode for which scenario.

Running in Test Explorer

1. Build project → tests auto-discovered
2. Test menu → Test Explorer
3. Run All or select specific tests
4. Green = pass, red = fail with details

🏗️ Vik: “We run SysTest in our Azure DevOps pipeline. Every check-in triggers build + test. Failed tests block the check-in.”

Task Recorder

Records user actions to generate documentation and test artifacts.

Output	Purpose
Step-by-step Word doc	Training documentation
BPM recording	Upload to LCS Business Process Modeler
XML recording	RSAT automation
Task guide	In-app help

RSAT (Regression Suite Automation Tool)

Converts Task Recorder XML into automated end-to-end tests. Business analysts record, RSAT replays against test environments.

SysTest vs Task Recorder/RSAT

	SysTest	Task Recorder/RSAT
Level	Unit — methods and classes	End-to-end — business processes
Author	Developers in X++	Business analysts in UI
Speed	Seconds	Minutes (simulates clicks)
Data cleanup	Auto-rollback	Requires test data management
Best for	Code validation	Business process regression

Question

SysTest base class?

Click or press Enter to reveal answer

Answer

SysTestCase — provides assert methods, setUp/tearDown, Test Explorer integration.

Click to flip back

Question

[SysTestMethodAttribute] does what?

Click or press Enter to reveal answer

Answer

Marks a method as a test case discoverable by Test Explorer.

Click to flip back

Question

Default SysTest transaction behaviour?

Click or press Enter to reveal answer

Answer

Auto-rollback. Test data cleaned up automatically after each test.

Click to flip back

Question

RSAT purpose?

Click or press Enter to reveal answer

Answer

Converts Task Recorder XML into automated end-to-end tests replayed against test environments.

Click to flip back

Knowledge Check

Vik needs to test his CoC extension on validateField. Approach?

ASysTest unit test — create data, call method, assert resultBTask Recorder recordingCManual UI testingDPost-event handler logging

Check Answer

Knowledge Check

Tests should clean up automatically. Which mode?

ADefault — auto-rollback transactionBNotInTransactionCCommitAndRollbackDManual tearDown cleanup

Check Answer

Knowledge Check

Business team wants regression tests after upgrade. Not developers. Tool?

ATask Recorder + RSATBSysTest in Visual StudioCTrace ParserDBPM only

Check Answer

---

Next up: Domain 5 — Reporting in F&O — SSRS, Power BI, Excel, and Electronic Reporting.