Test Hackathon: #ContinuousTesting
Test Hackathon is the first online and offline combined software test hackathon.
In its 4th year, our theme is Continuous Testing
and the fun is non-stop, again.
Gather your team, submit your application, qualify for the finals, code hard and get awards!
Online + Offline Action
Prizes & Gifts
Dates to Remember
September 9th, Monday
Last Day of Submission
September 20th, Friday
Announce of Hackathon Finalists
September 30th, Monday
October 8th, Tuesday
Between 09:00 - 21:00
– Teams can have 2-4 members,
– Team members could be professionals, students or enthusiasts,
– No age restriction,
– English is the common-language in the event.
Hackathon Day: Schedule
– Door opens at 9:00
– Happens between 10:00 and 15:00
– Judge presentations between 15:00 and 18:00
– Awards will be delivered after the event: Keytorc TestTalks
Hackathon Day: Venue Facilities
– Complimentary light foods and drinks during day
– Bathrooms, smoking, resting areas
– Electricity, basic internet connection
– 1 Desk and 4 chairs per team
Hackathon Day: Technical
– No limitation for preferred coding languages.
– No limitation for preferred CI server.
– No limitation for any DevOps Tool.
– Teams can use Selenium Webdriver or preferred similar ones.
– Team Keytorc will be at Hackathon venue to clarify things that are not fully understood.
– Teams will use Github to submit their work.
Hackathon will happen between 09:00 and 18:00
– Onboarding and general briefing
– Test subject declaration
– Development begins
– After development phase, teams will present their codes to judges.
– Judges evaluates the outputs.
– Results will be declared at open community Keytorc TestTalks event which will take place afterwards.
– Judges need to understand teams’ backgrounds and motivations about test automation. They are also curious about team members’ soft-skills.
– Conceptual Assessment questions is the ultimate way to impress the judges upfront, and get the ticket to attend Hackathon Day.
– Assessment will be handled by an online survey tool, which will be declared.
– It will be a web application to be tested.
– The application will be declared in the beginning of Hackathon Day.
– Teams are able to use Java, C#, Python or Ruby or any other language that they feel comfortable.
– Teams can use preferred DevOps tools, CI Servers, Selenium Webdriver, SahiPro, RobotFramework, Cucumber or any other tool that they may prefer.
No, they will meet at code presentation phase at Hackathon Day.
There will be no restrictions about tasks. Teams are able to establish additional functions such as cloud integration or continuous integration within their time.