Scenario
About 1 minutesLet's start with a scenarioFictional example; numbers are illustrative
An error occurred in production, and he wanted Dragon Warrior to help identify the cause.
He had the full code snippet and a log file containing customer addresses at hand.
Jiang Haoran, Full-Stack Test Engineer at Heyao Electronics, wanted it to help generate test scenarios and planned to paste the entire test specification.
Procedure
About 2 minutesProcedure: Three Questions, Red/Yellow/Green, Three Steps of Desensitization
Prompts and Examples
About 4 minutesPrompt 1: Provide only the phenomenon, no code
Suggested timeI am giving you only the phenomenon and the desensitized error message, not the code. Phenomenon: [One-sentence description] Original error message (addresses and accounts replaced with placeholders): [Paste] Please list: 1. Possible causes, sorted by likelihood, each in one sentence, marked 'To be verified'; 2. What I should check and how to check it, without providing definitive conclusions; 3. What information I did not provide, which prevents you from making a judgment. Rules: Do not fabricate function names, library names, or parameter names; write 'Uncertain' if unsure; do not determine the cause for me.
Prompt 2: Brainstorm test scenarios
Suggested timeBelow is a text description of a feature (replaced with placeholders, containing no internal details). Please list test scenarios in three categories: normal, boundary, and abnormal. For each scenario, write: preconditions, operations, and expected results. Finally, separately list 'Scenarios I may have missed.' For any expected result you are unsure of, write 'To be verified against the specification document'; do not fabricate. Feature description: [Paste]
Prompt 3: Acceptance review of its suggestions
Suggested timeYou previously suggested [a certain fix or function]. Please answer: 1. Did this function, library, or parameter appear in the information I provided? 2. Have you actually run it? 3. If not, directly write 'I have not run it,' and list the verification steps I must perform before going live.
Example: The same log differs before and after desensitizationFictional example; all materials are fictional
Red: Do not post
- A segment of source code for a company service
- Access keys in the configuration file
- The entire segment of error logs containing customer addresses
Yellow or Green: Can be posted after desensitization
- After replacing customer addresses with 'Customer A,' keep only the three lines showing the phenomenon and error message (Yellow)
- Public product introduction page text (Green, but still check company regulations first)
- General Login Page Testing Brainstorming (Green)
Common Deviations and Remedies
Too lazy, directly posting the entire code snippet
Remedy: Write down 'Three things not to post today' and stick it to the side of your screen.
Believing the function names it fabricated
Remedy: For every function, library, and parameter, verify them in the code or official documentation; if you can't find them, do not use them.
It says 'This fix works' or 'Tests passed'
Remedy: This is just a clue. It must go through review and testing. Anything without executed code or execution logs does not count.
Error report contains customer address
Remedy: Delete or replace with a code name first, then post.
Quiz and Takeaways
About 3 minutesThree quick questions to check yourself
Question 1: Can the fix it provided be deployed directly?
Question 2: What should you do if the error report contains a customer network address?
In this lesson, take away four key phrases.
- Before posting, ask three questions: Is it public? Can it reproduce the business scenario? Is it approved by the company?
- Do not post red-flagged materials: source code, keys, or customer logs.
- It only provides clues; review and testing are mandatory before launch.
- Test results without operational records do not count.
Next step: Write down your three items.
Write down the three items you are not posting today, and place them by your workstation.
- Write down your role’s 'three items not to post today.'
- Select one error message, perform a delete, replace, or shorten operation, then ask for its possible cause, and mark it as 'pending verification.'
Show the full transcript (video narration)
Boundaries of Code and Testing Assistance
This lesson covers the boundaries of code and testing assistance. It does not teach coding or replace introductory code review training; it only addresses boundaries: which materials can be used for assistance, which must not be shared, and how to verify the results afterward. Let's start with a scenario.
Let's start with a scenario
The scenario above is fictional, and the numbers are illustrative. Qiu Ziang, a backend developer at Qilan Intelligence, encountered a production error and wanted Dragon Warrior to help identify the cause. He had the full code and a log file containing customer addresses at hand. Jiang Haoran, a full-stack test engineer at Heyao Electronics, wanted it to help generate test scenarios and planned to paste the entire test specification. Neither of them should have done this. Once code and logs enter a public application, they cannot be retrieved.
Procedure: Three Questions, Red/Yellow/Green, Three Steps of Desensitization
The process has five steps. First, ask three questions: Is this content public? Can posting it allow reconstruction of our business and clients? Has the company approved this tool? If any answer is no, do not post it. Second, check against the Red/Yellow/Green list. Red materials are never posted; Yellow materials can be posted only after desensitization; Green materials, such as general algorithm ideas, still require checking company regulations. Third, desensitize in three steps: delete, replace, and shorten. Fourth, treat its suggestions only as leads; review and test them, and check for fabricated non-existent functions, libraries, or parameters. Fifth, add to the acceptance checklist: who reviewed it, what tests were run, and what were the results.
Prompt 1: Provide only the phenomenon, no code
The first prompt provides only the phenomenon, not the code. Paste the one-sentence phenomenon and the desensitized error message. Ask it to list possible causes, sorted by likelihood, each marked 'To be verified'; then tell me what to check and how; finally, state what information it did not see. The rule is: do not fabricate function names, library names, or parameter names, and do not determine the cause for me.
Prompt 2: Brainstorm test scenarios
The second prompt is for brainstorming test scenarios. The feature description must first be replaced with placeholders. Ask it to list scenarios in three categories: normal, boundary, and abnormal, clearly stating preconditions, operations, and expected results for each. For uncertain expected results, write 'To be verified against the specification document'; do not fabricate.
Prompt 3: Acceptance review of its suggestions
The third prompt is for acceptance review of its suggestions. Ask it: Did this function appear in the information I provided? Did it actually run it? If not, it must directly write 'I have not run it' and list the verification steps required before going live.
Example: The same log differs before and after desensitization
Look at an example: all materials are fictional. Source code for company services, access keys in configuration files, and full error logs containing customer addresses are red and must not be posted. After replacing the customer address with 'Customer A', keeping only the phenomenon and three lines of the error is yellow; this can be posted after desensitization. Public product introduction text and general login page testing brainstorming are green, but you must still check company regulations first. For the same error report, first delete, replace, or shorten it before deciding whether to post it.
Common Deviations and Remedies
There are four common deviations. First, being too lazy and directly posting the entire code snippet; the remedy is to write down 'Three things not to post today' first. Second, believing the function names it fabricated; the remedy is to verify every function, library, and parameter in the code or official documentation. Third, it says 'This fix works' or 'Tests passed'; the remedy is that this is just a clue, and since it hasn't executed the code or provided execution logs, it doesn't count. Fourth, the error report contains a customer address; the remedy is to delete or replace it with a code name first, then post.
Quiz Question 1
Let's do the quiz. Question 1: Can the fix it provided be deployed directly? A, Yes, its answer is very professional. B, No, it must go through review and testing. C, Yes, as long as it says 'Tests passed'. The answer is B. It only provides clues. Deployment requires review and testing; 'Tests passed' without execution logs does not count.
Quiz Question 2
Question 2: What should you do if the error report contains a customer network address? A, Post it as is to help it locate the issue. B, Delete or replace with a code name first, then post; keep only the phenomenon and necessary lines. C, Directly ask it to ignore the address and continue analysis. The answer is B. The address must be deleted or replaced with a code name first. Keep only the phenomenon and necessary lines, then post.
In this lesson, take away four key phrases.
Let’s review the four key phrases from this lesson. First, before posting, ask three questions: Is it public? Can it reproduce the business scenario? Is it approved by the company? Second, do not post red-flagged materials: source code, keys, or customer logs. Third, it only provides clues; review and testing are mandatory before launch. Fourth, test results without operational records do not count.
Next step: Write down your three items.
Next, write down your role’s 'three items not to post today' and place them by your workstation. Then, select one error message, perform a delete, replace, or shorten operation, and ask for its possible cause. Remember to mark all its responses as 'pending verification.' This video’s narration is AI-generated. Thank you for watching.