Important links for organizer team

• FigJam (public)
• Project management sheet
• Information for sponsors

What is browser automation challenge?

Browser automation challenge is a recreational contest where teams race to complete various browser automation challenges using their preferred tools and programming languages.

It aims to bring together automated testers, RPA specialists, QA engineers, students and developers interested in automation.

For more information about the format and rules, check out the event description page.

What are the goals?

While the event is structured as a contest, our goals for this event is for people to:

• Meet up with other automation enthusiasts
• Exchange techniques that different people use
• Observe the masters of their crafts at work

When is the event?

The date is Wednesday, November 20, 2024, in the evening.

Status

Items	Status
Food	✅ Self-managed with sponsored funds
Prize pool	✅ 26 prizes in total
Event staff	✅ Assembled a team of 14
Challenges	✅ 8 challenges
Live leaderboard	✅ Still unimplemented
Beverages	✅ Sponsored by We Love Bug
Venue	✅ Sponsored by Cleverse

What do we need help with?

This section is outdated, but kept here for future reference

• Prize sponsorship: We're using a prize pool system where winners choose prizes in order of their ranking. Any number of prizes are welcome.
• Food sponsorship: We are looking for food sponsors for 80 people.
• Co-organizers: We welcome additional organizers to help plan and execute the event, to make the event the best it can be.
• Event staff: We need volunteers to assist with event logistics on the day.
• Have something else to contribute? We welcome contributions to help us enhance the event experience. Let’s talk!

Contact person is Thai ( dtinth), reachable via Facebook messenger: dtinth

Who is organizing this event?

This event is part of showdown.space initiative which aims to give stage for people to demonstrate their expertise through recreational tech contests. We have run these events in the past:

• Code in the Wind #2
• Code Golf Party #1
• Code in the Wind #1

Activity log

Date	Activity
2024-07-02	dtinth implemented a first challenge in private to test the idea, eventually becoming the demo challenge.
2024-07-03	2nd and 3rd challenges implemented, which eventually became the ‘buttons’ and ‘robot’ challenges.
2024-08-27	4th and 5th challenges implemented, which eventually became the ‘calendar’ challenge and ‘towers’ challenges. The inspiration for the ‘calendar’ challenge came from seeing how Huly tests their time widgets
2024-09-07	Discussed potential date ranges for the event. Consideration is to not collide with students’ final exams and new year seasons. Tentative range is in November.
2024-09-15	Discussed with rayriffy and betich about potential event dates, taking into consideration travel plans and other events around that time. Plan for 2024-11-20.
2024-09-29	Announced the intent to organize the event publicly at Vue Thai Conf 2024, kickstarting the organizing process.
2024-10-23	Announced the intent to organize on Facebook, recruiting team, call for sponsors, etc.
2024-10-31	Confirmed beverage sponsorship from We Love Bug Biz
2024-11-04	Confirmed venue sponsorship from Cleverse
2024-11-06	Kick-off meeting planned, created FigJam board
2024-11-07	Kick-off meeting, Panthipa offered to help with internal coordination and managing the event project
2024-11-08	Soft launched. Early bird challenger tickets released.
2024-11-08	7th challenge implemented after getting inspired from discussing with We Love Bug Biz about the challenges they face at work.
2024-11-09	Early bird observer tickets released.
2024-11-11	General ticket release announced.
2024-11-12	General ticket released with a challenge contributed by @narze.
2024-11-16	Development began on challenge portal, an ElysiaJS server-rendered web app using Grist as a backend.
2024-11-18	General ticket challenge re-released as a practice challenge.
2024-11-19	@narze contributed the 8th challenge, eventually becoming the ‘seven’ challenge.
2024-11-20	Event date. Livestream available on Facebook.

Event rundown

18:00 - Registration

• Participants arrive and register for the event

18:30 - Dinner & guest speaker

• Serve dinner
• Guest speaker presents

18:45 - Event introduction and setup

• Introduce the event
  • Welcome
  • Thanks all sponsors
    • BigBears.IO พี่หมี for providing funding to showdown.space
    • Cleverse for venue and การอำนวยความสะดวกต่างๆ ด้านสถานที่
    • We Love Bug Biz for beverages and prizes.
      • We have 200 bottles of water, 100 soft drinks, 60 coffee bottles
      • We will reveal the prizes at the end
    • MyOrder for prizes
    • EarnIn for prizes
    • Nonzero Sumgame for funding this event
    • DEV Forward for prizes
• Introduce the event format and rules
  • This event will be like CTA challenge
  • You have 2 hours
  • We will release challenges for you to solve, and you can solve in any order
  • First solver will get MAX points, second team MAX-1, third team MAX-2, and so on
  • We expect to release all challenges in the 1st hour, the 2nd hour you can focus on maximizing score
  • At the end we will sum all scores and give prizes
  • How prize giving works:
    • We have a total of 20 prizes in the pool, with 2 prize categories
      • Cash prize
      • Item prize
    • At the end, the 1st ranked team will get to choose the prize, followed by 2nd, and so on.
      • The team can choose one of:
        • A single cash prize for the whole team
        • Item prize for each person in the team
• Guide participants to log into the Challenge Portal (see Figjam for images of all flows)
  1. Go to challenges.showdown.space and log in with Eventpop account
     • Observers can also join
  2. For Challengers only - click the I am a challenger button and fill in your team name and hit submit
     • Staff will onboard your team
     • For staff: To onboard, search for matching information on Grist and check the “Enrolled” box
  3. Should see dashboard page (`/dashboard`) with your team name
     • Guide participant to share their screen
     • The screen should appear in VDO Ninja director view
• Explain how to access challenges and request reviews
  • Each challenge will have “Go to challenge” link.
    • Some challenge is “auto submit” - so if you passed, the challenge will auto submit for you
      • The “Go to challenge” link is unique to your team.
    • Some challenge is “manual submit” - after you solve the challenge, click “Request review” button
    • After submission, we will ask your team to DEMO your solution, and if pass, you will get point. If not pass, get penalty -5 points.

19:00 - Challenges

• Release the first challenge(s)
• Begin the two-hour challenge period

19:00 ~ 20:00 - Progressive challenge release

• Continue to introduce and release new challenges
• Review completed challenges as teams submit them
• Award points or apply penalties based on review results
• Facilitate solution explanations after each successful solve

20:00 ~ 21:00 - Final challenge hour

• Ensure all seven challenges are available to participants
• Remind teams they have one hour remaining
• Teams continue working on remaining challenges
• Continue reviewing submissions and awarding points/penalties
• Encourage teams to attempt as many challenges as possible

21:00 - Challenge period ends

• Stop accepting new submissions and reviews
• Finalize the scoreboard
• Talk about the sponsors and prize items
  • Venue sponsor
    • Cleverse
  • Financial sponsor
    • BigBears.IO
    • Nonzero Sumgame
  • Beverage sponsor
    • We Love Bug Biz
  • Prize sponsors
    • We Love Bug Biz
    • MyOrder
    • EarnIn
    • DEV Forward
  • More prize introduction
    • From Riffy
    • From Thai
• Review the final scoreboard
• Announce the winning teams
• Prize distribution:
  • First place team members each select one item from the prize pool
  • Continue with other teams in order of placement until prizes are exhausted
• Final remarks:
  • Thank all the staff who helped
  • Challenges will be uploaded and open sourced at https://showdown.space/events/browser-automation-challenges/
  • Feedback form
  • Thank attendees who joined