Skillnaija Start free

Your first robot, tested honestly: a build-and-test log

The capstone project for Robotics: Run and Test Your First Robot on a Simulated Bench — a free AI & Emerging Tech course. Pass it and you earn a certificate anyone can verify.

Start the course free Download the project workbook

The project unlocks once you complete the lessons. The workbook is free to download now so you can see exactly what is expected.

What you will submit

One shared Google Doc link with the robot sheet, the readings sheet, the motors and power sheet, the rules and state tables, the test-case tables for both robots, the build-and-test log and the real-parts plan with the honest statement, with screenshots of the bench and its printed lines (four are enough); plus a write-up (5,000 characters at most) that pastes the words proving each part, with each row of a table written as one line.

What to do, step by step

  1. Run and test the course's two robots, an obstacle-avoider and a line-follower, on the bench inside the lessons: the Run this code button under each sketch, in the English web lesson in your browser. The whole project can be done on a phone. A robot tested on the bench is fully accepted: nothing in this project requires parts, a computer or any other simulator, and real parts earn no extra marks. You do not type code on the bench: where a part says to run a version, choose it from the bench's list. Nothing in your project touches mains, flies, or is meant to hurt, frighten or spy on anyone. Your evidence is what the bench printed and what each wheel was told to do, written down as it happened.
  2. Part 1. Robot sheet (one page): the phone or computer and the browser you used; sense, think, act for the obstacle-avoider in three lines; the three-question test on one machine near you; the nine bench rules in your own words; and the LED resistor sum for one resistor (voltage left for the resistor ÷ resistance = current), checked against the pin limit of the board you name.
  3. Part 2. Readings sheet: your first run of blink (whether the bench ran, and whether it said slow motion); what happened with the two blink timing versions (what you predicted and what you saw by the bench's clock); five distance readings (the wall you set, the microseconds printed and the centimetres printed), with the ÷ 58 sum worked for one of them; and what each eye prints over the floor and over the line.
  4. Part 3. Motors and power sheet: the motor test as a table (the line printed at each step, what each wheel was told to do, and the bench's clock); in your own words and numbers, why a pin cannot drive a motor; a power budget for a real two-motor robot on AA cells, with each figure's source and the sum for three cases (both wheels running free, one wheel blocked, both blocked), saying which case decides how you power the motors; and your decision on lithium cells: either 'AA only', or the rules you would follow.
  5. Part 4. Rules and state tables, written before you test the robots: plain if-then rules and a three-row state table for the obstacle-avoider, in which every possible reading has exactly one row, and the four-row table for a line-follower with two sensors. If testing showed that a row of your first line-follower table was wrong, keep the draft and add the corrected table.
  6. Part 5. The two robots tested: a test-case table for each robot, with what you expected (decided before you looked) beside what happened. For the obstacle-avoider give at least six cases on the bench as printed, among them 19, 20 and 21 cm at the edge of the rule, one very near reading and one far reading, each with the line the bench printed and what each wheel was told to do, plus one case you could not test on the bench as printed, and why (if you closed it later with a listed version, your log says so). For the line-follower test all four rows and write the line the bench printed for each.
  7. Part 6. Build-and-test log, kept from Lesson 3 onwards: at least eight dated entries (your blink notes from Lesson 3 count). Each entry runs one version from the bench's list or changes nothing (an entry that only runs a test on the sketch as printed says 'changed: nothing'), with what you expected, what happened (the lines the bench printed) and what you did next. Versions never add up: each is the sketch as printed with that one change. Keep the failures in: on the bench a failure is a prediction of yours that turned out wrong, or a test that a version failed; if you had none, say so and invent none. Show one fault found and fixed, with the result before and after: one of the bench's two faulty builds (Lesson 10, the versions called 'A faulty build: find the fault'), or a fault of your own on real parts or a computer, and say which. For a faulty build, write each test you ran and its result (which failed and which still passed), the line you suspected before you tapped 'Show the changed line', the line the bench then showed (its number, was and now), and that 'As printed' then passed the same tests. A wrong guess is not marked down: write it as it was. End with three things the bench did not prove about a real robot.
  8. Part 7. Real-parts plan and honest statement. Either a shopping list for a real version, with each part, its price, the shop's name and the date you read it, and the sum shown as an estimate that says what it leaves out (such as VAT, delivery or batteries); or the sentence 'I am staying on the bench', with what that leaves unproven. Buy nothing for this project. Then five sentences: what your robot does, what it cannot do, what you tested, what you did not test, and what you would learn next. Promise nothing you have not tested.
  9. Put everything in one Google Doc (on a phone, use the free Google Docs app, with a Google account). Four screenshots of the bench are enough: one distance reading, the obstacle-avoider at 19 or 20 cm, one line-follower row, and, if your fault was one of the bench's faulty builds, that build with its changed line showing. Clear photos of handwritten sheets are fine for everything else. Set sharing to 'anyone with the link can view', and submit the link. In the write-up box (5,000 characters at most) paste the words that prove each part, a line or two each, because your write-up is what gets marked; write each row of a table as one line. Paste: the device you used; your sense, think, act lines; one distance reading with its ÷ 58 sum; your pin-against-motor sum; both state tables (with the corrected line-follower table, if testing changed a row); five obstacle test cases with expected and actual (19, 20 and 21 cm, one very near reading and one far reading); the case you could not test on the bench as printed, with why, and how you closed it or that it is still open; the four line-follower rows with the line the bench printed for each; a one-line list of all your log entries (date and version run); two log entries in full, the fault and the fix (for a faulty build: your tests, your guess before you looked, the line the bench showed, and 'As printed' passing); three things the bench did not prove; your shopping total with its date and shop, or 'bench only'; and your five-sentence honest statement.

Files to work with

Project workbook (fill in, then submit)The whole brief, an evidence checklist, the grading rubric as a self-check and the link-sharing steps in one file. Opens in Word, Google Docs or WPS.Word · 9 KB

How it is graded

CriterionWeight
The robot sheet, readings and sums show real understanding: sense, think, act; a printed line read with the right units; and why a pin cannot drive a motor, in numbers20%
The rules and state tables were written first, cover every case exactly once, and match what the robots did when tested (a first draft corrected after testing, with the correction shown, counts in full)20%
The test cases are specific: expected results decided before looking, the edge of the rule tested at 19, 20 and 21 cm, a very near reading and a far reading tested, all four line-follower rows covered, and a case that could not be tested on the bench as printed admitted and explained25%
The build-and-test log is honest and useful: at least eight entries, each running one listed version or changing nothing, the printed lines recorded, failures and wrong predictions kept in, and one fault found and fixed with before and after (one of the bench's faulty builds counts when the log says so, gives the learner's guess before looking and names the line the bench showed)25%
Safe and honest about limits: the device is stated, what the bench did not prove is named, the real-parts plan uses dated prices from named sources or says 'bench only', and the statement promises nothing untested10%

You need 65% overall to pass. A failed submission comes back with feedback and can be revised and resubmitted once free; further attempts come with the All-Access Pass or as a paid retake.

Before you submit: make your link public

If your work lives in Google Drive or Google Docs, open Share → General access and change “Restricted” to “Anyone with the link” (Viewer). Then paste the link into a private browser window: if it opens without sign-in, you are ready. A private link cannot be graded — it is the single most common reason a good project fails.

Frequently asked questions

Do I have to finish Robotics: Run and Test Your First Robot on a Simulated Bench before submitting the project?

Yes. The submission screen opens once every lesson in Robotics: Run and Test Your First Robot on a Simulated Bench is marked complete. The lessons are where the methods, the local context and the worked examples the project depends on are taught.

How is the project graded?

An examiner scores each rubric criterion from 0 to 100 and weights them as shown on this page; you need 65% overall to pass. Most submissions are graded within minutes and you get written feedback on what was strong and what to improve.

Can I resubmit if I fail?

Yes. A failed project comes back with feedback; revise the weak parts and resubmit. A passed project is final — the certificate is issued and cannot be re-rolled.

What do I actually submit?

A write-up of what you did (under 5,000 characters) plus a public link to your work — a Google Drive folder, Google Doc, spreadsheet, GitHub repository or video. The link must open without sign-in; a private link cannot be graded. The free project workbook on this page walks you through all 9 steps.

Is the certificate real?

Yes. Passing this project issues a certificate with a unique verification code. Anyone — an employer, a client, a school — can open the verification page and see that the certificate is genuine and which project earned it.

More AI & Emerging Tech projects

Ready to earn this certificate?

Robotics: Run and Test Your First Robot on a Simulated Bench is self-paced. Finish the lessons, complete this project, and the certificate is yours to share.

Start learning free