📚 Year 7 WJEC Computer Science: Practical Assessment Key Points | WJEC 七年级计算机：实验/实践考核要点
Practical assessments in Year 7 WJEC Computer Science are designed to test your ability to apply computational thinking, programming skills and safe working practices in a real or simulated environment. This article breaks down the key points you need to focus on, from setting up your workspace to debugging code and reflecting on your work. By understanding these areas, you can approach any practical task with confidence and demonstrate your skills clearly.
WJEC 七年级计算机的实验/实践考核旨在检验你在真实或模拟环境中应用计算思维、编程技能和安全操作规范的能力。本文详细分解了需要关注的关键要点，从准备工作环境到调试代码，再到反思你的作品。理解这些领域后，你将能自信地应对任何实践任务，并清晰地展示自己的技能。
1. Understanding Assessment Objectives and Marking Criteria | 了解考核目标与评分标准
Before you even touch the keyboard, read the task brief carefully. WJEC practical assessments typically evaluate three strands: planning and design, implementation, and testing/evaluation. Know exactly what the examiner expects for each strand, including the marks allocated for a logical flowchart, a working program, and evidence of testing.
在碰键盘之前，请仔细阅读任务说明。WJEC 实践考核通常评估三个维度：规划与设计、实现以及测试与评估。要确切了解考官对每个维度的要求，包括逻辑流程图、可运行的程序和测试证据能获得多少分数。
Your teacher may provide a mark scheme or a checklist. Always refer to it while you work. For example, if the task asks for a program that uses a loop to repeat a question until a correct answer is given, you must show that your loop condition works and that you have tested it with both correct and incorrect inputs.
你的老师可能会提供评分方案或检查清单。在工作过程中要不时参考。例如，如果任务要求编写一个程序，使用循环重复提问直到给出正确答案，你就必须证明循环条件有效，并且已经用正确和错误的输入进行了测试。
Common marking points include: correct use of sequence, selection and iteration; naming variables meaningfully; including comments to explain code; showing a test plan; and saving work with sensible file names. Make a small tick list on a sticky note if it helps you remember.
常见的得分点包括：正确使用顺序、选择和迭代结构；变量命名有意义；添加注释解释代码；展示测试计划；以及用合理的文件名保存作品。如果有助于记忆，可以在便利贴上列出一个小清单。
2. Safe and Responsible Use of Equipment | 安全且负责地使用设备
All practical work starts with safety. Ensure your workstation is tidy, cables are not trailing, and drinks are kept well away from computers. Log in using your own school account and never share your password. This protects your files and personal data, which is a key part of digital citizenship assessed indirectly in practical tasks.
所有实践工作都从安全开始。确保你的工作区域整洁，线缆没有散落，饮料远离计算机。使用自己的学校账户登录，绝不要共享密码。这保护了你的文件和个人数据，也是实践任务中间接评估的数字公民素养的重要组成部分。
When using the internet for research, only visit approved websites and do not download any files without permission. If you are using physical computing devices like a micro:bit or a Raspberry Pi, handle them gently and follow the specific instructions given by your teacher – for instance, never connect components while the device is powered on.
在网上进行研究时，只访问获批的网站，未经许可不要下载任何文件。如果你使用 micro:bit 或树莓派等实体计算设备，要轻拿轻放，并遵循老师给出的具体说明——例如，绝不要在设备通电时连接元器件。
Report any technical issue immediately. A frozen screen or a broken mouse can waste valuable time. The lab technician or teacher will appreciate an early warning rather than a last-minute panic.
任何技术问题都要立即报告。死机的屏幕或坏掉的鼠标会浪费宝贵的时间。实验室管理员或老师希望尽早收到提醒，而不是最后一刻的慌张。
3. File Management and Folder Structure | 文件管理与文件夹结构
Create a dedicated folder for your Computer Science work with a clear name, such as 'Y7_CS_Practical_Assessment'. Inside it, use subfolders like 'Code', 'Evidence' and 'Planning' acy and makes it easy to locate files when submitting your work or reflecting on it later.
为你的计算机科学作业创建一个专用文件夹，名称要清晰，如 'Y7_CS_Practical_Assessment'。在其内部使用子文件夹，如 'Code'、'Evidence' 和 'Planning'。这种组织方式展现出良好的数字素养，并且让你在提交作业或事后反思时能轻松找到文件。
Always name files with a logical convention. For a Scratch project, call it 'task1_quiz.sb3' rather than 'my project final final.sb3'. If you are writing Python code, save each version as you progress (e.g., 'quiz_v1.py', 'quiz_v2.py'). This way, if something breaks, you can always go back to a working version.
始终按照合理的命名规范给文件取名。对于 Scratch 项目，叫它 'task1_quiz.sb3' 而不是 'my project final final.sb3'。如果你在编写 Python 代码，每推进一个版本就保存一次（例如 'quiz_v1.py'、'quiz_v2.py'）。这样，如果程序出错，你总能退回到一个可运行的版本。
Check where your files are being saved. Often, students lose work because they save to a temporary folder or the desktop, and the computer is wiped after log-off. Always save inside your network home drive or a cloud-synced folder like OneDrive if your school uses it.
要留意文件的保存位置。学生经常因为把文件存到了临时文件夹或桌面，而注销后电脑被清空，导致丢失作品。请始终保存在你的网络主盘或学校使用的云同步文件夹（如 OneDrive）中。
4. Planning with Flowcharts and Pseudocode | 使用流程图和伪代码做规划
Never start coding immediately. Spend at least ten minutes planning your solution. The WJEC practical assessment expects you to show the design stage. Use a flowchart to map out the steps, decisions and loops. Standard symbols include: an oval for Start/End, a parallelogram for Input/Output, a rectangle for a process, and a diamond for a decision.
绝不要立刻就开始编码。至少花十分钟规划你的解决方案。WJEC 实践考核希望看到你的设计阶段。使用流程图来梳理步骤、决策和循环。标准符号包括：椭圆代表开始/结束，平行四边形代表输入/输出，矩形代表处理，菱形代表决策。
If drawing by hand is allowed, use a pencil, ruler and neat handwriting. Digital tools like draw.io or even PowerPoint shapes are also acceptable. Beside your flowchart, write short pseudocode – plain English instructions that resemble code. For example: INPUT score, IF score ≥ 50 THEN OUTPUT "Pass" ELSE OUTPUT "Fail".
如果允许手绘，请使用铅笔、直尺并书写工整。draw.io 甚至 PowerPoint 形状这样的数字工具也可以接受。在流程图旁边，写简短的伪代码——用类似代码的简单英语指令。例如：输入分数，如果分数 ≥ 50 则输出“通过”，否则输出“未通过”。
Planning helps you spot logical errors before they become bugs. Many marks are awarded simply for having a sensible plan, even if your final program isn't perfect. So always present your flowchart or pseudocode clearly as part of your evidence.
规划能帮助你在错误变成 bug 之前发现它们。即使最终程序并不完美，只要有合理的方案，就能获得很多分数。因此，务必清晰地展示你的流程图或伪代码，作为证据的一部分。
5. Setting Up the Programming Environment | 搭建编程环境
Whether you code in Scratch, Python (using an IDE like IDLE, Mu or Thonny) or a block-based environment, ensure you know how to open the correct software and set up the screen for efficient working. For Python, check that the shell and editor are both visible so you can test small snippets quickly.
无论你是在 Scratch、Python（使用 IDLE、Mu 或 Thonny 等 IDE）还是基于块的编程环境中编码，都要确保你知晓如何打开正确的软件并设置好屏幕以便高效工作。对于 Python，要检查 Shell 和编辑器是否都可见，这样才能快速测试小段代码。
Adjust the font size if you struggle to read the code. In block-based environments, familiarise yourself with the categories: Motion, Looks, Events, Control, Sensing, Operators, and Variables. Knowing where blocks live saves frantic searching mid-task.
如果觉得代码难以阅读，可以调整字体大小。在基于块的环境中，熟悉各类积木：运动、外观、事件、控制、侦测、运算和变量。知道积木的位置可以避免在任务中途手忙脚乱地寻找。
Before you start the assessed task, create a new project and save it immediately with the correct file name. This tiny habit prevents the heartbreak of losing unsaved work if the application crashes. Run a quick 'Hello, World!' program or a simple script to confirm the environment interprets your code correctly.
在开始评估任务之前，新建一个项目并立即用正确的文件名保存。这个小习惯能避免因应用程序崩溃而丢失未保存作品的伤心事。运行一个快速的“Hello, World!”程序或一个简单的脚本，确认环境能正确解释你的代码。
6. Writing Code: Sequence, Selection and Iteration | 编写代码：顺序、选择与迭代
The three building blocks of any program are sequence (doing steps in order), selection (making decisions with if/else) and iteration (repeating with loops). The examiners will look specifically for these structures. A typical Year 7 task might ask: 'Create a quiz that asks three questions and gives a final score.'
任何程序的三个基本构件是顺序（按次序执行步骤）、选择（用 if/else 做决策）和迭代（用循环重复）。考官会特别留意这些结构。一个典型的七年级任务可能会要求：“创建一个问答游戏，询问三个问题并给出最终得分。”
For selection, show that you can use an if…elif…else ladder. In Scratch, this is the 'if then else' block. In Python, indent correctly. Example:
对于选择结构，要展示你能够使用 if…elif…else 阶梯。在 Scratch 中，这是“如果 那么 否则”积木。在 Python 中，要正确缩进。例如：
English: if score >= 80: grade = 'A' elif score >= 50: grade = 'C' else: grade = 'F'
中文：如果 分数 >= 80：等级 = 'A' 否则如果 分数 >= 50：等级 = 'C' 否则：等级 = 'F'
For iteration, use a for loop when you know how many times to repeat, or a while loop when you need to keep going until a condition changes. Demonstrate that you can avoid infinite loops by ensuring the condition can eventually become false.
对于迭代，当你知道重复次数时，使用 for 循环；当需要持续到某个条件改变时，使用 while 循环。通过确保条件最终能变为假，来展示你能够避免无限循环。
7. Using Variables and Simple Data Types | 使用变量与简单数据类型
Variables are like labelled boxes that store information. In a practical task you will need to create and manipulate variables. Use meaningful names: player_name is better than x. Show you can change a variable's value, join strings together, and convert between numbers and text when reading input.
变量好比贴了标签的盒子，用来储存信息。在实践任务中，你需要创建和操作变量。使用有意义的名字：player_name 比 x 更好。要展示你能够改变变量的值、拼接字符串，以及在读取输入时进行数字和文本之间的转换。
In Python, use input() to get data, but remember it always returns a string. If you need a number, convert with int() or float(). In Scratch, create a variable from the Variables palette and use blocks like 'set score to 0' or 'change score by 1' to update it.
在 Python 中，用 input() 获取数据，但要记住它返回的总是字符串。如果需要数字，就用 int() 或 float() 进行转换。在 Scratch 中，从变量面板创建一个变量，然后用“将 score 设为 0”或“将 score 增加 1”之类的积木来更新它。
Be prepared to handle different data types. A classic error in Year 7 assessments is trying to do arithmetic on a string. Demonstrate that you can test and fix this: age = int(input("How old are you? ")). Showing awareness of type conversion gains marks.
要做好处理不同数据类型的准备。七年级评估中的一个经典错误就是试图对字符串做算术运算。展示你能够检测并修复这个问题：age = int(input("你几岁了？"))。表现出对类型转换的认知能赢得分数。
8. Debugging with Purpose, Not Panic | 有意而非慌乱地调试
Bugs are a natural part of programming. The examiner wants to see how you deal with them, not that you never make mistakes. When your program doesn't work, take a deep breath and read the error message. In Python, the traceback tells you the line number and the type of error. In Scratch, observe which blocks are highlighted when the program misbehaves.
Bug 是编程中自然而然的一部分。考官想看到的是你如何应对它们，而不是你从不犯错。当程序不工作时，做个深呼吸并阅读错误信息。在 Python 中，回溯信息会告诉你行号和错误类型。在 Scratch 中，观察程序表现异常时哪些积木被高亮。
Use a systematic approach: isolate the problem, form a hypothesis, make one change and test again. Keep a debugging log – a simple table of Date, Problem, Attempted Fix, and Result. This log is excellent evidence for the testing and evaluation strand, and it shows resilience.
运用系统化的方法：隔离问题，提出假设，做出一个改动然后重新测试。记录一份调试日志——一张包含日期、问题、尝试的修复和结果的简单表格。这份日志是测试与评估维度的绝佳证据，并且展现了你的坚韧精神。
Common logic errors: off-by-one in loops, forgetting to update a variable, or placing blocks in the wrong order. Check your loop counters carefully. If you need help, try rubber duck debugging: explain your code line by line to an imaginary duck. Speaking aloud often reveals the flaw.
常见的逻辑错误包括：循环中的差一错误、忘记更新变量、或者把积木放在了错误的顺序。仔细检查循环计数器。如果你需要帮助，试试小黄鸭调试法：逐行向一只想象中的小黄鸭解释你的代码。大声说出来常常能揭示缺陷。
9. Testing with a Test Plan | 使用测试计划进行测试
Testing is not an afterthought; it earns you marks. Create a test plan before you finish coding. A simple table with columns: Test Number, Test Data, Expected Outcome, Actual Outcome, and Pass/Fail. Include normal data (e.g., 15 for an age input), boundary data (values at the edge, like 0 or 100), and erroneous data (like typing 'twelve' instead of 12).
测试不是事后才补做的事情；它能为你赢得分数。在完成编码之前就创建一个测试计划。一张简单的表格，包含以下列：测试编号、测试数据、预期结果、实际结果、通过/未通过。测试数据要包含正常数据（例如年龄输入 15）、边界数据（临界值，如 0 或 100）和异常数据（例如输入 'twelve' 而不是 12）。
Run each test and record what actually happened. If a test fails, fix the bug, re-run the test and update the log. This iterative process shows that you follow a development cycle, which is a higher-order skill. The WJEC practical mark scheme often rewards evidence of thorough testing over a flashy but untested program.
运行每一个测试并记录实际发生的情况。如果某个测试未通过，修复 bug，重新运行测试并更新日志。这种迭代过程表明你遵循了开发周期，这是一种高阶技能。WJEC 实践评分方案通常奖励详尽测试的证据，而非一个花哨但未经测试的程序。
If you are short on time, test the most critical paths first: the happy path that the user is expected to follow, and at least one scenario where the user makes a mistake. Always screenshot or copy the evidence of your test runs into your 'Evidence' folder.
如果时间紧张，优先测试最关键的路径：用户预期会遵循的成功路径，以及至少一个用户犯错的场景。总是将测试运行的证据截图或复制到你的“证据”文件夹中。
10. Presenting Evidence and Commentary | 展示证据与评论
Your practical folder should tell the story of your project. Alongside the program files, include your design documents (flowchart/pseudocode), a completed test plan with outcomes, and a short evaluation paragraph. The evaluation should mention what worked well, what was challenging, and how you would improve the program if you had more time.
你的实践文件夹应该讲述项目的来龙去脉。除了程序文件，还要包含你的设计文档（流程图/伪代码）、一份包含结果的完整测试计划，以及一段简短的评价。评价应提及哪些部分做得好，哪些部分具有挑战性，以及如果有更多时间你会如何改进程序。
In your commentary, reference the success criteria. For example: 'I met the requirement to give feedback after each answer by displaying a message for two seconds using a wait block.' This shows the examiner you can reflect critically and link your work to the original brief.
在评论中，引用成功标准。例如：“我满足了这个要求，即在每次回答后通过使用等待积木显示两秒钟的信息来给出反馈。” 这向考官展示了你能够批判性反思并将你的工作与原始任务说明联系起来。
If you have worked in a pair or group, clearly state your individual contribution. While collaboration is encouraged in some tasks, your assessment is individual, so write down what parts of the code you wrote, what you tested, and what ideas you contributed.
如果你是以结对或小组形式工作的，要清楚说明你的个人贡献。虽然某些任务鼓励协作，但评估是针对个人的，所以要写下你编写了哪些代码部分、测试了什么，以及贡献了哪些想法。
11. Time Management During the Assessment | 考核期间的时间管理
Typical practical assessments last between 45 and 60 minutes. Break the time into chunks: 10 minutes to read the brief and plan, 25 minutes to code, 10 minutes to test, and the final 5–10 minutes to gather evidence and write a short evaluation. Stick to this structure even if your program isn't fully polished; a basic working program that is well-documented scores higher than an ambitious broken project.
典型的实践考核持续 45 到 60 分钟。将时间分块：10 分钟阅读任务说明和规划，25 分钟编码，10 分钟测试，最后 5-10 分钟收集证据并写简短评价。即使你的程序并非完美无瑕，也要坚持这个结构；一个有良好文档的基础运行程序，比一个雄心勃勃但故障百出的项目得分更高。
Glance at the clock periodically. If you are stuck on a bug for more than five minutes, move on and implement another feature. You can always return later, but you must have a running program to test. A program that works partially is still evidence of your coding skills.
时不时看一下时钟。如果你花在某个 bug 上的时间超过五分钟，就继续去实现其他功能。你随时可以再回来解决，但你必须有可以运行的程序用来测试。一个能部分运行的程序仍然是你编程技能的证据。
Use the last few minutes to double-check file saves and naming conventions. A common mistake is submitting a file that cannot be opened because it was saved in a temporary location or with an extension the teacher's computer doesn't recognise. Always double‑click your saved file to ensure it opens correctly.
利用最后几分钟反复检查文件保存和命名规范。一个常见的错误是提交了一个无法打开的文件，因为它被保存在了临时位置，或者带有教师计算机无法识别的扩展名。始终双击你保存的文件，确保它能正确打开。
12. Summary Checklist for Practical Success | 实践成功总结清单
Use this checklist the day before and during the assessment to stay on track:
在评估前一天和评估期间使用这份清单，确保不偏离轨道：
English: Read the task brief twice and highlight key words. / Chinese: 阅读任务说明两遍，并高亮关键词。
English: Create a simple flowchart or pseudocode. / Chinese: 创建一个简单的流程图或伪代码。
English: Save a new project immediately with a sensible name. / Chinese: 立即用一个合理的名字保存新项目。
English: Use sequence, selection (if/else) and iteration (loops) clearly. / Chinese: 清晰地使用顺序、选择（if/else）和迭代（循环）。
English: Include meaningful variable names and comments. / Chinese: 包含有意义的变量名和注释。
English: Test with normal, boundary and erroneous data; record results. / Chinese: 用正常、边界和异常数据进行测试；记录结果。
English: Write a short evaluation: what worked, what you would improve. / Chinese: 写一段简短评价：哪些有效，你会改进什么。
English: Ensure all evidence is saved in the correct folder with correct file names. / Chinese: 确保所有证据都保存在正确的文件夹里，并使用正确的文件名。
Remember, the practical assessment is your chance to show what you can do, not just what you know. Stay calm, manage your time, and enjoy the process of bringing your ideas to life through code.
记住，实践考核是你展示你能做什么，而不仅仅是你知道什么的机会。保持冷静，管理好时间，享受通过代码将想法变为现实的过程。
Published by TutorHao | Computer Science Revision Series | aleveler.com
更多咨询请联系16621398022（同微信）
或截图后用「扫一扫 → 相册」选择本图