Explore Connect Documentation
Snippets
01 Introduction
Why Contribute?
02 Types of Contributions
In/Out Puzzles Coding Games Contest Articles CodinGamer Tool
03 Technical Details
Writing the Statement Stub Generator Syntax Defining Test Cases
04 Contributing to CodinGame
Rules of Engagement Contribution Guidelines Moderation Rewards Licensing
05 Community
CodingHubs List of Community Contests List of Community Tools

This is a preview

This playground version isn't public and is work in progress.

Previous: Stub Generator Syntax Next: Rules of Engagement

A test case is composed of 2 tests:

  • a test for the IDE
  • a test for validating a solution, often called validator.

IDE tests are visible to the players whereas validators are hidden.

Guidelines

  • Test cases should cover all specifications

The more tests, the better.

  • Test cases must have explicit names

It helps players to understand the purpose of the test.

  • Each validator should check the same case as the corresponding test

They work by pairs.

  • Each validator must differ from the correspond test

It's only to ensure that the players don't harcode the solution.

  • The first test case must be a simple one

It's included in the statement.

Open Source Your Knowledge: become a Contributor and help others learn. Create New Content