What to learn next
Pick your next page based on what you want Optics to do for you.
You've run a test and know the basic pieces. Optics has a lot more in it, and you don't need most of it on day one. Start from the goal closest to yours.
I want to test my own app#
AndroidEmulators and phones through Appium.iOSSimulators and iPhones through Appium.WebAny website through Playwright or Selenium.
I want to create tests faster#
Record a testNo codeRun steps one at a time against the live app and save the ones that worked.Describe a test in plain EnglishAILet an AI model drive the app from a sentence, then keep its steps.Let your AI agent build testsAIConnect Optics to Claude, Cursor or any MCP client.Use Optics from PythonCodeCall keywords from pytest or your own scripts.
I want tests that break less#
Define elementsGive elements fallback values that survive redesigns.Find elements by text and imageUse OCR and pictures when the UI tree can't help.
I want to run tests every day#
Run tests in CIRun the suite on every pull request.Catch error screensFail the run when the app shows a crash or "Session expired".
A suggested order#
If you're learning Optics from scratch, this order adds one idea at a time:
- Write a test suite: the file formats in full.
- Define elements: locators that last.
- Run a suite and read the results.
- Organise a suite: setup, teardown and reuse.
- Variables and data-driven tests: one flow, many inputs.
- Run tests in CI, then work through the readiness checklist.