Test strategy and test concept
- Test levels and their scope: unit, integration, system, acceptance
- Coverage map against the requirements
- Exit criteria and release gates
- Test data and test environment concept
- Tooling and process fitted to your team
Software Quality Assurance — software that is always ready for delivery.
We provide independent, end-to-end quality control of software: it minimises the risks at acceptance and the surfacing of defects in late phases and in the field — and keeps the collaboration between client and developers calm and constructive.
For embedded software, cloud, AI and business applications.
Working with us is easy and pleasant.Get in touch any time!
SQA 01
-
What is tested, at which level and with what: the test concept, a coverage map against the requirements, the exit criteria.
Strategy and coverage
-
Unit, API and end-to-end tests that run in the pipeline and need no manual pass.
Test automation
-
Acceptance runs, a readiness report, and go or no-go decisions based on reliable numbers.
Release readiness
SQA 02
When we are called in:
Does this sound familiar? Let’s talk.- Defects surface at the customer, not in the tests
- The release is postponed “by one more week” again
- There are tests, but nobody trusts a green run
- Acceptance turns into an argument
- There is no independent party between client and contractor
- The regression grows with every sprint
- QA is needed for embedded or automotive software, HIL included
- An audit or a certification needs a test base that can be proven
SQA 03
Running the tests says what was checked. Quality says whether the product fulfils expectations.
You know: Tests≠quality
- Requirements traced to tests
- Risk-based choice of what to test
- Negative and edge cases
- Non-functional requirements: load, security, usability
- Test data, mocks, simulations
SQA 04
A green pipeline means the software is built, not that it works.
You know: Green≠done
- Coverage by requirement, not by line
- Exit criteria agreed before the run
- Smoke tests on the production system
- Known defects listed, not hidden
- A readiness report per build
SQA 05
The developer checks what they built. QA checks how it is used.
You know: Independence≠distrust
- A separate role with its own mandate
- Own access to the requirements and the backlog
- One report, to the client and the team at once
- Findings as facts, not as blame
- Defects triaged together
SQA 06
Acceptance is where client and developer usually clash. With agreed acceptance criteria it becomes a formality.
You know: Acceptance≠handover
- An acceptance protocol agreed up front
- Defects classified by severity
- A date in the calendar, not “when it is fixed”
- Acceptance runs on the client’s own data
- Warranty cases told apart from change requests
SQA 07
How we work
Six steps, from the first look at what is there to the release and beyond.
- 01
Check-up
What is tested today, how, and what a green run actually proves.
- 02
Strategy and coverage map
Test levels, tooling, exit criteria — and every requirement mapped to the test that covers it.
- 03
Automation in the pipeline
Unit, API and end-to-end suites wired into CI, so every commit is checked without anyone being asked.
- 04
Runs, defects, reports
Test runs per sprint, defects tracked with severity and owner, one report for everyone.
- 05
Release gate
Go or no-go on the exit criteria — and the numbers behind the decision.
- 06
After the release
Smoke tests in production, field defects fed back into the suites, the coverage map kept current.
SQA 08
A selection of what we do
in software quality assurance
Test automation: unit and end-to-end
- End-to-end suites with Playwright
- Unit test coverage where it pays off
- Integration into your CI/CD pipeline
- Stable, maintainable suites rather than flaky ones
- Reports the team reads and trusts
API and integration tests
- REST and SOAP interfaces with Postman and SOAP UI
- Contract tests between services
- Data-driven test sets
- Interfaces to ERP, CRM and e-commerce systems
- Automated regression of the interfaces
System and acceptance tests, automotive included
- Acceptance runs on the client’s own criteria
- HIL and ECU tests with EXAM
- Requirements-based test cases per Automotive SPICE
- Traceability from requirement to result
- Acceptance protocols the auditor accepts
Release readiness and reporting
- Readiness report per release
- Defect statistics by severity and age
- Coverage and trend metrics per sprint
- Go or no-go on agreed criteria
- Support after the release
SQA 09
What you get
- 01
Clear plan
Levels, tooling, criteria and responsibilities in one document.
- 02
Coverage map
Every requirement and the test that covers it — and the ones nothing covers yet.
- 03
Automated suites
Unit, API and end-to-end tests in your repository, running in your pipeline.
- 04
Defect reports
Reproducible, classified by severity, with an owner and a date.
- 05
Readiness report
The state of a release against its exit criteria, before the decision is made.
- 06
Metrics per sprint
Coverage, defect trend and test stability, sprint by sprint.
// Everything stays with you: the test code, the reports, the pipeline.
SQA 10
Industries we are strong in
- Automotive
- Energy
- Compliance
- IT-Security
- Healthcare
- Logistics
- Education
SQA 11
The standards and practices the work is done to
- ISTQB
- ISO/IEC 25010 — Software Quality Model
- ISO/IEC/IEEE 29119 — Software Testing
- Automotive SPICE — SWE.4 to SWE.6
- CRA — Cyber Resilience Act
- ISO 21434 — Automotive Cybersecurity
- OWASP ASVS
- MISRA
- GDPR
- Industry- and customer-specific test regulations
SQA 12
Frequently asked questions
What is the difference between SQA and simply hiring testers?
Testers execute tests. Software Quality Assurance decides what has to be tested, at which level and to which criteria — and whether the result is good enough to release. We do both, but the second part is the one that changes outcomes.
Do you need access to our source code?
For unit tests and for automation in the pipeline, yes. For system, acceptance and API tests, access to the running system and its interfaces is enough. We agree the scope of access up front and work under your NDA.
Do you work with our team or on your own?
Both, and usually at the same time: we set up the strategy and the automation together with your developers, and keep the independent role of checking what was needed. The report goes to the client and the team at once.
How soon is the first report on the table?
The audit of what is there takes one to two weeks. It ends in a written picture of the current test base, its gaps and the first steps — that is the first report.
What if Ciqualia also writes the software?
Then QA is a separate team with its own mandate and its own report to you. Independence is a role, not a company: whoever writes the code does not decide whether it is released.
How do you measure coverage?
By requirement, not by line of code: which requirements have a test, which have a passing one, and which have none. Line coverage is one input to that picture, not the picture.
Which industries do you work in?
We work in the automotive industry, in e-mobility and smart home production, in energy, media, education, health, marketing, compliance, the public sector and transportation, among others, as well as in other data-intensive fields.
Which concrete solutions have you delivered recently?
Our current projects include market analysis, knowledge bases for technical documentation, AI-supported compliance, customer service portals, reverse engineering of legacy systems, log analysis and structuring of unstructured data.
What advantages do your solutions offer?
Our solutions combine modern AI techniques, robust software development, optimised data structures, strong security, cloud and on-premise flexibility as well as capable and stable operating models.
How do you ensure security and compliance?
We take data protection, security standards, organisational requirements and regulatory obligations into account from the start – from the architecture through to operations.
How can I discuss a project or an idea with you?
Through the contact form on this website or directly by message. We answer quickly and are glad to talk about your requirements and the solutions that are possible.
SQA 13
Working with us is easy and pleasant!
Ask us – we answer quickly.
✓Price list on request — we send it over
✓An offer within 24 hours
✓Migration of your data free of charge
✓Integration of your applications free of charge — tell us which ones
Thank you.
We will get back to you within one business day.
Not sent.
That did not work. Please check the fields or email us directly.