Why “It Works in Dev” is a Failure: Automated Verification in OutSystems ODC

In traditional development, “It works on my machine” was the ultimate developer cliché. In the era of OutSystems Developer Cloud (ODC), that cliché has evolved into “It works in Dev.” But in a high-speed, cloud-native environment, “working in Dev” means very little if you can’t prove why it works and ensure it stays working after the next deployment.

The Shift to Serverless Testing

ODC moves us away from the traditional monolithic server approach and toward a more modular, serverless architecture. This brings incredible scalability, but it also introduces complexity. When your logic is distributed, your testing must be, too.

1. The Strategy: Isolation vs. Integration

In ODC, unit testing should focus on the Business Logic layer.

• Small Surface Area: Keep your serverless functions focused. If a function does one thing, it only needs one set of tests.
• Decoupling: Ensure your logic is decoupled from side effects. This makes it easier to run tests without spinning up the entire ODC ecosystem.

2. The Power of Mocks

You can’t always rely on a live external API being available during a test run. Mocks allow you to:

• Simulate “Timeout” or “500 Internal Server Error” responses to see how your ODC app reacts.
• Speed up test execution by bypassing network latency.
• Create predictable, repeatable test environments.

3. Automated Verification (11QA)

The goal of 11QA is to move from “testing” (a manual effort) to “verification” (an automated process). Every time a developer pushes a change in ODC, a suite of automated tests should act as the gatekeeper.

The Rule of Thumb: If a human has to click a button to verify a calculation, you haven’t finished the feature.

Recommended Tools

To achieve true automated verification in ODC, consider:

• ODC Test Framework: Leveraging built-in capabilities to structure your test suites.
• BDD Framework: Writing tests in “Given-When-Then” format to ensure business requirements match the technical execution.
• Custom Mocking Actions: Creating “Mock” versions of your service actions that can be toggled via Site Properties or Settings for test execution.

Final Thoughts

Transitioning to ODC is an opportunity to reset your technical debt. Don’t bring old manual testing habits into a modern cloud-native platform. Embrace Automated Verification and turn “It works in Dev” from a hopeful prayer into a verified fact.