Anyone who is interested in exploring ideas through test code - including Swift Testing - is welcome to apply, regardless of experience level.
To apply for the Testing Lab, select the application link in the internal announcement. and submit your response after writing your Challenge Statement, based on the provided Research Idea (Big Idea).
Using your Challenge Statement as a starting point, you’ll work with Jaesung to set up your Investigate direction for defining your Challenge Response.
You’ll create a final deliverable that can be shared on this repository such as sources or discussions, and spend the lab period carrying out your Act phase based on your Challenge Response.
| Phase | Duration |
|---|---|
| 📚 Investigate | 2 days |
| 🔬 Act | 7 days (weekdays only) |
| 🎓 Epilogue | 1 day |
| Guiding Activities | Guiding Question |
|---|---|
| Get started with WWDC sessions | How can I find the appropriate Apple's development/design sessions for my Challenge? |
| Explore existing discussions in the open source community | What existing discussions or approaches are related to my challenge? Where are these discussions taking place? What gaps or opportunities have been discovered from the existing discussions or approaches? |
| Design code with diagrams | How can I define the structure of my code? How can I map out every branch, condition, and edge case in my logic before it becomes code? How can I trace method calls and data flow between objects at runtime? |
| Prepare to open great Pull Request | How can I help reviewers understand and review my Pull Requests effectively? |
| Looks Good to Me - Explore how to communicate for better code | How can I provide good reviews for Pull Requests? |