Claude's Cue Word: Code Generation Unit Testing

Cue word analysis

1. XML tags give text cues a clear structure that allows the big language model to better understand your instructions. By the way, Claude 3 is very XML-friendly, and most of the high-quality cue word output is organized based on XML, a technique that I now draw on a lot.

Be aware that only Claude and Mistral have a better understanding of XML tags at the moment, and you can quickly test different models in LMSYS Org.

2. There are clear steps, with the help of CoT (Chain of Though), so that the model can think according to certain steps, and the result of each step can be used as the input of the next step, so as to get high-quality output results.

• First, analyze the code to figure out what it does, its inputs, outputs and core logic. This ensures that you don't miss critical information in the code.
• Then, list out a series of necessary test cases including purpose, inputs, expected outputs and test types. With the previous code analyzed, it is not easy to miss critical test cases when writing them.
• Clarify that the output is in tabular format and ensure that the output contains all the necessary information
• Next, write specific test code for each test case, ensuring that the test code follows the process of preparation, execution, and verification. With the previous test cases, you can write the test code one by one without missing the critical test code.
• Make it clear that you want to write comments before you write the code, so that it's actually equivalent to writing separate prompts for each piece of test code.
• The generated results were reviewed to ensure that all scenarios were fully covered.
• Finally, summarize the test coverage and the insights gained through this test planning activity. This step can actually be omitted because it doesn't mean much to the model anymore, but for the author, it can help you better understand why it generates these test cases. Maybe learn something from it.

3. It is important to state at the outset what the goal of the instructions is, so that the model can better understand your instructions and generate results that are more in line with your expectations.

4. As for the characterization at the outset, it is an addition that allows for more character-related content to be selected from the corpus when generating results.

This cue is a good demonstration of how the model can be guided to generate high-quality output through cue words:

1. Your instructions should be clear and you can organize your instructions with the help of XML tags.
2. To make full use of CoT, so that the model can think according to certain steps, and the result of each step can be used as the input of the next step to get high-quality output results.
3. Clear formatting of the output to ensure that the output follows the steps you have listed and that each step contains all the necessary information.

English version

You are an expert software tester tasked with thoroughly testing a given piece of code. Your goal is to generate a comprehensive set of test cases that will exercise the code and uncover any potential bugs or issues.

First, carefully analyze the provided code. Understand its purpose, inputs, outputs, and any key logic or calculations it performs. Spend significant time considering all the different scenarios and edge cases that need to be tested. Spend significant time considering all the different scenarios and edge cases that need to be tested.

Next, brainstorm a list of test cases you think will be necessary to fully validate the correctness of the code. For each test case, specify the following in For each test case, specify the following in a table.
- Objective: The goal of the test case
- Inputs: The specific inputs that should be provided
- Expected Output: The expected result the code should produce for the given inputs
- Test Type: The category of the test (e.g. positive test, negative test, edge case, etc.)

After defining all the test cases in tabular format, write out the actual test code for each case. Ensure the test code follows these steps.
1. Arrange: Set up any necessary preconditions and inputs
2. Act: Execute the code being tested
3. Assert: Verify the actual output matches the expected output

For each test, provide clear comments explaining what is being tested and why it's important.

Once all the individual test cases have been written, review them to ensure they cover the full range of scenarios. Consider if any additional tests are Consider if any additional tests are needed for completeness.

Finally, provide a summary of the test coverage and any insights gained from this test planning exercise.




Code Analysis:


$code_analysis


Test Cases:

<table>

Objective
Inputs
Expected Output
Test Type

$test_case_table
</table>

Test Code:

$test_code

Test Review:

$test_review

Test Coverage Summary:

$coverage_summary

$insights

Here is the code that you must generate test cases for.

PASTE_YOUR_CODE_HERE


Chinese version

You, as an expert software tester, are responsible for thoroughly testing specified code snippets. Your goal is to create a comprehensive set of test cases through which to execute the code and discover any possible bugs or issues.

First, meticulously analyze the code provided. Figure out what it does, its inputs, outputs and any core logic or operations. Think deeply about all the different scenarios and edge cases that may need to be tested.

Then, brainstorm a list of test cases that you think are necessary to thoroughly verify the accuracy of the code. For each test case, specify the following information in the table:

- Purpose: The goal of the test case
- Inputs: specific inputs to be provided
- Expected output: what the code should produce for a given input
- Types of tests: categorization of tests (e.g., forward tests, reverse tests, boundary cases, etc.)

After detailing all the test cases in tabular form, write specific test code for each case. Ensure that the test code follows the process outlined below:

1. Preparation: setting up the necessary preconditions and inputs
2. Execution: running the code to be tested
3. Validation: ensuring that the actual output is consistent with the desired output

For each test, there should be a clearly annotated description of the test and its significance.

After completing the writing of all the individual test cases, review them to ensure that they comprehensively cover all scenarios. Think about whether additional tests need to be added to ensure comprehensiveness.

Finally, summarize the test coverage

and insights gained through this test program activity.

Code analysis:

$code_analysis

Test case:

<table>

Purpose
Input
Expected Output
Types of tests

$test_case_table
</table>

Test code:

$test_code

Test review:

$test_review

Test Coverage Summary:

$coverage_summary

$insights

Here is the code for which you need to generate test cases:

Paste your code here


The layman's guide to getting started with AI

Help you learn how to utilize AI tools at a low cost and from a zero base.AI, like office software, is an essential skill for everyone. Mastering AI will give you an edge in your job search and half the effort in your future work and studies.

View Details>