Operations teams re-running regression checks on every maintenance release
The flows that must pass before release are automated first; the rest move to nightly or scheduled runs to cut checking time.
Public-sector test automation
A public-sector test automation service that covers web, mobile, and API regression checks through to run logs and reports.
- Public agencies · public SI
- Web · mobile · API
- CI/CD integration
- Qoretix
01Overview
Regression checks for public projects, as automated tests and run records
Public-sector test automation is an IXC service that turns regression checks on public web, mobile, and API systems into automated tests run on every release.
Tools are chosen to fit each agency’s system and security policy, starting with open-source options such as Playwright, Selenium, and Appium. Run logs and reports are kept in Qoretix, the platform IXC builds, or in a tool the agency specifies, and scripts and run instructions are handed over as deliverables for acceptance and maintenance.
IXC is the brand of 아이엑스씨㈜ (IXC Corp.) in Korea; 코어틱스 is the Korean name for Qoretix.
02When it fits
Agencies and contractors it suits
Public systems ship frequent maintenance releases and must keep test results on record. Automation reduces both burdens at once.
Contractors preparing test deliverables for public SI projects
Scenarios, run results, and defect actions are kept in one format so they can go straight into acceptance documents.
Agencies preparing a cloud migration
The same regression scenarios run before and after the move to compare behaviour, and pair with performance tests to evidence the cut-over decision.
03Scope
Six things public-system regression testing needs
Scope and tools are agreed with the agency at kickoff. Automation starts with the flows that pay off most and widens from there.
The same business flow is checked automatically in web browsers and mobile apps — Playwright and Selenium for the web, Appium for mobile apps — against a browser and device list agreed at kickoff.
Requests, responses, permissions, and error handling of business APIs are verified ahead of UI tests. Checks that survive UI changes grow, and regression time falls.
Tests connect to the CI tool the agency and contractor already use — Jenkins, GitLab CI, or GitHub Actions — and run before every release against pass criteria agreed up front.
Each run keeps screenshots, session recordings, and logs together, and failures are labelled as product defects, environment problems, or stale scripts, so results need no re-interpretation.
The same scenarios run before and after moving from on-premises to the cloud. Paired with performance and load tests, they show response-time changes after the move.
Scripts, test-data set-up, and run instructions are handed over, with failure-review cadence and fix ownership agreed. Only what in-house staff cannot cover stays under a maintenance contract.
04Qoretix
Run records and reports are kept in Qoretix
Qoretix (코어틱스) is IXC’s software platform that connects QA automation, security checks, and operations monitoring in one project flow.
Case preparation
Draft test plans and cases are generated from requirements, screens, and repository code, then reviewed and approved by the team.
Runs and evidence
Approved cases run against APIs and real browsers, keeping screenshots, recordings, and logs for every failed step.
Unverified scope
Reports separate what passed from what has not been checked yet, so tests that never ran do not look like passes.
Fixes and re-verification
Issues link to Jira and to re-verification records, with code, secret, and dependency security findings in the same project.
How Qoretix is used and which data it connects to are confirmed against the agency’s security policy during onboarding. Work can also run on the agency’s own tools without Qoretix.
05Approaches
Four ways to adopt test automation
Public agencies adopt test automation in four main ways. In-house staffing, the run environment, and security policy decide which fits.
| Approach | Examples | Fits when | Check |
|---|---|---|---|
| Build on open-source tools | Selenium, Playwright, Appium, Postman · Newman | In-house developers or QA staff can maintain the scripts | The agency must provide the run environment, reporting, and maintenance staff itself. |
| Commercial all-in-one test tools | Katalon, Tricentis Tosca, OpenText Functional Testing | Web, mobile, and API tests should live in one tool | Licence cost, installability on internal networks, and local support coverage. |
| Cloud device and browser services | BrowserStack, Sauce Labs | Many real devices and browsers must be covered | Confirm first that the security policy allows access to an external cloud. |
| Specialist test automation service | IXC test automation + Qoretix (코어틱스) | Someone should own scenario design, build, runs, and maintenance | Agree deliverable ownership, handover scope, and maintenance terms in writing before kickoff. |
The approaches can be combined. IXC builds scenarios, run environments, and reporting on open-source tools, and adapts to any commercial tool the agency already uses.
06How to choose
Five steps to choose a public-sector test automation service
Settle the run environment and deliverables before comparing tool names.
- 01
Settle the run environment
Confirm where tests will run — internal network, segregated network, or cloud — and what external access is allowed.
- 02
Split scope by layer
Decide what to check in the web UI, the mobile app, and the API. Push each check down to the fastest layer that can make it.
- 03
Match the deliverable format
Check that run logs, screen evidence, and reports fit the acceptance-document format and that unverified scope is shown separately.
- 04
Fix the pipeline and the owner
Decide which CI runs the tests and when, who reviews failures, and who fixes the scripts.
- 05
Check contract requirements
For procurement reserved for SMEs, check direct production confirmation; for public software projects, check software business registration.
07Credentials
IXC holds the credentials Korean public contracts require
In Korea, information system development and maintenance services reserved for competition among SMEs can only be bid on by firms holding direct production confirmation. IXC is confirmed for the items below.
- Direct production confirmation
- KODMA · Oct 12, 2026 – Oct 11, 2028 · information system development, information system maintenance, package software development and implementation, outsourced operations, internet support development services
- Registered software business
- Korea AI and Software Industry Association
- Venture enterprise confirmation
- Venture Enterprise Confirmation Institution · Innovative Growth category · Oct 7, 2026 – Oct 6, 2029
- Accredited corporate research institute
- Korea Industrial Technology Association (KOITA)
- Registered AI and digital transformation supplier
- Gangwon Technopark
- Head office
- Chuncheon ICT Venture Center, Chuncheon, Gangwon
08FAQ
Questions agencies ask before starting
It turns regression checks on public web, mobile, and API systems into automated tests that run on every release and keep logs and reports. IXC covers tool selection, build, pipeline integration, and handover.
The tools may be the same; what differs is who owns scenario design, the run environment, reporting, and maintenance. IXC builds those on tools such as Playwright, Selenium, and Appium and hands them over.
Each run keeps screenshots, recordings, and logs, and reports separate passed items from unverified scope. Issues found are linked to Jira and to re-verification records.
Yes. Results can be kept in the agency’s reporting tool or CI results page. 코어틱스 (Qoretix) is added when run records and re-verification history should sit in one place.
IXC holds direct production confirmation for five items, including information system development, and is a registered software business. Technology is led by CTO Shin Minkyu, in product development and QA since 2016.
Public projects
Start with the system and the run environment
Tell us which system to verify, how often it ships, and the security policy, and we will propose the automation scope and approach.