https://divekit.org/docs/archive/divekit-v2/Recent content in Divekit v2 on DivekitHugoenhttps://divekit.org/docs/archive/divekit-v2/go-testing-guide-legacy/Mon, 01 Jan 0001 00:00:00 +0000https://divekit.org/docs/archive/divekit-v2/go-testing-guide-legacy/<div class="pageinfo pageinfo-primary"> <p>Legacy material: this document is preserved for historical context and is not the current testing standard for Divekit CLI.</p> </div> <h3 id="what-should-be-tested-in-this-project">What should be tested in this project?</h3> <p>Given that this CLI is the entry point for the user to interact with Divekit, it is essential to test all commands. Currently, there is only one command <code>patch</code>, but all commands should be tested with the following aspects in mind:</p> <ul> <li><em><strong>Command Syntax</strong></em>: Verify that the command syntax is correct</li> <li><em><strong>Command Execution</strong></em>: Ensure that executing the command produces the expected behavior or output</li> <li><em><strong>Options and Arguments</strong></em>: Test each option and argument individually to ensure they are processed correctly and test various combinations of options and arguments</li> <li><em><strong>Error Handling</strong></em>: Test how the command handles incorrect syntax, invalid options, or missing arguments</li> </ul> <p>Additionally, testing the utility functions is necessary, as they are used throughout the entire project. For that the following aspects should be considered:</p>