SHM Setting

Users with admin role can access the Setting dashboard to configure SHM server.

• Change some key config attributes of Handow engine.
• Set SHM server auto-run mode
• Maintain users list

Handow configuration

These config items have global scope and override same fields in project config.js, and they are overridden by relevant config attributes of the plan in run time. The SHM server needn't restart if the config items were changed from the Setting dashboard. It is convenience for SHM administrator reconfig Handow engine in run time.

Schedule and control

SHM server provides 3 running modes, SHM administrators can choose one for test automation. The new running mode is valid immediately after the current testing finished if test engine is not idle. The handow-seed project doesn't choose any running mode, so the SHM derver works in manual-run mode by default.

• Infinite Looping - Admin user can specify a group of plans and make SHM server run them over and over until the auto-run mode is changed. As a matter of fact, SHM seldom run test like this except you want to verify the repeating behavior of some features in the target application.
• Timeer schedule - Admin users can setup daily timers, each timer can sart running specific group of plans. That's the easiest way for test automation.
• Http request trigger - Admin users can set the SHM server keep listening on POST /api/shm/run. This request should specify plans and it will trigger SHM run these plans sequentially in one cycle. A secrete header is reuired to make this trigger request secured. This mode is useful when the applications have a pipeline dominating the build and deployment, so the SHM could be integrated into the pipeline easier.
• (manual run) - SHM is cotroled manually if no auto-run mode selected. Admin users can open any signle plan or story in Runner and run it with the Run button.

User management

The SHM server implememt simple access control basing on the SHM security level and user roles. The admin user can register new users and assign admin or user roles to them.

SHM security level vs roles

SHM server can start with specific security level: public, secure or private. The default mode of handow-seed is public for local running.

• public mode - Visitors are assigned admin role automatically, no sign-in required.
• secure mode - Visitors are assigned user role automatically, the admin users need to sign in to access protected resources and operations.
• private mode - Visitors cannot access SHM server unless sign in as admin or user

The admin users can access all features of SHM server, but users are denied to access SHM setting and "Read-Only" for testing resources.

The shmSetting.json file

Handow and SHM server depend on file system. The shmSetting.json is the repository file for the SHM setting. You can refactor this file before deploy SHM server to change the default seeting.