create-texttests

name	create-texttests
description	Design integration_tests for new functionality using TextTest.

• When you are using this skill, stack replies with this emoji: 📋
• If you expect the tests to all pass, run them to make sure.
• If you expect the tests to fail, ask the user to run them and manually approve the new results. These tests act as the executable specification of the requirements, and the user wants to retain control of what is in them.
• Each test case is in a folder with a name referring to the test scenario, and listed in the testsuite.rpg file in the folder above. A full test description can be included as a comment in the testsuite file, if needed.
• Each test case may define input to the test rig. This could be command line arguments options.rpg or a file for it to pass to standard input stdin.rpg. Place the input file(s) in the test folder.
• When a test fails the runner will pause execution and wait for interactive approval, unless you pass the argument -o to overwrite or -n to update the approved files. DO NOT do this unless the user explicitly asks you to. Otherwise, abort and ask the user to manually run the tests and approve the changes.
• Full TextTest documentation is available at TextTest on Sourceforge