Your IT Team will provide you with a URL for the SurveyTester site and your login credentials.
If for some reason you cannot enter the system click on “I forgot my password.”
You will then be prompted for you user details.
An e-mail will be sent to the e-mail address registered in the system when your account was created.
After logging in, you are presented with a list of projects that you have designated as favorites, and a Scheduler showing current projects and associated key dates. The scheduler will show all calendar events you have created, and events created by others that they have deemed to share.
Click on the Project form on the top left, to display the list of projects to which you have been granted access. Select the project you are to test and review the notes and tasks that have been created by the Project Manager.
Next, you should look to see if other testers have already reported any issues. To do this, simply click on the Project Issues menu item.
You can then see all reported issues. As you go through your test run you will be able to see these same issue notifications on the pages in the survey where the issues appear. This lets you see if the issue has been resolved or if it still exists.
After you have reviewed the notes, tasks and issues, click on the Test Survey menu item on the top menu bar.
You will then be presented with a pop-up menu asking you to select the language of the survey you want displayed. If the survey only contains one language, it will be the sole option presented in the drop down menu item.
The Box on the left that is highlight in Gray is the default way to start a test run – Manually moving through the survey like actual respondents will do.
New to this release, we have the box on the right that lets you have SurveyTester run a specified number of automatic test runs. The default being 5 test runs.
Clicking on the text in that box will highlight the item and allow you to specify the desired number of test runs to be completed.
In Manual mode, you may also choose to jump directly to a specific page in the survey. This allows you to test and review specific questions without having to take the entire survey every time you want to check on something specific.
Most testers will skip the jump option and begin the test with the first question in the survey (the default), by clicking the Start button. Programmers wishing to simply go to a specific question to review a bug can easily do so by selecting that page from the list. Please note that the list only contains questions that have been already been tested by a tester inside the selected project.
This will open the actual survey with a SurveyTester menu bar present at the bottom of the browser window. (The survey URL was provided by the project manager; see the Administration of SurveyTester section for details).
At the lower left of the window you will see the ST task button.
Click on it to display items.
If you are using SurveyTester with the SurverTester Extension* (more details later) you will see these items.
If you are using Internet Explorer which does not support the extension, you then you will see the older/original icon items shown below. In the latest release the ruler has been eliminated when using the extension.
*WE HIGHLY RECOMMEND THAT TEST RUNS BE DONE IN THE CHROME BROWSER, USING THE SURVEYTESTER EXTENSION.
In the lower center of the web page you will see 3 small blue items. If you move your mouse down to that area, three buttons will pop up. They are ‘semi-hidden’ so as not to obstruct any of the actual web page that your respondents will view.
We will see more details on these items a little later
Clicking on the Issues menu item will display all reported issues on the page.
You can click on a reported item to see more details.
You will also use this form to report issues that you find.
As you proceed through the survey, you can report any issue, from a simple spelling error to serious routing errors. Simply click on the Issues menu item on the SurveyTester menu bar, which will open a pop-up form. The form will prompt you to enter a description of the issue, specify the type of issue and specify its priority level (if you have been given permissions to do so).
The number of drop-down boxes on this form is under the control of the system administrator and will vary greatly from company to company. The screen shots of the “add issues” form shown in this manual will probably NOT match the “add issues” form you will see, as each site determines what fields will appear on that form.
After you have entered the relevant information, click Add Issue (or Save if you are editing an already reported item). The fields in the pop-up form, such as Issue Type or Priority, are defined by the administrator and assigned to the project by the Project Manager. Therefore, the form might look slightly (or very) different for different projects.
You may enter multiple issues per question/page. This allows for the accurate tracking of each and every issue as a separate item. A distinct SurveyTester issue record is created for each problem reported.
Routing Diagram is the last menu bar item. It displays numerous parameters for the specific page. The History Section of the dialog box shows the answers to all questions on all pages from the last test run. Click on the gray box to see all previous tester responses. It also provides an option, by clicking on the green question name icon, to jump back to a specific page. These features help programmers resolve issues.
In testing surveys, we have found that completing large mandatory grid questions can be very frustrating.
A perfect time to use the auto-answer feature. Since tester Jim previously told the programmers to make the response to this question mandatory.
When/if you reach the very end of the survey the system will inform you that the survey is complete and ask if you wish to return to the last page completed. If you choose that option you can then use the Back button in the survey (if there is one) to go backwards within the survey and review things again. In almost all cases you will choose No on this form.
If you are a user with SurveyTester access permission, you will be taken back to the SurveyTester main menu form. If you are an external/client user, you will be directed to the SurveyTester home screen.
During testing it sometimes happens that a test run encounters a server time-out. The system will detect the “end of interview” and when you restart the survey, SurveyTester will offer you the option to go back to the last question that was active. If you click yes, a new interview will start, replaying all the pages of your first test run, and then stop at the last question before the “end of interview” was triggered by the server.
A new test run is automatically started for this approach because the old test run was already timed out. This feature, however, can still save the user a lot of time by taking them to the point in the survey at which they timed out.
2x4 Solutions GmbH
+49 174 1674678
or email us:
Please enter your email address for the SurveyTester Newsletter.
SurveyTester allows Project Managers, Survey Authors, QA-specialists and even End-Clients or other stakeholders working together on making better surveys. SurveyTester is a cloud base solution for testing surveys before they go live. It includes a collaboration area for the survey team working together, includes screenshots of all tested survey pages made with a variety of devices and performs automatic test runs with just using a Survey Link.
Strictly necessary cookies guarantee functions without which this website would not function as intended. As a result these cookies cannot be deactivated. These cookies are used exclusively by this website and are therefore first party cookies. This means that all information stored in the cookies will be returned to this website.
Functional cookies enable this website to provide you with certain functions and to store information already provided (such as registered name or language selection) in order to offer you improved and more personalized functions.
Performance cookies gather information on how a web page is used. We use them to better understand how our web pages are used in order to improve their appeal, content and functionality.
Marketing / Third Party Cookies originate from external advertising companies (among others) and are used to gather information about the websites visited by you, in order to e.g. create targeted advertising for you.