QA and testing
The same input every run, down to the character
You are three screens into the signup flow and you need the 300 character name again. Typed out by hand it comes back 299 or 301, the field behaves differently, and the report describes a bug nobody else can reproduce.
For iPhone, iPad, Mac & Apple Vision Pro · Android on Google Play · Windows coming soon
One card, 300 characters, unchanged since the day it was saved.
Three runs, one string
Nothing on the screen tells you which of the three you just typed. Each one makes the field behave differently, and only one of them is the value you wrote into the report. Pasting from a card removes the question.
Three runs, three different strings
Three runs, the same string
public/screenshots/en/qa-field-crop.webpmac-dark/en-US/en-mac-11-field-overflow.pngThe counter reads 300 of 120, which is the bug. Paste the same card tomorrow and it reads 300 of 120 again, which is what makes this a report rather than a story.
The seven that keep coming back
Every one of these has broken something. Kept as cards, the value in the field and the value in the report are the same value, and that is what a second person needs before they can watch it happen too.
| Value | What it tends to break | Key | |
|---|---|---|---|
| 01 | Maaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa | Column widths, and any field that trusts its own maximum length | ⌘1 |
| 02 | 👨👩👧👦🇹🇼🏳️🌈👋🏽 | Character counts, because not one of these is a single character | ⌘2 |
| 03 | مرحبا بالعالم | Alignment, punctuation order and where the text gets cut | ⌘3 |
| 04 | 007 | Anything that keeps a reference as a number | ⌘4 |
| 05 | " " | Required field checks that only test for empty | ⌘5 |
| 06 | [email protected] | Address filters that stop reading at the plus sign | ⌘6 |
| 07 | 2024-02-29 | Date handling on a leap day | ⌘7 |
public/screenshots/en/qa-report-notes.webpmac-dark/en-US/en-mac-12-bug-report.pngFile it with the steps already written
The template card carries the five headings your team reads first. The steps carry the input itself, pasted in rather than described, so whoever picks the bug up runs exactly what you ran.
- 01Summary
- 02Steps to reproduce
- 03Expected
- 04Actual
- 05Build and device
Saved once, then pasted for the rest of the round
- 01
Library
A folder per project, full of what breaks it
Boundary strings, right to left text, an emoji in the middle of a surname, a date in a format nobody planned for, the sample addresses and phone numbers every form asks for, the tester addresses on example.com your team files under. The report template and the repro step skeleton sit in the same folder, one card each, so the write up starts with a shape.
- 02
Menu bar
One click from the build under test
1SecCopy sits in the Mac menu bar, next to whatever you are poking at. Click the icon and the cards drop over it. Click a card and the value lands in the field the cursor is in. Press ⌘1 to ⌘9 for the nine this round keeps asking for. On an iPhone or iPad build, the 1SecCopy keyboard types the same values into the app under test.
- 03
Sync
The same value on the device you pick up next
The input that broke the form on your Mac is on the iPad when you pick it up to check the tablet layout, usually about a second after you saved it. One set of test data across the devices you test on, so the run you did before lunch is the run you can repeat after it.
Cross-device sync is included with Premium.
Other people who copy and paste for a living
Stop typing the same thing twice.
Get 1SecCopy on the App Store or Google Play. Free to start.
For iPhone, iPad, Mac & Apple Vision Pro · Android on Google Play · Windows coming soon