Security and data privacy for on-premise test automation
Q-Guard turns the journeys real users take through your web application into automated tests, without keeping what they type.
- Installed on-premise, on your own servers
- User input anonymised at the source, before storage
- Only user journeys are kept
- No sensitive data stored on Q-Leap’s side
How does Q-Guard protect your data?
Q-Guard keeps the path users take through your application, not the values they enter. User input is removed in the data collector before anything is stored, and what remains is stored on your own servers.
At the source
- Your usersuse your web application, in production or in a test environment.
- Data collectorrecords each visit as a session: the sequence of actions a user performs.
- Anonymisationthe collector drops every value users type, before anything is stored.
On your servers
- User journeysthe anonymised sequences of actions are stored on your servers.
- Test casesQ-Guard detects repeated journeys and generates test cases and Selenium scripts from them.
Steps 4 and 5 run on your own servers, where Q-Guard is installed. The full product workflow is described in how Q-Guard generates test cases from real user journeys.
What data does Q-Guard capture?
Q-Guard captures sequences of user actions, called sessions. It does not keep the values users type, and everything it stores stays on your servers.
| Data | Recorded | Kept | Stored on |
|---|---|---|---|
| Sequences of user actions (sessions) | Yes | Yes, as anonymised user journeys | Your servers |
| Values users type (user input) | No, dropped by the data collector | No | Not stored |
| Usage patterns (sequences of action types) | Derived from user journeys | Yes | Your servers |
| Test cases and Selenium scripts | Generated by Q-Guard | Yes | Your servers |
| Test reports and dashboard | Generated by Q-Guard | Yes | Your servers |
A session is the sequence of actions a user performs during a single visit; a pattern is a sequence of action types used to model a usage and create a test case. More definitions are in the Q-Guard FAQ.
How does Q-Guard anonymise user input?
In the data collector, at the moment of capture: each value a user types during a session is dropped before anything is stored, and only the user journey is retained.
- What is removed
- Every user input from the session: the values users type into your application.
- When
- Upstream, before any data is stored.
- Where
- In the Q-Guard data collector, at the source.
- What is kept
- The user journey: the sequence of actions, which Q-Guard uses to detect repeated usage and generate test cases.
Where is Q-Guard data stored?
On your own servers. Q-Guard is currently available only as an on-premise installation, so the user journeys, test cases and reports it produces are stored on infrastructure you operate.
Does Q-Leap store my application or user data?
No sensitive data is stored on Q-Leap’s side: the data Q-Guard collects stays on your servers. A hosted SaaS version is planned; until it is available, on-premise is the only deployment model. See Q-Guard licence and deployment options.
How does Q-Guard support GDPR and data minimisation?
Q-Guard is designed with GDPR requirements in mind. It does not make your processing compliant on its own; it reduces the personal data involved in test automation through four mechanisms.
- Data minimisation. Only the sequence of actions is kept; the values users type are not.
- Anonymisation at the source. User input is removed in the data collector, before storage.
- Storage location. Q-Guard data is stored on your own servers, not by Q-Leap.
- Customer-controlled infrastructure. Q-Guard data sits on infrastructure you operate, under the access, backup and retention rules you already apply to it.
Your data protection officer can review this data flow with the Q-Leap team during a demo.
Does Q-Guard affect application performance?
Q-Guard is designed to observe how users move through your application without affecting the performance of your application or infrastructure.
Because Q-Guard runs on your own servers, you can check its footprint in your own environment: the trial lets your team test Q-Guard on its own application before subscribing.
How is Q-Guard deployed and installed?
On-premise, by the Q-Leap team. Q-Guard is sold as an annual licence installed on your own infrastructure; installation is included in the licence and typically takes less than one day.
- Demo. See Q-Guard and discuss your environment and security requirements.
- Trial. Test Q-Guard on your own application before subscribing.
- Installation. The Q-Leap team installs Q-Guard in your environment, included in the yearly licence.
- Support. Documentation and ongoing technical support are included in the licence.
Pricing depends on your environment and is shared on request: see what the Q-Guard licence includes.
Security and privacy FAQ
What data does Q-Guard collect?
Q-Guard collects the sequences of actions users perform in your web application, called sessions. It does not keep the values users type: its data collector drops them before storage and keeps only the user journey.
Does Q-Guard record what users type?
No. Each value a user types during a session is dropped by the Q-Guard data collector before anything is stored. Q-Guard keeps the sequence of actions, not the content of the inputs.
Where is Q-Guard data stored?
On your own servers. Q-Guard is currently available only as an on-premise installation, so user journeys, test cases and reports are stored on infrastructure you operate.
Does Q-Guard send data to Q-Leap?
Q-Guard stores its data on your servers, and no sensitive data is stored on Q-Leap’s side. If your security policy requires the list of network connections of your installation, ask the Q-Leap team during a demo.
Can Q-Guard run on-premise only?
Yes. Q-Guard is installed on your own infrastructure, and on-premise is currently its only deployment model. A hosted SaaS version is planned. If your installation must run without internet access, raise it with the Q-Leap team during a demo.
Is Q-Guard designed for GDPR requirements?
Yes. Q-Guard is designed with GDPR requirements in mind: it minimises the data it keeps, anonymises user input at the source and stores its data on your own servers. Assessing the compliance of your processing remains the responsibility of your organisation.
Does Q-Guard slow down my application?
Q-Guard is designed to capture user journeys without affecting the performance of your application or infrastructure. You can check this on your own application during a trial, before subscribing.
How long does a Q-Guard installation take?
The Q-Leap team installs Q-Guard in your environment. Installation is included in the yearly licence and typically takes less than one day.
Questions about licensing, support or test reports are answered in the Q-Guard support FAQ.