GemX Software
GEMX SOFTWARE
 
GemX Software

Producer and distributor of Information management software applications.

 

Don't touch my do-Organizer

You cannot touch my doO. Go get your own one.

Beta Testing

We appreciate your help in testing GemX software applications. Robust beta testing periods for all GemX applications is an integral part of our quality control procedure. You can be part of it too.

Beta testing

 

How can I become a GemX Software beta tester?

It’s simple. You don’t need any special qualifications. If you are using and like GemX software applications you are already an ideal candidate

For a start, send an email to GemX Support indicating your wish to become a Beta Tester for GemX Software application/s. Please include in your email:
- Specifications of your computer that you’d be using for beta testing ( Operating system, memory, display, connected devices, etc )
- GemX application name you wish to beta test
- And any other comments you may have

After receipt of your email, your details will automatically be added to our “Prospective Beta Testers” database. Until we start receiving quality feedback and reports, your details will stay in “Prospective Beta Testers” database for up to 6 months. Non-activity after 6 months will result in your details deletion. On the other hand, once we receive a few quality feedback reports, you’ll become an approved GemX beta tester for your chosen application.

If and when you become an approved beta tester, we will send you download links as soon as beta applications become available according to our development schedule

After sending your “Beta tester email application” you don’t need to contact us. Just download any of GemX Software applications and start testing it and send your findings to: gemxsupport@gmail.com Your findings may be suggestions, corrections as well as bugs. Before you start, be sure to read GemX Beta Testers Guidelines at the bottom half of this page.

Please use a valid email address - preferably a long term one. The email address you use will also be your beta tester ID as well as your contact address. You must use the same email address when communicating with us. If you change your email address, please let us know in advance. In view of our GemX privacy policy, your email address will not be used for any form of spam or passed on to other parties.

 

General Guidelines

All beta testers need to submit their reports as a plain tex [.txt] file or if you are a user of TexNotes, you can submit it as a TexNote file. Please collect all your findings for a week or so, and submit them as one report rather than emailing every little issue.

Things you need to include in every beta test report:
Name and version of the application you are testing. Date you have started beta testing for stated application and test environment [your machine specs].

You can simplify this process by creating a simple text document template in Windows Notepad or TexNotes and use same template continually. Your template can look something like this:

do-Organizer v3.1.3
20 November 2008

Processor Type: AMD Athlon
Memory Type and Size: 256 MB, Dram
Hard Disk: Maxtor 68160PO, 120 MB
Display Card: Radeon 9600
Monitor: 19″ CRT
Pointer/Controller Type: Wheel mouse
Operating System: MS Windows XP pro sp2
Locale/International settings:
Desktop screen size:
Number of Colors:
Font size display:

Network name and type:
Network protocols used:

Other connected hardware (printers, scanners etc):


Afterwards, you can log all your findings.

You can find the above information by right clicking on “My Computer/Properties” and Start menu/Settings/Control panel.

General Considerations - About the beta-testing procedure…
Try everything you can think of within the program (type letters instead of numbers, use menus in unexpected ways, etc.) If something doesn't’t work properly, try to reproduce the exact steps needed to cause the problem. Listing steps will be of greater help. Afterwards, we can work on fixing the bug. If you find the interface confusing, try to explain why (if you have a suggestion for improvement, please let us know). Check the output for accuracy. Are the results correct? Please don’t limit your comments to problems. We would also like to hear what features you like and/or dislike about the application you are testing.

Send your findings to GemX.
Once you are ready to send your findings and recommendations, zip the TexNotes file named as “Application Name_Your email address Report Number XXX” and email it to: gemxsupport@gmail.com with a subject line “Beta Test - Application Name”

Detailed Guidelines

he objective of this document is to present you, the Beta tester, with general guidelines for testing the Beta versions of Gemx software applications.

 


 

  1. Installation and Un installation
    1. Does the installation process completely describe what is being installed and where it is being installed?
    2. Does the installation process overwrite newer files with older versions of the files?
    3. Does the installation process allow you to make backups of files that it replaces with newer versions?
    4. Does the license agreement screen of the installation process have a “No, I don’t Agree” button?
    5. Does the installation process force you to install the software on a particular disk drive or directory?
    6. Does the uninstall process completely uninstall all files that it has created? This would not include data created by the program during its use.
    7. Does the uninstall process optionally allow you to not uninstall shared files such as DLLs?
  2. General Program Considerations
    1. Is the main program window laid out in such a manner as to present the work in a logical and easy to understand manner (work flow)?
    2. Do all viewable sections of the program fit in a minimum Windows configuration (800 X 600)?
    3. Unless the program is specifically concerned with high resolution, high color graphics, does the program support the minimum Windows color configuration of 256 colors?
    4. Can the main program window be resized to aid in user work, if necessary?
    5. Are visual cues, such as buttons with /images on them, easy to understand?
    6. Are the visual cues backed up by textual cues, such as floating hints or a help/status line?
    7. Is all text in all windows and dialogs correctly spelt?
  3. Program Functionality
    1. Does the program completely perform its intended function?
    2. Does the program perform its primary function in a timely manner?
    3. Is anything that is vital to the intended functionality of the program missing from the program?
    4. Does the program provide adequate help facilities?
    5. Does the program provide an adequate method for you to contact REL Software to report bugs and suggestions?
    6. Does the program provide an adequate method for you to reach the GemX Software Web site?
    7. Does the program provide an adequate method or methods for you to order the program?
    8. Does the program provide an adequate method for you to register?
    9. Can all program functions be accessed using the keyboard instead of a mouse?
    10. Is there anything you think should be included as part of the program’s normal functionality?
    11. Is there anything you think should be added to the program as a “nice to have” function?
  4. Dialogs
    1. Is the dialog color and general layout consistent with other dialogs in the program?
    2. Is the dialog window a fixed size? Exceptions to this would be dialogs that provide some type of function where the resizing of the dialog would make the task easier [where applicable].
    3. Does the dialog have a caption?
    4. Is the dialog caption easy to understand?
    5. Is the dialog caption consistent with the item used to activate the dialog?
    6. When the dialog is displayed, does the main program window become disabled?
    7. Is the dialog border consistent with borders in other dialogs in the program?
    8. Is the dialog’s keyboard tab order consistent with other dialogs in the program?
    9. Are each of the dialog’s hot keys unique?
    10. Can the dialog be closed (canceled) with the Escape key?
    11. Can the dialog be closed (canceled) with system Cancel (X) button?
    12. Is the dialog window the same background color as the other dialogs in the program?
    13. Can dialog controls be accessed by keyboard?
    14. Does dialog tab order follow left to right, top to bottom convention?
  5. Child Windows
    1. Are child windows lacking Ok, Cancel and Close buttons?
    2. Can child windows be tiled?
    3. Can child windows be maximized?
    4. Can child windows be minimized?
    5. Is the current child closed when the main menu Close item is selected?
    6. Is the current child completed/closed when the main menu Save item is selected?
    7. Are child menu items merged into the main menu when the window is opened?
    8. Are child menu items removed from the main menu when the window is closed?
    9. Are the child menu items positioned properly in the main menu?
    10. Are child controls hints displayed in the parent status bar?
    11. Can all form controls be accessed by keyboard?
    12. Does the form tab order follow left to right, top to bottom convention?
  6. Standard Buttons
    1. Are the buttons labeled in the same order in each window and dialog of the program?
    2. Are disabled buttons grayed out?
    3. Are disabled buttons missing from the keyboard tab sequence?
    4. Is there a hot key for every button that requires one? Omit OK, Close and Cancel.
    5. Is each button hot key unique?
    6. Do the buttons lack hints? They should not have any.
    7. If a button activates a pull down menu, does the menu appear directly below the button?
    8. Are the buttons all the same size in all windows and dialogs of the program?
    9. Are the buttons aligned with one another?
    10. Are the buttons spaced the same in all windows and dialogs of the program?
    11. Does each dialog have a default button (if appropriate)? A default button is one that executes if the Enter key is pressed.
    12. Is each button in the program clearly labeled as to purpose?
    13. Are the button labels consistent with the rest of the buttons in the program?
    14. Is there a button which allows the user to leave the dialog without having to perform the dialog’s function?
  7. Edit Fields
    1. Do all edit fields in the program have the same background color?
    2. Do all non-editable fields in the program have the same background color?
    3. Are non-editable fields absent from the keyboard tab order?
    4. Do numeric fields only allow numbers?
    5. Are numeric fields right justified?
    6. Do all alpha fields in the program allow only alphabetic characters?
    7. Do all upper case fields in the program allow only upper case?
    8. Are all alpha fields in the program left justified?
    9. Are the edit fields in a window or dialog aligned with one another to present a pleasing and easy to follow appearance?
    10. Is each edit field in the program the same relative size as the data to be entered into it?
    11. Is each edit field in the program labeled as to purpose?
    12. Are the edit field labels consistent throughout the program?
    13. Do all edit fields lack hints? They should have prompts instead of hints.
    14. Does each edit field have a limit as to the number of characters that may be entered into it?
  8. Toolbars
    1. Are the toolbar functions arranged in some sort of logical order?
    2. Are the toolbar functions separated into logical groupings?
    3. Are any of the toolbar items in the keyboard tab order? They should not be.
    4. If the toolbar is user-modifiable, is this function accomplished in an easily-understood manner?
    5. If the toolbar functions have only visual cues (such as a push button with a bitmap on it), do they also have text cues, such as a floating hint or a hint on a status/hint bar?
  9. Pull Downs and List Boxes
    1. Do all the pull-downs in the program have the same background color?
    2. Can you pull the list down with Alt-down arrow key?
    3. Can you pop the list up with Alt-up arrow key?
    4. Is the highlighted item selected when the Alt-up arrow key is pressed?
    5. Can you pop the list up with the Escape key?
    6. Is the highlighted item selected when the Enter key is pressed?
    7. Are disabled pull-downs absent from the tab order?
    8. Is the pull-down labeled as to purpose?
    9. Are the pull-down labels consistent with the pull down labels in the rest of the program?
    10. Do all pull-downs lack hints? They should have prompts instead of hints.
    11. Do all the list boxes in the program have the same background color?
    12. Are the list boxes in the keyboard tab order?
    13. Do the list boxes all have a vertical scrollbar?
    14. If the information presented in the list box is longer than the list box is wide, is there a way to see all the information (horizontal scroll bar, hint, another window, etc)?
  10. Text Areas
    1. Do all non-editable text areas in the program have the same background color?
    2. When necessary, are scroll bars present in the text area?
    3. Do all text areas lack hints?
    4. Are editable text areas in the keyboard tab order?
    5. Are non-editable text areas missing from the keyboard tab order?
    6. Have Windows clipboard cut, copy and paste functionality been provided for editable text areas?
  11. Data Grids
    1. Do all data grids in the program have the same background color?
    2. If the data grid is non-editable, when tabbing into the grid, is the focus by row (instead of by data cell)?
    3. If the data grid is editable, when tabbing into the grid, is the focus by data cell (instead of by row)?
    4. Can you tab out of the grid?
    5. Does each data grid in the program have a grid header?
    6. Is the grid header font the same as the data font? (It can be bolded, though)
    7. When necessary, are the scroll bars present?
    8. Do the data grids lack hints? They should have prompts instead of hints.
  12. Menus
    1. Does the application contain only one main menu?
    2. Does each main menu item category have a first letter hot key.
    3. Does each main menu item have a hot key?
    4. Are subsections of a main menu category delimited by a line?
    5. If a main menu category is very long, has it been broken up into submenus?
    6. If a main menu item has a shortcut key, is the shortcut displayed with the menu item?
    7. Does each main menu item have a hot key?
    8. Is each main menu hot key unique within its particular menu?
    9. Are non-selectable main menu items grayed out?
    10. Are all selectable main menu items not grayed out?
    11. If present are popup menus activated with a right-mouse click?
    12. Does the popup menu appear close to the mouse cursor?
    13. Are non-selectable popup menu items grayed out or missing?
    14. Are all selectable popup menu items not grayed out or present?
    15. Is each popup menu item clearly labeled as to function?
    16. Does each popup menu item have a hot key?
    17. Is each popup menu hot key unique within its own menu?
  13. Checkboxes and Radio Buttons
    1. If there are a group of checkboxes, are they aligned with one another?
    2. Are non-checkable checkboxes grayed out?
    3. Are checkable checkboxes not grayed out?
    4. Do all the checkboxes lack hints? They should each be clearly labeled as to function, instead.
    5. Is each checkbox in the keyboard tab sequence?
    6. Can select or unselect a checkbox with the keyboard space bar?
    7. Are radio buttons grouped appropriately?
    8. Can only one radio button of a group be selected at a time?
    9. Are the radio buttons in a group aligned?
    10. Are non-selectable radio buttons grayed out?
    11. Are selectable radio buttons not grayed out?
    12. Do all the radio buttons lack hints? They should each be clearly labeled as to function, instead.
    13. Is the group of radio buttons in the keyboard tab sequence? A single tab should get you into the radio group, and a single tab should get you out. Navigation inside the radio button group should be done with the keyboard arrow keys.
  14. General Labeling
    1. Are the labels in a window or dialog all the same font?
    2. Is the label font of a window or dialog consistent with the label font of other windows or dialogs?
    3. Are labels of a window or dialog the same color as labels in other windows or dialogs?
    4. If a label indicates a hot key, is the label connected to the proper control?
    5. Is the spelling correct for all labels?
  15. Notebooks and Tabs [where applicable]
    1. Are the notebook tabs displayed consistently with tabs in other windows or dialogs (top or bottom)?
    2. Are the notebook tabs labeled clearly and consistently with the rest of the program?
    3. Does each notebook tab have a hot key?
    4. Is each notebook tab hot key unique?
    5. Are the general controls for the dialog displayed outside of the notebook page?
    6. Do the notebook tabs lack hints?
 

Search GemX.com

Type in your search phrase in the search box below
and hit enter or search button.

Login to your GemX account

You may use this login form to login your GemX Software registered user area. Please remember to enter correct login info.

User ID (email address)

Password (software registration number)

Login

I can not access my account?

do-Organizer at rock bottom  low price

 

 

TexNotes