QA-példák

Így néz ki a tesztelés dokumentációja.

Két szemléltető példa mutatja, hogyan tervezi, hajtja végre és jelenti a DOKRAVE a tesztkört: terjedelem, forgatókönyvek, eredmények, észrevételek és újratesztelés.

Ajánlatot kérek

A példákról

Mindkét példa szintetikus bemutató, gyakori API- és integrációtesztelési minták alapján. A nevek, adatok és rendszerrészletek általánosak, valódi ügyfél vagy éles rendszer nem szerepel bennük. A dokumentáció angolul olvasható, ahogy a tesztdokumentáció általában.

01

API rendeléslétrehozás

Funkcionális, hitelesítési és adatvalidációs tesztelés

Egy rendeléslétrehozó végpont ellenőrzése érvényes kérésekre, hozzáférés-védelemre, kötelező mezőkre és a tárolt adatokra. Az első hitelesítési hiba megtalálva, javítva és újratesztelve.

  • 6 forgatókönyv
  • 5 Megfelelt
  • 1 Hibás
  • 1 észrevétel
Áttekintés / Terjedelem / Módszer

Áttekintés

A synthetic demonstration of testing an API endpoint that creates business orders. It covers request handling, authentication, input validation and verification that submitted data is correctly stored.

A tesztelés célja

Verify that an order-creation endpoint accepts valid authenticated requests, rejects unauthorised or invalid requests, and persists submitted information consistently.

Terjedelem

  • Successful order creation using a valid authenticated account.
  • Access control when no valid authentication is supplied.
  • Required-field and malformed-input handling.
  • Verification of created order data in the application and underlying data store.
  • Retesting after an authentication defect is corrected.

Nem része

  • Full penetration testing or a formal security assessment.
  • Load, stress or performance testing.
  • Testing every API endpoint or all possible business rules.

Módszer

  1. Review the endpoint purpose and expected request structure.
  2. Use an API client or interactive API documentation to submit requests.
  3. Compare responses with expected behaviour.
  4. Verify persisted order data through the application and, where appropriate, read-only database queries.
  5. Record defects with reproducible steps and retest after a change.

Tesztforgatókönyvek és eredmények

  • API-01

    Valid authenticated request

    Megfelelt
    Lépések
    Submit a complete, valid order request with a permitted account.
    Elvárt eredmény
    The endpoint accepts the request and returns the documented success response and order reference.
    Eredmény
    Pass in this illustrative scenario.
  • API-02

    Request without authentication

    Hibás
    Lépések
    Submit an otherwise valid request without credentials.
    Elvárt eredmény
    The request is rejected; no order is created.
    Eredmény
    Failed. The unauthenticated request was accepted and an order could be inserted.
  • API-03

    Missing required field

    Megfelelt
    Lépések
    Omit a field defined as mandatory in the API contract.
    Elvárt eredmény
    The API returns a clear validation response; no incomplete order is created.
    Eredmény
    Pass in this illustrative scenario.
  • API-04

    Persisted data verification

    Megfelelt
    Lépések
    Retrieve the created order in the application and in the database, and verify the relevant stored fields.
    Elvárt eredmény
    Stored values match the submitted request and business rules.
    Eredmény
    Pass in this illustrative scenario.
  • API-05

    Authentication defect retest

    Megfelelt
    Lépések
    Repeat the unauthenticated request after the access-control change.
    Elvárt eredmény
    The request is rejected and no order is created.
    Eredmény
    Pass on retest.
  • API-06

    Full repeat after the fix

    Megfelelt
    Lépések
    Repeat API-01, API-03 and API-04 after the access-control change to confirm nothing else was affected.
    Elvárt eredmény
    All earlier results still hold.
    Eredmény
    Pass. The change was approved.

Illustrative request (generic data)

POST /api/orders
(no Authorization header)

{
  "customerId": "C-1042",
  "currency": "EUR",
  "lines": [
    { "sku": "SKU-001", "quantity": 2, "unitPrice": 19.90 }
  ]
}

Expected:  401 Unauthorized, no order created
Observed:  201 Created, order inserted   (defect API-F01)

Észrevételek

API-F01 · Súlyosság / hatás: High

Unauthorised order creation

The endpoint accepted a valid order-creation request without an authenticated session or valid credentials. This could allow unauthorised order creation.

Újratesztelés / követés: The access-control behaviour was corrected and the unauthenticated request was repeated. The request was then rejected, and the earlier scenarios were repeated successfully.

Összegzés

This demonstration combines functional API checks with access-control verification and data-persistence checks. It illustrates a defect loop: reproduce, document, verify the change and retest. It is not a full security audit.

Eszközök és technikák

Illustrative tools: Postman or Swagger UI for API requests; application-level verification; read-only SQL queries where database access is available.

Synthetic demonstration. Names, data and system details are generic. Outcomes are illustrative and are not a claim about a named customer or production system.

02

Webáruház–ERP integráció

Integrációs, adatszinkronizációs és kivételkezelési tesztelés

Egy webáruház és egy ERP közötti adatáramlás ellenőrzése: szinkronizálási irány, vevők, rendelésimport és hiányzó termék kivétele. A kivétel nem a specifikáció szerint került kezelésre.

  • 6 forgatókönyv
  • 4 Megfelelt
  • 1 Hibás
  • 1 Megfelelt kerülő megoldással
  • 1 észrevétel
Áttekintés / Terjedelem / Módszer

Áttekintés

A synthetic demonstration of validating data exchange between an e-commerce platform and an ERP system. It focuses on synchronisation direction, product and customer data, order import and handling missing product records.

A tesztelés célja

Verify that supported e-commerce data is transferred to the ERP as specified, synchronisation occurs only in the intended direction, and exceptions are handled in accordance with integration requirements.

Terjedelem

  • Product synchronisation from the e-commerce platform to the ERP.
  • Confirmation that ERP-side product changes do not trigger unsupported reverse updates.
  • Order import for an existing customer and a newly created customer.
  • Order handling when an order contains a product not yet available in the ERP.
  • Retry behaviour after the missing-product condition is addressed.

Nem része

  • Testing all features of the e-commerce platform or ERP.
  • Payment-provider, tax-calculation or shipping-carrier certification.
  • Performance, volume or resilience testing beyond the stated scenarios.

Módszer

  1. Confirm intended data-flow direction and expected mapping rules.
  2. Create and update controlled test records in the source system.
  3. Verify corresponding records and values in the ERP.
  4. Check that ERP actions do not create unintended reverse synchronisation.
  5. Create orders for existing and new customers, then verify imported order details.
  6. Introduce a missing-product condition and compare observed behaviour with the agreed exception rule.

Tesztforgatókönyvek és eredmények

  • INT-01

    New product synchronisation

    Megfelelt
    Lépések
    Create two products in the e-commerce platform.
    Elvárt eredmény
    Corresponding products are created in the ERP with the expected mapped information.
    Eredmény
    Pass in this illustrative scenario.
  • INT-02

    No reverse product synchronisation

    Megfelelt
    Lépések
    Create a counterpart product in the ERP, edit it and delete it, then check the e-commerce platform.
    Elvárt eredmény
    ERP-side changes and deletions do not trigger an update in the e-commerce platform.
    Eredmény
    Pass in this illustrative scenario.
  • INT-03

    Existing customer order

    Megfelelt
    Lépések
    Place an order using a customer already present in the ERP.
    Elvárt eredmény
    The order is imported and associated with the correct customer.
    Eredmény
    Pass in this illustrative scenario.
  • INT-04

    New customer order

    Megfelelt
    Lépések
    Place an order using a customer not yet present in the ERP.
    Elvárt eredmény
    The customer is created or matched according to integration rules, and the order is imported correctly.
    Eredmény
    Pass in this illustrative scenario.
  • INT-05

    Order with missing product

    Hibás
    Lépések
    Place an order containing a product that does not exist in the ERP.
    Elvárt eredmény
    The integration follows the specified exception rule, such as creating a designated placeholder product while retaining the original product description.
    Eredmény
    Failed. The expected placeholder was not created and the order remained pending.
  • INT-06

    Retry after prerequisite is addressed

    Megfelelt kerülő megoldással
    Lépések
    After the missing-product condition is addressed, retry the pending order.
    Elvárt eredmény
    The order is imported without duplication and retains correct customer, product and order information.
    Eredmény
    Pass after manually creating the required placeholder. This is a workaround, not evidence that automatic exception handling was fixed.

Észrevételek

INT-F01 · Súlyosság / hatás: Medium to high, depending on business context

Missing-product exception not handled as specified

When an order contained a product absent from the ERP, the expected placeholder-product handling did not occur and the order remained pending.

Újratesztelés / követés: A placeholder was created manually and the order was retried successfully. This showed a workaround and recovery path; it did not verify a permanent correction. Recommendation: create the placeholder product, or confirm the exception rule is implemented, before the integration goes live.

Összegzés

This demonstration covers integration behaviour across systems, including data-flow direction, customer handling, order import and exception recovery. It shows why testing must verify not only successful synchronisation but also behaviour when required data is missing.

Eszközök és technikák

Illustrative tools: e-commerce test environment, ERP test environment, integration logs and application-level data verification.

Synthetic demonstration. Platform and system references are generic. The missing-product behaviour and manual workaround are illustrative, not a claim about a named customer or production integration.

Írja meg, mit kell tesztelni.

Írja le a rendszert, mi változik, és mi a határidő. Kérdéseket vagy javasolt következő lépést kap.

Ajánlatot kérek