Skip to main content

QA Testing Overview

Quality Assurance is essential to ensuring NetPad delivers a reliable, bug-free experience for all users. This section provides structured guidelines, templates, and resources for testing NetPad's features systematically.

What's Coveredโ€‹

This QA Testing section includes:

DocumentPurpose
QA FrameworkComprehensive testing guidelines, test cases, and user journeys
Quick ReferencePrintable quick reference card for testers
Bug Report TemplateStandardized template for reporting bugs
Test TrackerCSV file for tracking test execution and results

Testing Philosophyโ€‹

NetPad QA follows five core principles:

  1. Test as a real user โ€” Follow the journey a customer would take
  2. Document everything โ€” Screenshots, screen recordings, exact steps
  3. Test edge cases โ€” Empty inputs, special characters, large files, slow connections
  4. Test across browsers โ€” Chrome, Firefox, Safari, Edge
  5. Test responsive design โ€” Desktop, tablet, mobile viewports

NetPad's Core Pillarsโ€‹

Testing is organized around NetPad's four core pillars:

PillarComponentsPriority
FormsForm builder, 30+ field types, conditional logic, multi-page, themingCritical
WorkflowsWorkflow editor, 25+ node types, triggers, execution engineCritical
Data ManagementData browser, connections, import/exportHigh
AI/ConversationalConversational forms, RAG, AI form generationMedium

Testing Environmentsโ€‹

EnvironmentURLPurpose
Productionhttps://app.netpad.ioFinal verification only
Staginghttps://staging.netpad.ioPrimary testing environment
Developmenthttps://dev.netpad.ioEarly feature testing
Localhttp://localhost:3000Developer testing

Quick Startโ€‹

Smoke Test (5 minutes)โ€‹

A quick test to verify core functionality is working:

  1. Login โ†’ Dashboard loads
  2. Create form โ†’ Add 1 field โ†’ Save
  3. Preview โ†’ Submit test data
  4. View submissions โ†’ Data appears

Pre-Release Checklistโ€‹

Critical paths that must pass before any release:

  • User can sign up and create organization
  • User can create form with basic fields
  • User can publish form
  • End user can submit form
  • Admin can view submissions
  • Workflow triggers on form submission
  • Email notifications send correctly

Bug Severity Levelsโ€‹

SeverityDefinitionResponse Time
CriticalSystem unusable, data loss, security issueImmediate
MajorFeature broken, no workaround, blocks workflow24 hours
MinorFeature impaired but workaround existsNext sprint
TrivialCosmetic issue, typo, minor UI glitchBacklog

Test Data Guidelinesโ€‹

  • Never use real customer data for testing
  • Use clearly fake data: "Test User", "test@example.com", "555-0100"
  • Prefix test records with [TEST] for easy cleanup
  • Clean up test data after completing test cycles

Getting Startedโ€‹

  1. QA Framework โ€” Start here for comprehensive test cases and user journeys
  2. Quick Reference โ€” Keep this handy while testing
  3. Bug Report Template โ€” Use this template when filing bugs

Next Stepsโ€‹

Ready to start testing? Begin with the QA Framework for detailed test cases covering all NetPad features.