NAVICORE ONE company operating system · Part 43 · Developers & extensions
Testing
Understand the areas NAVICORE ONE is planned to be tested in: logic, security and full flows.
What this page describes is the intended scope from the product specification. The status label shows how far along this area is.
Illustrative layout, not a live screenshot.
What it is
Four kinds of testing are specified: unit (business logic, permission logic, validation, financial calculations), integration (API, database, authentication, authorization, notifications), security (tenant isolation, RBAC, privilege escalation, unauthorized access, session security) and end-to-end flows.
The problem
A business system that handles pay, approvals and company data cannot rely on hoping it works.
What NAVICORE ONE does
NAVICORE ONE specifies tests for business logic, permissions and money calculations, for the systems it connects, for tenant isolation and privilege escalation, and for whole user journeys.
The result
The riskiest parts are the most carefully checked.
Who uses it, and when
- The NAVICORE engineering team
- Whenever a module changes
- Technical reviewers
- When asking how quality and security are checked
How it works, step by step
Layers of testing
Sequence assembled from this part's listed functions, in plain language.- 1
Unit
Business logic, permissions, validation, financial calculations
- 2
Integration
API, database, authentication, authorization, notifications
- 3
Security
Tenant isolation, RBAC, privilege escalation, unauthorized access, sessions
- 4
End to end
Registration through chat, with demo and organization isolation
Key functions
Unit tests
Business logic, permission logic, validation and financial calculations.
Integration tests
API, database, authentication, authorization and notifications.
Security tests
Tenant isolation, RBAC, privilege escalation, unauthorized access and session security.
End-to-end flows
Registration, domain verification, invitation, HR approval, onboarding, leave, task, finance, approval and chat.
Isolation checks
Demo isolation and organization isolation.
Full scope from the product specification (26 items)
Unit
- Business logic
- Permission logic
- Validation
- Financial calculations
Integration
- API
- Database
- Authentication
- Authorization
- Notifications
Security
- Tenant isolation
- RBAC
- Privilege escalation
- Unauthorized access
- Session security
E2E
- Registration
- Domain verification
- Invitation
- HR approval
- Employee onboarding
- Leave
- Task
- Finance
- Approval
- Chat
- Demo isolation
- Organization isolation
How it connects to other parts
- Part 05In build
Roles & permissions
Decide exactly who can see and do what, down to a department, team or single project.
- Part 02Live
Companies & workspaces
Give each company its own isolated workspace, set up the way that company actually runs.
- Part 07Planned
HR & employee lifecycle
Hire, change and offboard employees through one approved, recorded flow.
- Part 01Live
Public website & demo
Understand NAVICORE ONE and ask for a demo before you commit to anything.
- Part 37In build
Security center
Watch sign-ins, devices, permission changes and alerts for the whole company in one place.
See it in action
Ask for a demo, or tell us how you would like to partner.