The app went live. Now what?
Your app is finished. Hundreds of people download it.
On Monday a user writes: "The pay button does nothing." On Tuesday the bank changes a rule. On Wednesday the client asks for a new feature.
Release is not the end. This lesson covers the last three stages.
Key words
| Word | What it means | Example |
|---|---|---|
| Prototype | An early, simple version that you can try. | a clickable first version |
| Module testing | Testing one small part of the software alone. | test the total function |
| Integration testing | Testing that the parts work together. | order screen and payment together |
| Automated testing | Tests that a program runs by itself, again and again. | tests that run after every change |
| User testing | Real users try the software and say what they think. | five customers try ordering |
| Version control | A tool that keeps every version of your files, and who changed what. | Git |
| Deploy | Put the software where users can use it. | publish the app |
| Maintenance | Looking after the software after it is released. | fix bugs, add features, help users |
The cells students fill in are left blank in this preview.
Quick check: which test?
Have a go
Quick check: which test?
3 questionsYour answers are marked here and are not kept. A college account keeps every student’s marks.
Four kinds of testing
| Kind | Who or what tests | What is tested | Why |
|---|---|---|---|
| Module testing | Developer | One part alone | Finds small bugs fast |
| System integration testing | Tester | Parts working together | Finds problems between parts |
| Automated testing | A program | Anything, again and again | Catches new bugs when code changes |
| User testing and feedback | Real users | The whole product in use | Shows if people can really use it |
The cells students fill in are left blank in this preview.
Start with a prototype
Do not build everything at once. Build a prototype first. It is small and rough, but real users can try it.
You learn fast and cheaply. Each round you improve it and test again.
Deploy: get it to the users
Deploying has four jobs.
Install and configure: put it on the server or in the app store and set it up. Update: send fixes and new versions. Document: write down what changed and why. Version control: keep every version, so you can go back.
Now look at a real history. Press Start on the lab bar. Then press Run on each step below.
See a project history: step 1
git clone http://gitea:3000/student/hello-git.gitA command for the lesson’s lab terminal. It is shown here and not run.
Step 2: go into the folder
cd hello-gitA command for the lesson’s lab terminal. It is shown here and not run.