Emazing Retailing is a dedicated survey system in SurveyTester. A project set to Emazing (or to Automatic) recognises an Emazing survey the moment the browser extension opens it - the screening questions, the shopping simulation that follows them, and the questions asked afterwards about every product in the basket. From there everything else in SurveyTester works as usual: Auto Answer, Auto Complete, SurveyBots, test cases, issues and the Pages & Routing overview.
What an Emazing survey looks like to a tester
An Emazing study has three stages, and they look nothing alike:
- The screener - a classic questionnaire, one question per page, with a Next question button and the note "This question is mandatory". There is no Back button.
- The shopping simulation - a small web shop: a product listing with filters and a basket, a product page with Add to cart and Buy now, the basket with Checkout, and a Not interested in any product button on every page for respondents who do not want to buy.
- The follow-up questions - the same questions are asked once for every product that ended up in the basket ("What do you like about this product?"), each page showing the product it refers to.
Why this is hard to test without SurveyTester
- The shop is not a questionnaire. Product tiles, "Add to cart" and "Checkout" are links and buttons, not survey questions. SurveyTester treats the listing as a multiple-choice question (every product is an option), the product page as the choice between adding the product or leaving, and the basket as a read-only summary of what was chosen - so an automated run shops its way through to the checkout like a respondent would.
- The same question, many times. After the shop, every product in the basket gets the same set of questions.
SurveyTester names each round after the product (
Q10635_13051,Q10635_13106), so the test run shows every round separately and a test case can answer them differently. - Rules hidden in the page. A "none of these" option that clears all others, or a limit on how many options may be chosen, exists only in Emazing's scripts. SurveyTester reads them, marks the option as exclusive and respects the limit.
- Mistakes are silent. When a mandatory question is sent without an answer, Emazing simply shows the same page again - no error message. SurveyTester notices the repeated page and does not get stuck.
- Screen-outs you can see. Emazing's demo links mark every option that ends the interview ("Screen out", "Screen out quota"). SurveyTester records the marker on the option and can build the Completed and Screenout test cases from it - see Test cases from the survey's own rules.
Supported question types
| Emazing page | How SurveyTester tests it |
|---|---|
| Single choice | One option is clicked. |
| Multiple choice | Several options are clicked; an exclusive option ("none of these") is only chosen on its own, and the allowed number of selections is respected. |
| Option with text field ("Other, please specify") | The option is chosen and a fitting text is typed into its field. |
| Open end (text box) | A fitting text is typed; the product the question refers to is part of the question text. |
| Explanation / information page | Recorded as information; SurveyTester moves on with Next question. |
| Video page | SurveyTester waits until the video has ended and Next question becomes active. |
| Shop: product listing | A multiple-choice question whose options are the products; "Not interested in any product" is the exclusive way out, the basket link leads to the checkout once something was added. |
| Shop: product page | A single choice between Add to cart, Buy now and Not interested; Back to results continues the shopping. |
| Shop: basket | Read-only: the products in the basket are recorded as the answer; Checkout continues. |
A page type SurveyTester has not met yet (for example a slider or a price question) is still recorded as a page so the test run continues; it is marked in the page structure so you can see which type needs attention.
Step by step
- Create the project. Choose Emazing as the survey system, or leave it at Automatic - the survey is
recognised either way. Paste the survey link. Prefer the vendor's demo link (
emzrtl_source=demo): it shows the screen-out markers that SurveyTester turns into test cases, and it does not spend real sample. - Start a test run from the project with the SurveyTester browser extension. The SurveyTester bar appears above the survey and the first question is recorded as step 1.
- Answer the survey by hand, or press Auto Answer and Auto Next to let SurveyTester fill the page and move on. In the shop, Auto Answer opens a product, adds it to the basket, returns to the listing and finally goes to the basket and the checkout - or leaves through Not interested in any product.
- Check the result on the Pages & Routing page: the screener questions, the shop pages and one round of follow-up questions per product.
Good to know
- Question names. Emazing numbers its questions; SurveyTester uses those numbers (
Q10117). Shop pages are namedShop_<study>,Product_<product>andCart_<study>; follow-up questions add the product (Q10635_13051). - Option codes are global. Emazing's answer codes identify the option across the whole platform, not just within one question. SurveyTester therefore never guesses which code is an exclusive "none of these" - it reads the marker Emazing puts on the option.
- The shop is random. The product order in the listing changes with every visit. Products are recorded by their code, so test cases and issues stay correct.
- The end of the survey. Studies usually end on the panel's redirect page. Add it to the survey end pages of the project type (or the project) so SurveyTester knows which outcome the run reached.