BEAM Test  Automated Testing for PeopleSoft Applications

SMALLsisyphus_charcoal_concept_sketch02.png

 

 

 

 

Why are you still testing PeopleSoft manually?

a.) It's fun!

b.) It's a habit.

c.) It's an efficient use of resources.

d.) It's very ad hoc.

e.) Haven't found a tool that helps.

Correct Answer: For most organizations, b or e.

 

Oracle Validated Application for PeopleSoft logoBeacon’s BEAM Test enables organizations to dramatically lower the cost, effort, and time needed for testing changes and updates to PeopleSoft applications. And with Selective Adoption in PeopleSoft 9.2, automating testing is easier, and more effective than in the past.

Easier, because their are no more application upgrades. Previously, upgrade scripts physically moved and converted application data, a complete change to the underlying data and data structures. These changes invalidated automated test scripts, requiring maintenance. And because each upgrade changed the data and data structures, it was "too hard" to automate testing scripts, as they would need to be maintained for each release.

Update Manager in 9.2 doesn't involve scripts or data structure changes. Each PeopleSoft Image adds a few features and fixes bugs, but doesn't otherwise change the data or the data structures. With BEAN Test, this means test scripts can be re-used, image after image, without maintenance. As you add new features you can add a couple of new test scripts, if you chose.

More effective, because while PeopleSoft applications and PeopleTools remain remarkably dynamic, based on the records and PeopleCode, the underlying 9.2 data structures have remained static. Not only does the value of automated tests increase because they no longer need maintenance (for each new release), but the automated tests are run much more frequently, as new images are released. 

 

Greater breadth and depth of testing is achieved through automating test scripts, and repeatable consistent testing, across environments, leads to more predicable release cycles of higher quality and reliability.

BEAM Test creates environment-independent test scripts, and has understanding of and integration with PeopleSoft metadata, which eases test script development and maintenance.

BEAM Test can be configured to work with a wide variety of external data sources. and running scripts in Business Process mode creates test and training documents.

In addition, BEAM Test can “load” transactions, into PeopleSoft environments, providing high-volume maintenance capabilities.

PeopleSoft Testing

PeopleSoft applications are constantly changing. These changes need to be tested to assure that the system still performs as expected. With manual testing, the introduction of these changes – new data, objects, and processes – require intense levels of effort and cost.


PeopleSoft Testing Challenges
  • Testing is often ad hoc, performed in selected environments, by various people, often manually
  • Testing is often as good as the tester (“It’s looks good to me”)
  • Data – whether configuration or transaction –  is often assumed to be correct (There is no verification process before testing)
  • Code changes from Oracle still need validation (bugs)
  • Process is not repeatable
  • Process has no measurements/metrics

 

BEAM Test is the only third-party testing tool for PeopleSoft that is an Oracle Validated application. It has three main features necessary for successful, scalable automated PeopleSoft testing.

  1. Integration with PeopleSoft metadata (eases script development and maintenance)
  2. Environment independence (Record once, play anywhere)
  3. Data source independence (Data external to script and environment)

A testing tool may store its scripts and data independently of your test environments, but not be integrated with PeopleTools, or it may be well integrated with PeopleSoft but require scripts and/or data to be migrated to the testing environment(s).

 

 

BEAM Test 

The BEAM Test product has four key parts, shown below. The left panel, the BEAM Test Suite Tree, displays environments, (called contexts), test scripts, and other testing assets. The center of the screen contains – at the top, a PeopleSoft environment, and below the code for a test script. On the right is the BEAM Test Data Sheet.

BEAM Test home page

  

The Test Suite Tree 

Each PeopleSoft environment is defined to BEAM Test (upper left in image). Note that there are two types of PeopleSoft connections available. Standard contexts use a PeopleSoft URL to connect to a PeopleSoft environment. Beam Test can also establish direct database connections. In this internal example, Beacon shows seven different environments defined to BEAM Test. A BEAM Test customer might show five or six FSCM environments, plus HCM and Campus environments.

The key message about environments is that when a context is made active, any recording or playback will then happen in that environment. A recording made in one environment (854) can be played back in another (Financials), with just a click.

BEAM Test PeopleSoft Environments