over 5 years ago
More on submitting bots for testing
The deadline is around the corner on July 18th and we know you’re hard at work. Remember, you are required to submit the following items:
1. A demo video that clearly shows your bot functioning on its intended platform.
2. Share your code repository publicly or privately through GitHub or BitBucket with firstname.lastname@example.org.
3. Access to a working bot.
4. Testing instructions with anything we need to know to test your bot.
5. Text description should include a brief explanation of what the bot Application does and what makes it unique.
6. A completed submission form on Devpost.
Bot Definition: You must export your bot definition file (a JSON configuration file that defines the structure of your Lex bot along with any associated Intents and Slot Types). You may use this Node.js utility to create the bot definition file.
Testing your bot: The easiest way to test is if you provide access to your bot running on its intended platform. For example, you can do this by inviting email@example.com to a Slack channel where the bot is running.
Facebook Messenger bots that are not public yet: add the Facebook ID: stef.devpost.1 as a tester role. Then on your submission form, include a link in your testing instructions to the Facebook page where we can chat with the bot. If you want to try this out ahead of the deadline, feel free to email firstname.lastname@example.org.
We're here to help. If you have any questions about the hackathon, post on the discussion forum or email email@example.com and we'll respond as soon as we can.