Skip to content
Automated Testing

Test Automation with RPA

Test scenarios recorded on your current system run automatically on the migrated system.
We treat how your current system behaves today as the right answer, and check that the migrated system behaves the same way.

01

Record scenarios on the current system

Operate the current system with our RPA tool and record the steps as test scenarios. Screenshots of each screen are captured as well.

02

Run them on the migrated system

The recorded scenarios run automatically on the migrated system. The same tests can be repeated after every fix.

03

Compare screens to find differences

Screenshots from before and after migration are compared and differences detected automatically. Testers review only the screens that differ.

Challenges

Common challenges in migration testing

Migration testing must confirm the new system works the same as the current one — and doing this by hand is a heavy burden.

Writing test cases takes a lot of effort

Steps and expected results must be written for every screen. If specifications are outdated or missing, you first have to rediscover how the current system behaves.

Every fix means testing again

After each defect fix, the affected screens must be checked again. Done by hand, the effort grows with every round.

Visual checks miss things

When people compare screens before and after migration by eye, small differences in display or values can be missed.

Quality varies from tester to tester

How far to check and what counts as a difference vary by person, making results hard to keep consistent.

How it works

How automated testing works

Scenarios and screenshots recorded on the current system are automatically matched against the results from the migrated system.

Current system STEP 1 Record operationsOperate with RPA → scenario Capture screensScreenshots Migrated system STEP 2 Run the scenarioRPA replays the same steps Capture screensScreenshots Same scenario STEP 3 Compare before & after Match screens step by stepDetect differences automaticallyList screens with differences
STEP 1

STEP 1 Operating the current system creates the test cases

Instead of writing test cases, you record them by operating the current system.

What our RPA tool records

StepsThe order of opening screens, entering fields, clicking buttons and so on
Values enteredSearch conditions and data used in the test
ScreenshotsThe state of the screen after each step — the “right answer” for comparison

Why this approach works

  • Current behaviour becomes the expected result
    Even where specifications are outdated or missing, today’s behaviour serves as the right answer.
  • Uses the knowledge of business users
    The operations people perform every day become scenarios as they are.
  • Create once, use many times
    Recorded scenarios can be reused throughout testing of the migrated system.
STEP 2

STEP 2 Run the same scenario on the migrated system

The scenarios recorded in STEP 1 are replayed on the migrated system without manual work.

Runs nights and weekends

Tests can run in batches at set times with no one present.

Automated regression tests

After a fix, rerun the same scenarios to check for side effects on other screens.

The same steps every time

No variation between people — every run uses the same conditions.

STEP 3

STEP 3 Compare screenshots to find differences

Screens at the same step are compared before and after migration, and differences are found automatically.

Before (current system) Order entry Order no. A-10025 Customer Acme Trading Quantity 16 Total 12,800 Migrated system Order entry Order no. A-10025 Customer Acme Trading Quantity 16 Total 12,000 VS ! Difference found: "Total" on the Order entry screen differs (12,800 → 12,000)

What comparison reveals

Different values

Calculated or displayed values differ

Different display

Missing fields or different messages

Different screen flow

The same step leads to another screen

Testers only need to review the screens where differences were found. (The screen and values are a fictitious example.)

Benefits

Benefits for you

Confirm migration quality while keeping the testing burden low.

01

Less effort to create test cases

Simply operating the current system produces both scenarios and expected results.

02

Objective proof of “same as today”

Screenshot comparison shows differences before and after migration, screen by screen.

03

After every fix, retest with confidence

The same scenarios repeat automatically, so the impact of fixes is checked too.

04

Fewer oversights, consistent results

Automated comparison reduces missed differences and variation between testers.

Getting started

How to get started

Start with a few screens, confirm the benefit, then widen the scope.

Choose target screens

Start with business-critical or frequently used screens.

Record on the current system

Record operations with our RPA tool together with people who know the business.

Trial (PoC)

Run and compare on the migrated system to confirm the benefit and the operation.

Roll out

Widen the scope and build it into migration and regression testing.

Related services

Contact

Try automated testing on your most important screens

Tell us about the system and the number of screens, and we will propose how to run a PoC.

TEL +81-3-5962-3776