Skip to main content

AI-powered learning for institutions

Teach with AI, and give every learner a path

Your teachers prepare the course outline, lessons, assignments and exams with AI. Each learner follows a path planned for them, and the cohort meets live on Google Meet.

CCueTA™Cuesoft Talent Academy
TodayTeachCoursesLesson StudioExamsGrading6AssistantProgressPeopleCohortsLive SessionsOOOlaife Olawore

Unit, integration and end-to-end automation

Lesson studio · AI-Assisted Quality Engineering & Testing · module 2 of 4 · for the September 2026 cohort

Draft · 9 min 30

Outline

From the outline and the cohort’s answers

Missed a mocking question15 of 24
Passed test strategy9 of 24
Three kinds of testShorter for 9
0:00 · Blackboard · 2 min · recorded
One slide for the 9 who passed test strategy; three slides for the rest.
A unit test with a fake databaseLonger
2:00 · IDE · 3 min · recording
A second example with a real database call, because 15 of 24 missed mocking on Tuesday.
The end-to-end run in the browser
5:00 · Browser · 2 min 30 · script ready
What to test before Monday
7:30 · Blackboard · 2 min · script ready
After the lesson
  • Quiz: testing basics8 questions
  • Practice: fix a flaky testFor the 9
Materials
orders-api Startertest/orders.test.tsci.ymlTest Report Page
orders.test.tsorders.tsIDE
orders-apisrcorders.tsdb.tstestorders.test.ts.github/workflowsci.yml
1import { it, expect, vi } from 'vitest'2import { createOrder } from '../src/orders'3 4it('saves the order, returns its id', async () => {5 const db = { insert: vi.fn() }6 db.insert.mockResolvedValue({ id: 42 })7 const order = await createOrder(db, { qty: 2 })8 expect(db.insert).toHaveBeenCalledOnce()9 expect(order.id).toBe(42)10})11// no real database: this runs in 4 ms
Terminal$ npm test -- ordersPASS test/orders.test.ts · 1 test, 4 ms
IDE · 2:00 to 5:00 · the orders-api starterEdit CodePreview from 2:00

AI Draft

IDE segment · edited by you

Narration at 2:00
“Now we hand the service a fake database, so this test runs in milliseconds and never touches a real server.”
Why 3 minutes: 15 of 24 missed a mocking question on Tuesday.
New to Mocking · 15a second example
Ready · 9skip to CI at 4:10
Keep DraftRewrite

Voice-Over

Olaife Olawore · at the 2:00 mark

  • Take 2 · kept2 min 58
  • Take 13 min 06
Recorded in your own voice. Learners hear it from 2:00, with captions.
Record AgainPlay Take 2
4:20 / 9:30Voice-over: 2 of 4 marks recordedSegments snap to marks
0:001:002:003:004:005:006:007:008:009:00
Marks0:002:005:007:30
Surfaces0:00BlackboardThree kinds of test2:00IDEA unit test with a fake database5:00BrowserThe end-to-end run in the browser7:30BlackboardWhat to test before Monday
Voice-overTake 1 · 1 min 56Take 2 · 2 min 58 · keptNot recorded yetScript ready
CCueTA™Cuesoft Talent Academy
TA

Unit, integration and end-to-end automation

AI-Assisted Quality Engineering & Testing

orders.test.tsorders.tsIDE
orders-apisrcorders.tsdb.tstestorders.test.ts.github/workflowsci.yml
1import { it, expect, vi } from 'vitest'2import { createOrder } from '../src/orders'3 4it('saves the order, returns its id', async () => {5 const db = { insert: vi.fn() }6 db.insert.mockResolvedValue({ id: 42 })7 const order = await createOrder(db, { qty: 2 })8 expect(db.insert).toHaveBeenCalledOnce()9 expect(order.id).toBe(42)10})11// no real database: this runs in 4 ms
Terminal$ npm test -- ordersPASS test/orders.test.ts · 1 test, 4 ms
0:00Blackboard2:00IDE5:00Browser7:30Blackboard
2:40 / 9:30Voice-over by your teacher1×
Olaife Olawore, at 2:40
“Now we hand the service a fake database, so this test runs in milliseconds.”

Chapters

Three surfaces, four marks

Three kinds of test0:00 · Blackboard · 2 min
Watched
A unit test with a fake database2:00 · IDE · 3 min
Now
The end-to-end run in the browser5:00 · Browser · 2 min 30
What to test before Monday7:30 · Blackboard · 2 min

Made for You

Your path adjusted this lesson

The IDE part runs longer
Mocking was your gap, so you get a second example with a real database call.
The recap is one slide
You passed test strategy on Wednesday, so the pyramid takes a minute, not three.
TodayPathTasksProgress
From first call to first cohort

Here is how it goes

Follow one institution from our first conversation to its first cohort.

  1. CCueTA™Cuesoft Talent Academy
    • Your name and mark on every screen
    • Three tiers and twenty courses, as you teach them
    • A new cohort on the 1st of every month

    We set up your institution

    Your name and mark on every screen, with your own courses, cohorts and teachers. Nothing assumes one curriculum.

  2. Course Outline

    AI-Assisted Software Engineering · drafted with AI

    AI-Assisted Frontend Engineering
    4 modules · reviewed by Olaife Olawore
    AI-Assisted Backend Engineering
    4 modules · Mubin Sheidu, MEng is editing

    Your teachers prepare with AI

    They bring the course outline. We draft the lessons, assignments and exams, and they edit them first.

  3. Open Your Canvas

    canvas.cuesoft.io

    Invite code from your teacherK7QM-2Y4PJoin the Cohort

    Your learners sign in

    Each learner opens their canvas at canvas.cuesoft.io with an invite code, and their path is ready.

Everything below is your institution, up and running.

Blackboard

Give it the topic. We draft the slides

Name the lesson and we draft the Blackboard from your course outline and the cohort’s quiz answers. You change what you like before any learner sees it.

WHAT IT IS WORTH
  • From your outline
  • Edited by you
  • Cohort-aware
  1. New lesson
  2. Three kinds of test
  3. In the outline

IDE

The code is typed and run on screen

At 2:00 the lesson moves into the IDE. The files are real and the terminal runs the tests, so a learner who pauses can open them and try it too.

WHAT IT IS WORTH
  • Real files
  • A real terminal
  • Pause and try
  1. orders.test.ts
  2. The AI’s narration
  3. Paused at 2:40

Browser

The result opens inside the lesson

At 5:00 the lesson opens the browser on the test report the code just produced. Then it returns to the Blackboard for what to test before Monday.

WHAT IT IS WORTH
  • The real result
  • No tab switching
  • Back to recap
  1. Script ready
  2. Test report
  3. What to test before Monday

The timeline

Your voice, recorded at the marks

Blackboard at 0:00, IDE at 2:00, Browser at 5:00, then Blackboard again. You record your voice at each mark and we animate it into one lesson.

WHAT IT IS WORTH
  • Your own voice
  • Captions
  • Snaps to marks
  1. Four marks
  2. Take 2 kept
  3. Ready for the cohort

One lesson, prepared once and played by each learner

The teacher prepares it once in the studio. Each learner plays it with the parts that matter to them running longer.

Unit, integration and end-to-end automation

Lesson studio · prepared once by Olaife Olawore · 9 min 30

Draft
4:20 / 9:30Voice-over: 2 of 4 marks recordedSegments snap to marks
0:001:002:003:004:005:006:007:008:009:00
Marks0:002:005:007:30
Surfaces0:00BlackboardThree kinds of test2:00IDEA unit test with a fake database5:00BrowserThe end-to-end run in the browser7:30BlackboardWhat to test before Monday
Voice-overTake 1 · 1 min 56Take 2 · 2 min 58 · keptNot recorded yetScript ready
0:00Blackboard2:00IDE5:00Browser7:30Blackboard
2:40 / 9:30Voice-over by your teacher1×

Made for You

Your path adjusted this lesson

The IDE part runs longer
Mocking was your gap, so you get a second example with a real database call.
The recap is one slide
You passed test strategy on Wednesday, so the pyramid takes a minute, not three.
Then: Quiz: testing basics8 questions · prepared with AI, checked by Olaife Olawore

A path for each learner

Every learner gets a path planned for them

After every quiz and assignment we adjust each learner’s path, with the reason in plain words. The teacher sees every change and can undo it.

WHAT IT IS WORTH
  • Plain reasons
  • Teacher can undo
  • Nothing dropped
  1. Tuesday’s quiz
  2. What changed this week
  3. Today’s plan

An AI tutor that hints

Hints and questions, never the answer

Stuck on an assignment, a learner asks the tutor. It points to the right file and asks the question a mentor would ask, then leaves the work to them.

WHAT IT IS WORTH
  • Their own work
  • Hints only
  • Checks first
  1. What your teacher checks
  2. A hint, not the answer
  3. Submit for review

Cohorts and live sessions

Open a cohort and invite its learners

Share one invite code, accept the requests and set the week’s live sessions. Each session gets its own Google Meet link on every learner’s plan.

WHAT IT IS WORTH
  • One invite code
  • Google Meet
  • No links to chase
  1. Invite code
  2. Requests to accept
  3. Live sessions on Google Meet

Who needs you this week

See who needs a check-in, and why

We read the week’s study time, quiz answers and checks, and tell you in plain words who is falling behind. You decide who to talk to.

WHAT IT IS WORTH
  • Reasons, not scores
  • You decide
  • Caught early
  1. Needs attention
  2. Ask the assistant
  3. On Google Meet

Grading

Marks you confirm, feedback you approve

We read the pull request against your rubric and suggest each mark with its evidence. You confirm every mark, and feedback goes out only when you approve it.

WHAT IT IS WORTH
  • Evidence shown
  • Your rubric
  • You approve
  1. Pull request #7
  2. Marks to confirm
  3. Feedback to approve

Exams

Questions from the outline, keys you confirm

We draft the exam from the course outline and what the cohort covered, with a marking key for every question. You confirm each key and set the sitting on Google Meet.

WHAT IT IS WORTH
  • Only what was covered
  • Keys you confirm
  • On Google Meet
  1. Questions from the outline
  2. Keys to confirm
  3. Wednesday on Google Meet

For families

Parents follow the week in plain words

Parents see each linked learner’s week: what they finished, what is due and what the teacher noticed. They download the report and ask for a meeting.

WHAT IT IS WORTH
  • Plain words
  • Weekly PDF
  • Meet a teacher
  1. The week in plain words
  2. Weekly reports
  3. Request a meeting
Coming soon

And more is on the way

Each one arrives inside the canvas your teachers and learners use.

  • Study groups

    Coming soon

    Learners on the same module find each other, form a group and meet on Google Meet.

    Study Group · Mocking

    4 learners on this module this week

    AOSBTACO
    Thursdays at 19:00, on Google Meet
  • Messages

    Coming soon

    Learners and teachers write to each other inside the canvas, in the cohort or one to one.

    Anyone else stuck on the Postgres service in CI?Amaka · September 2026 cohort
    Yes. Check the ports line in ci.yml first.You · 18:42

Get started

Bring Cuelearn™ to your institution

Tell us about your institution, your courses and your cohorts, and we will walk you through Cuelearn™ on a call. Nothing is paid on this site.

  1. Your institution

    We set up your name, your courses and your first cohort

  2. Your teachers

    They prepare their first lessons in the studio with us

  3. Your learners

    They sign in at canvas.cuesoft.io with an invite code

Request a Demo

We reply within one business day. Nothing is paid on this site.