Skip to content
English
  • There are no suggestions because the search field is empty.

Appendix A - Open Items for Verification

Items that require confirmation from the development or product team. Rules marked “To be verified by QA” elsewhere in the manual were carried over from documentation of an earlier version and should be re-tested on the current build.

#

Information needed

Source

Priority

1

Screens listed as remaining gaps in section 5.15

Test environment

High

1e

Invoice quantity entry: cumulative or per-invoice. Evidence now strongly favours cumulative; needs formal sign-off

Development team

CRITICAL

1j

Whether an invoice finalised in error can be corrected, given GoBD immutability

Development team

High

1h

Order of operations in the payment calculation — retention base

Development team

High

1i

Ticket approval: who may approve, and whether approval can be reversed after use

Product owner

High

1c

Populated BoQ screenshot; Actions menu; OZ schema; Finalize behaviour

Test environment

High

1d

GAEB/Excel import: accepted versions, validation failures, append vs replace

Development team

High

1b

QA re-test of the trade edit/delete/finalise rules in section 5.6.7

QA

High

2

How organisation roles and permission presets interact

Development team

High

3

Remainder of the permissions list below "Members", incl. Payments and Companies

Test environment

High

3b

Verified formulas for Cost tracking computed columns

Development team

High

3c

Project settings: Sync tab and Danger Zone contents

Test environment

High

4

CAPMO sync scope, direction, frequency, and error handling

Development team

High

5

Production URL and login procedure

Internal

High

6

Recapture screenshots without test data or test URL

Test or staging environment

High

7

Row Actions menu contents for every list screen

Test environment

Medium

8

Field validation rules (lengths, formats, date ordering)

QA / development

Medium

9

What the Companies Source column indicates

Development team

Medium

10

Whether Add connector is available to administrators

Development team

Medium

11

Confirm optional Postal code vs mandatory City is intended

Product owner

Low

12

Known issues, support process, escalation contacts

Support / internal

High