View Categories

Phase 5: QA – Efficient and Traceable Survey Testing

Once the initial programming is complete, the Quality Assurance (QA) phase is the most critical step to ensure a flawless respondent experience. Kalever centralizes this process by allowing testers to report issues in real-time directly from the survey test link, creating an immediate and transparent feedback loop with the programmer.

Scenario: The programmer has scripted the ‘Luxury Brands’ survey in Decipher. It’s now time for the QA team to test it thoroughly before launch.

Step 1: Prepare the Project for QA #

A smooth QA process starts with setting up a single, unified environment for collaboration.

  1. Add Testers to the Project: The Project Manager must ensure all QA testers are added as members to the internal project (“Luxury Brands – Internal”). This gives them access to the TrackEntry board where all issues will be logged and tracked.
  2. Integrate TrackEntry: The programmer must confirm that the TrackEntry project is correctly integrated into the Decipher survey test link. This is the key to enabling in-context feedback.

Step 2: The QA Testing Workflow #

Testers should now use the survey test link that has the TrackEntry integration active. When they discover an error, the process for reporting it is seamless.

Scenario: A tester finds that a routing instruction at question S5 is incorrect.

  1. While viewing the test link on question S5, the tester clicks the TrackEntry icon that appears on the screen.
  2. This opens the “New entry” window as an overlay, without the tester needing to leave the survey page.
  3. The tester fills out the form:
    • Question ID: This is often auto-populated with “S5” because the tester is on that specific question.
    • Priority: They set it to “Critical.”
    • Description: They describe the issue: “Routing incorrectly jumps to S10 when option 3 is selected.”
    • Attachments: They use the screenshot function to automatically capture an image of the error.
  4. The tester clicks Submit.

Step 3: Real-Time Collaboration and Resolution #

The moment the tester clicks “Submit,” the following happens instantly:

  • The new entry appears on the TrackEntry dashboard inside the internal project.
  • The programmer receives a notification and can immediately see the ticket, complete with the screenshot and all details.
  • If the programmer needs a quick clarification, they can ping the tester in the Live Chat to discuss the issue in real-time.

Once the programmer fixes the bug in Decipher, they update the status of the entry from “Open” to “Implemented.” This automatically notifies the QA tester that the issue is ready to be re-tested.

This closed-loop feedback system—where issues are reported directly from the live environment and tracked in a central hub—dramatically reduces errors, eliminates messy spreadsheets, and significantly speeds up the entire QA process.