Skip to content

Testing and Publishing

Testing and publishing are essential steps in turning your project into something reliable and shareable. Testing helps you evaluate whether your prototype or system actually works for users, under real conditions. Publishing means making your work, results, or knowledge accessible to others – this can be through documentation, open-source code, a project website, or even an academic paper.

Why is this relevant to you? Because as a Creative Technologist, your work only has real impact if it can be tested, validated, and shared. Testing ensures quality and usability, while publishing builds credibility and allows others to build on your ideas.

Starting Points

  • Plan your tests carefully.
    Example: define what you want to learn from a user test (e.g. “Can users understand the gesture controls within 30 seconds?”).
  • Choose appropriate methods.
    Example: run quick usability tests with 5 users, or stress-test your prototype under different conditions.
  • Think about your publishing format.
    Example: a GitHub repository for code, a short video demo for social media, or a structured report for an academic audience.

Key Points

  • You test iteratively, not just once at the end. Each test feeds back into design improvements.
  • You consider both functionality and experience: does it work technically, and is it meaningful for users?
  • You publish in a way that fits the context: clear for your team, accessible for clients, or open for a community.
  • You respect ethical aspects: anonymize user data, cite sources, and be transparent about limitations.
  • You reflect on your outcomes: what do your tests prove, and what still needs exploration?