testPoint

Beginner Intermediate Expert

General Menu Test

1. Drive the test via mouse

The test process can be driven only via keyboard, just use the commands in the list below:
  • Show the info layer.
    There is no a mouse command to show the info layer. Just tuneup a property or move to next test step.
    if the info layer is disabled (duration slider is set to "Do not show test information") nothing will be shown.
  • Open the dashboard.
    R-click inside the test window.
    To close the dashboard just R-click somewhere indside the test window again.
  • Tuneup the default test property.
    Scroll the mouse wheel. If there is a default test property its value will be changed.
  • Tuneup alternative test properties.
    Hold ⇧, ⌃ or ⌘ while scrolling the mouse wheel. If there are alternative test properties their values will be changed.
  • Go to next step.
    Click inside the test window.
    Hold ⇧ while clicking will step backward.
    The test will close itself when step forward from the last test step, or step backward from the first test step. If you prefer to step in cycle just hold ⌥ while clicking.
  • Close the test.
    The test will close itself when step forward from the last test step, or step backward from the first test step.
    This will not work if the "Step in cycle" checkbox is selected. In this case, use Esc key or the dashboard.
Working via mouse is very convenient and fast method when you drive multiple tests simultaneously.

2. testPoint & myPoint Shade

Test window can be positioned below or above the shade layer (and other gadgets from myPoint family). Below are some prescriptions how to use this option:
  • Deselect the "Below shade layer" checkbox when you test a monitor.
    In this case, the monitor is a part separated from your working environment. Because of this, nothing (like shade) should change the colors of the test template.
  • Select the "Below shade layer" checkbox when you tuneup your working environment.
    In this case, you should consider the shade value. For example, run the Brightness & contrast test ant tuneup the shade value until you get the best view.

3. Info layer visibility duration

The info layer is very valuable for newbies. We recommend a value of 2 seconds to be set until you get familiar with tests.
Later you can decrease the value to 0.5 seconds.
Sometimes you will find it convenient to disable the info layer. In such a case, just drag the "Show test information..." slider to its rightmost value. Now it will show the "Do not show test information" label.
There is a copy of this option in the dashboard:

4. Change screen indices

Open the test settings panel:
  1. Tuneup the indices' behavior.
  2. Beware of the "Show for..." slider value.
    In a case of "Show for infinite" value, there are two ways to hide indices:
    • Move the "Show for..." slider to a finite value.
    • Deselect the "Show screen indices" checkbox in the test center.
Usability notes:
  • Avoid the "Show for infinite" value for general use.
  • Use only translucent colors for the background, especially when "Show for infinite" value is set.

5. Run a test automatically when new screen is attached to the computer

This feature is convenient when a lot of screen attachments are processed.
  1. Open the test settings panel and choose the preferred test.
    Usually this will be a custom group.
  2. Beware to set the appropriate video wall settings.

6. About color spaces

In common cases apps are using calibrated color space. However, this should not be a limitation to devs and researchers. Open the test settings panel and choose the preferred color space.
General rules to determine the test's color space:
  • gray-scale tests are using the Gray color space.
  • Colored tests are using RGB color space.
  • Tests with "HL" in their names are using the HSL/HSB color space.
Preview the Tests section of this website to get the right color space for each test.
Note:
HSL is simulated via RGB. The algorithm is well defined and there should not be a doubt about the output value. However, there are some popular implementations and optimizations. We've collected and preset them in variants: A, B, C... Some of algorithms are skipped because they are producing very incorect output values. If you are using your own code to conver HSL to RGB and you are ready to share it, please drop us a line - we will include it as a new variant.
© 2012-2024 CODERACE
Apple, the Apple logo, App Store, Mac, Mac OS X and macOS are trademarks of Apple Inc.