## Closed Web Testing on itch.io & Git README Integration ### Uploading Web Builds & Managing Versions on itch.io 1. Go to your **itch.io Dashboard** $\rightarrow$ **Create New Project**. 2. Set **Kind of project** to **HTML**. 3. Under **Uploads**, upload your exported `.zip` file (ensure `index.html` is at the root of the ZIP archive). 4. Check the box: **"This file will be played in the browser."** #### Managing Multiple Test Builds * Upload multiple `.zip` files to the same project page, naming them clearly by version (e.g., `v0.1-mechanics.zip`, `v0.2-dynamics.zip`). * Use the file options to assign display labels so testers know which build is which. * You can toggle **"Play in browser"** on a specific version to control what runs, or keep multiple files available for download and play. --- ### Lock the Page & Generate the Password Link 1. Scroll down to **Visibility & Access**. 2. Select **Restricted**. 3. Check **"Also allow a password to view page"** and enter your chosen password. 4. Save the project page. #### Direct Access URL Bypass the manual password entry screen for your testers by appending the password directly to the project URL: `[https://username.itch.io/project-name?password=yourpassword](https://username.itch.io/project-name?password=yourpassword)` --- ### Add Testing Access to Your Repository Place this access information directly inside your project's **README.md** file so collaborators, reviewers, and testers can easily launch active builds. In your README, list the current test versions alongside their direct password-authenticated URLs and the plaintext password (in case they are prompted manually). --- Here is how to set up mixed-methods PXI feedback forms using Google Forms, distribute them to your testers via email, and document the collected survey data inside your Git repository. --- ### Developing the Mixed-Methods Form in Google Forms Use **Google Forms** or **Microsoft Forms** or something similar to build your miniPXI feedback instrument combining quantitative Likert-scale data with qualitative open-ended responses. * **Quantitative Core (PXI Constructs):** Add items using the **Linear scale** question type ($1$ to $7$, where $1 = \text{Strongly Disagree}$ and $7 = \text{Strongly Agree}$). Group them by construct: * *Functional Dynamics:* "The controls were intuitive and responsive." * *Psychosocial Aesthetics:* "I felt a strong sense of agency and mastery." * **Qualitative Depth (Mixed-Methods):** Pair every construct section with a mandatory or optional **Paragraph** (long-answer) text field asking *why* they gave that rating (e.g., *"What specific moment or mechanic influenced your score above?"*). --- ### Distributing the Form in Your Test Email When sending out test invitations or feedback requests to your closed testing group, include both the password-authenticated game link and the direct survey link. **Key Email Components:** * **Playable Game Link:** `[https://username.itch.io/project-name?password=yourpassword](https://username.itch.io/project-name?password=yourpassword)` * **Direct Form Link:** Add a clear call-to-action link to your Google Form. * **Testing Instructions:** Ask players to play the build for a set duration before filling out the form so their responses reflect a complete dynamic playthrough. --- ### Exporting & Documenting Survey Data in Your Git Repo To maintain an auditable trail of user testing data alongside your source code: 1. **Export Raw Responses:** In Google Forms, go to the **Responses** tab, click the three dots ($\vdots$), and select **Download responses (.csv)**. 2. **Convert to Markdown:** Convert the response data into Markdown format using a CSV-to-Markdown tool or script, or write a summary table. 3. **Commit to Repository:** Create a `evaluations/` or `data/` directory in your Git repository and save the exported results as a `.md` file (e.g., `evaluations/v0.2-pxi-results.md`). #### Suggested `.md` File Structure: * **Metadata Header:** Record the build tag, evaluation date, and total number of participants ($N$). * **Quantitative Summary:** Include a Markdown table detailing the mean scores and standard deviations for each $1\text{--}7$ PXI scale item. * **Qualitative Categorization:** Group player text responses under their respective construct headings to highlight recurring feedback themes or control complaints.