Audience

The following information is for anyone who...

• Is considering purchasing SecureTG (STG) or
• Has STG but were not involved in the initial STG setup process but need to get up to speed or
• Needs to make changes to their STG setup

Start by visiting our SecureTG web page to learn more, or contact us to schedule and online demo or support session.

FAQ

 

 

Q: Does SecureTG require a particular web browser in order to work?

A: No.  STG is its own special version of a web browser.  It does not matter which web browser you use--SecureTG does not require it.
What is required are the 3 files that make up SecureTG.  These file need to be copied onto any Windows computer, laptop or notebook that will be used by your test-taking audience to take an STG-enabled test.

Q: What happens if a test taker attempts to access / open a test that has been created to only run through a secure browser?

A: The test taker will not be able to take the test using the standard browser.  SecureTG-enforced tests, must be taken using STG.

Q: I now have two URLs for web Tester – the original one that was set up when TG Web was installed – and a new URL for tests delivered through a secure browser.  Do I need both?

A: That depends on how you deliver your tests.  If you plan on only delivering tests that enforce SecureTG, when the test taker opens SecureTG.exe, it will automatically present your web Tester URL within the SecureTG browser.  Some customers provide both secure and non-secure tests based on the testing audience and the type of test that is being published.  Where you direct your test takers will be driven by your testing policies and the types of testing you provide.

Q: If I need to change my SecureTG settings, will I need a new plug-in?

A: Yes, we will have to generate a new plug-in for you.  If you know which settings you want to use, you can email or call us.

Q: Can I enforce secure testing for a test and then change that setting later on?  Will it affect the test data that I collect from that test?

A: If you enforce secure testing for a test, and disable that property later on, your test won't be available through SecureTG.  Your test takers would have to open a regular browser--Chrome, IE, Firefox--enter your web Tester URL and log in to take the test. 

Q: Is SecureTG enabled all the time?

A: SecureTG can be enabled on an as-needed basis. How / when it is used subject to your testing policies.  If you don't wish to enable it, you can use the standard web browser to access your tests.  Note: non-SecureTG testing does allow the test taker full control of the desktop. 

Q: Can I change the test supervisor/proctor password?

A: Yes.  We would need to provide you with a new configuration file.  The easier option would be to enable a proctor login within a test’s security properties.  This feature is found under TG's Test Settings > Test Properties: Security tab > Security Parameters Dual Login feature.

Q: Does SecureTG need to be installed on every machine?

A: The SecureTG plug-in needs to be installed on any machine that will be used to access tests through a secure browser.  Deployment options will vary depending our your requirements and your organization’s testing policies.

Q: SecureTG is compatible with which operating systems?

A: SecureTG is compatible with Windows 7, 8, 10 and Mac OSX.

Q: Once I open SecureTG, can I have multiple test takers login and out ?

A: Yes. Once a test taker completes testing and returns to the login page, another test taker could log in and take another test.

Q: If the test taker experiences a problem while taking a test, and the proctor is not available, how do we proceed??

A: A "problem" encountered during a test-taking event is an interruption. Interruptions can be caused by a network failure, power outage, session time-out or computer crash.  In most cases, once an interruption is resolved, the test taker would be able log back in to the Tester and resume their test--"resume" meaning that they could pick up where they left off--any questions answered prior to the interruption are saved and their position in the test is bookmarked.

If the STG settings required a proctor login, the proctor would have to be present in order to allow the test taker back into the test.  There may also be other STG settings that would prevent the test taker from resuming their test without the assistance of a proctor or TG support.  These scenarios are addressed with customers during an online orientation session prior to the implementation of STG.

Q: Does the SecureTG installation install any system files or create any registry settings? 

A: SecureTG consists of a three files: a single executable, a .dll and configuration file. These files are copied onto the test-taking computer and placed in a directory chosen by IT or the test administrator.  All three files should remain in the same directory.  A shortcut to the executable file can be pinned to the Start menu or task bar.  When the executable is opened, it does modify various registry keys, which are then reset once the test event is over.  No permanent registry changes are made.

Q: Does SecureTG work on other operating systems?

A: SecureTG works on Windows and Macintosh computers, laptops or desktops. Tests that are not SecureTG enabled can be viewed on any device.

Q: If I am installing SecureTG in a TG LAN environment, do I need to have SecureTG files installed on each machine?

A: Yes. You can copy the three files onto a flash drive, or make a copy of the files and save them on the server. Next, on any machine containing a TG or Tester-client installation, place the SecureTG.ini, SecureTG.exe and SecureTGDLL.dll files in a directory of your choosing, for example, C:\Program Files\SecureTG.  Regardless which directory you use, make sure to keep the three files together. A shortcut to the executable file can be placed on the desktop or pinned to the Start menu or task bar. 

Q: I will be publishing both secure and non-SecureTG tests.  Can I use same shortcut to open both secure and non-secure tests?

A: No.  You should plan on creating a SecureTG shortcut for secure tests and a separate, web Tester browser bookmark for your non-secure tests.   Save both shortcuts in a location that is easily accessible to your test takers and make sure to indicate which shortcut to use.

Q: In TG, what are the test properties that need to be enabled in or for a test to be taken using STG?

A: In order to take an STG-enabled test, the test author must enable the Enforce Secure Testing checkbox setting located under a test's Test Properties > Security tab, "Security Parameters", highlighted in the example on the left. If this property is not enabled the test won't be available in STG.  We always recommend previewing the test before publishing it. 

Also, the test admin should review our Guide to SecureTG Performance and Windows 10 Updates to make sure all of the testing machines have a Windows versions and build that is compatible with their version of STG.