1. References
1.1. Mob testing
1.2. Crownd sourcing test
1.3. A hackaton for testers
1.4. Software Testing World Cup
1.5. Testahon
2. Definition
2.1. Meeting of testers and other roles and stakeholders that are part of the software development of a product or software. They get together to explore the product, find bugs and enhancements and collect feedback about the quality and requirements.
3. Benefits of use
3.1. Individual
3.1.1. Learning opportunities
3.1.1.1. Technical skills
3.1.1.1.1. Testing Strategy
3.1.1.1.2. Testing techniques
3.1.1.1.3. Tools
3.1.1.1.4. Testing ideas
3.1.1.1.5. Innovative and creative solutions
3.1.1.1.6. Testing heuristics
3.1.1.2. Soft skills
3.1.1.2.1. Team work
3.1.1.2.2. Time management
3.1.1.2.3. Leaderships
3.1.1.2.4. Result orientation
3.1.2. Networking
3.1.2.1. Meet other people and companies culture
3.1.2.2. Meet people from other regions and countries
3.1.3. Fun
3.1.3.1. The gamified experience of a testing marathon always turn into a fun competition
3.1.4. Rewards
3.1.4.1. The learning
3.1.4.2. It's a milestone for a testing career
3.1.4.3. Prizes
3.2. Testing Community
3.2.1. Knowledge exchange
3.2.2. Coaching
3.2.3. Increase engagement
3.3. Companies
3.3.1. Fast feedback about the quality of a product
3.3.2. Feedback given by a larger number of professionals with different perspectives
3.3.3. Tests done in a variety of devices
3.3.4. Compare the products with the similar of other companies.
3.3.5. Recruitment of talents
3.3.5.1. It's possible to identify excellent people at the testing marathons
4. Framework
4.1. Set the goals
4.1.1. Define the product
4.1.2. Define the target devices/operational systems
4.1.3. List the main roles involved
4.1.3.1. Testers
4.1.3.2. UX
4.1.3.3. UI
4.1.3.4. Product Owner
4.1.4. Set the time-box
4.1.5. Schedule
4.2. Setup the needed infrastructure
4.2.1. Servers
4.2.2. Applications
4.2.3. Devices
4.2.4. Tools
4.2.4.1. Bug management
4.3. Run the CESAR.thon
4.4. Collect feedback
4.5. Compile the marathon data
4.5.1. Bugs
4.5.2. Enhancements
4.5.3. Quality issues
4.5.4. New requirements
5. Results
5.1. 2016
5.1.1. 4 testing marathons
5.1.1.1. 1 business prospecting phase
5.1.1.1.1. More than 120 bugs
5.1.1.1.2. 30 QAs
5.1.1.1.3. 3 hours
5.1.1.2. 3 Internal applications
5.1.1.2.1. More than 80 bugs
5.1.1.2.2. 26 QAs
5.1.1.2.3. 7 hours
5.1.2. 17 lightning talks
5.1.3. 3 dojos
5.1.3.1. Web automation with Selenium
5.1.4. 2 mob testing
5.1.4.1. Google hacking
6. Why use it?
6.1. Improve engagement
6.1.1. In your company
6.1.2. Your local testing community