Testiranje in preverjanje aplikacij
OpenFactory ima dve povezani področji:
- image scenarios, ki zaženeta zgrajen artifact in izvedeta omejene guest assertions; in
- predogled app-platform, ki ustvari immutable app variants ter workflowe UI-test in walker.
Razpoložljivost se med moduli app-platform močno razlikuje. Pred uporabo preberite stanje na vsaki strani.
Razpoložljivost app-platform
| Tema | Trenutna meja |
|---|---|
| App Deployment | V vrsto postavi Git source skozi immutable variant pipeline; spremljajte asinhroni deployment in health evidence. |
| App UI Testing | Shranjuje in izvaja omejene semantic scenarios proti dosegljivim targets; rezultati dokazujejo le navedene actions in assertions. |
| Prompt-assisted deployment | Zahteva obstoječ template Git URL; brief je provenance, ne source generation. |
| App environment variables | Encrypted storage in deployment handoff sta implementirana, ko so nastavljeni zahtevani keys/tokens; rotation in runtime evidence ostajata skrb operaterja. |
| Managed Databases | Le stub contract; nobena baza se ne provisionira. |
| Object Storage | Le stub contract; noben bucket se ne provisionira. |
| Custom Domains | Le Public-DNS ownership verification; custom TLS serving/routing ni aktiven. |
| Checkpoints | Le stub identifiers; recoverable snapshot ne obstaja. |
| Observability | Manual event storage in VM allocation sta resnična; ingest, probes, samples, logs in dashboard so nepopolni. |
| Web IDE | Le stub binding; editor ali private route se ne provisionira. |
| App Auth | Le stub binding; identity provider, issuer ali real token flow se ne provisionira. |
| Templates and Remix | Ustvari app records iz manifestov ali eligible source lineage; ne deploya in ne ustvari samodejno declared services. |
| Autonomous Walker | Omejeno UI discovery z pomembnimi limiti coverage, authorization in side effects. |
| Walker Diffs | Primerja stored walks in izvozi ticket-shaped payloads; zunanjih tickets ne vloži sam. |
| Walk and Fix | Ustvari fix intent; legacy live-VM patching je v sporu z immutable deployment model. |
Ne vključujte stub adapter v produkcijski workflow zato, ker je njegov API vrnil success.
Image scenarios
Image tests tečejo le, če jih izbrani build/scenario omogoči in je na voljo zahtevana test infrastructure. Ta stanja ločite:
- artifact construction;
- guest provisioning in boot;
- assertion execution;
- evidence finalization; in
- certification or publication policy.
Build lahko uspe, medtem ko so testi onemogočeni, pending, failed ali incomplete.
Oblikovanje testov
Vgrajeni testi
Vgrajena imena, kot so boot, login, packages, network in services, dajejo osnovo. Natančne omejitve so v Default Tests.
Custom assertions
Za service, port, HTTP, file, command, process in podprta GUI opažanja uporabite Custom Assertions. Vsaka assertion naj vsebuje opis, expected result, target, timeout in pomen neuspeha.
Benchmarks
Benchmark catalogs so strukturirane množice preverjanj, ne compliance determinations. Ujemite natančen OS/version, obdržite applicability in failures ter preberite CIS benchmark evidence.
Kontrolni seznam evidence
Pri teku, ki nosi odločitev, obdržite:
- recipe, source, build, artifact, VM, scenario in run IDs;
- natančne artifact in source digests;
- test environment in runner version;
- vsak rezultat assertion in raw output;
- screenshots le kjer je upravičeno in varno obdelano;
- manjkajoča, skipped ali not-applicable checks;
- timestamps in terminal status; in
- reviewer disposition in odobritev za navedeno odločitev.
Ko test ne uspe, najprej diagnosticirajte plast, ki odpove, šele nato rebuild. Podvojen build lahko skrije napako v ownership, deployment, test-runner ali evidence finalization namesto da jo odpravi.