Technical Guidelines

    1. You can use any language to build your solution.

    2. You can use any open source tool or the tools mentioned in the list below to build your solution

    3. Your code must be modular and reusable across components

QA Guidelines

    1. Participants needs to deliver the best possible solution within the timeline given. They need to detect any issues that might block the successful operation or affect the user experience.

    2. To achieve that, they need to document the requirements to solve the problem statement.

    3. Against each requirement they need to write valid test cases and test the software.

    4. For testing they can follow any 2 approaches:

        a. Manual Test Cases in a document

        b. Automated Unit Test cases:  where the developers write unit tests for checking the reliability of their written code.

        c. Automated API Test Cases: it is similar to the unit test cases with a setup, a call to the API method and then checking the results.

        d. Record and Play: Can use any opensource tool to record and play and check the reliability of the software.

        e. UI Automation: Creation of automated scripts to check the successful operation of the software.

    5. The participants can use any source tool or any language for automation.

Selection Criteria

• Technical Solution- Everyone must present their work. How technically impressive was the hack? Was the technical problem the team tackled difficult? Did it use a particularly clever technique, or did it use many different components?
• Design pattern- Did the team put thought into the user experience? How well designed is the interface?
• Quality Check- Did the team followed all quality parameters and did performance testing.
• Completion- Does the hack work? Did the team achieve everything they wanted?
• Learning: Did the team stretch themselves? Did they try to learn something new? What kind of projects have they worked on before?