Back to all discussions

  •   almost 9 years ago

How should we provide way to access and test? What about deployment files?

I'm reading the instructions in preparation to submitting my chatbot, and I'm trying to understand what is needed for judging and testing.

"Provide a way to access your bot for judging and testing" - How should we do this? If we are using slack or Facebook, does that mean we need to get it approved by the platform and published to the public just so judges can test it? Or is there a way to provide access for judging in private?

"including a link to your repo hosting the bot code and all deployment files and testing instructions needed for testing your bot." - Link to repo, can do. I read in another thread that testing instructions simply meant ways to use the bot (utterances). But what does "all deployment files" mean? Do we need to write up detailed instructions on building out all the intents, slots, and utterances needed to rebuild the bot entirely? I don't see anyway to export these bot settings from AWS LEX, so what exactly is needed here?

Some clarification would be helpful.

  • 13 comments

  • Manager   •   almost 9 years ago

    Hey Matt,

    Good questions all around. You are not required to make your bot available in a store, though if it is in a store then that's an easy way to share it for testing.

    We require access to your code (public or privately shared repos) and any necessary deployment files in order to run the bot in the platform you chose. You do not need to write up detailed documentation, simply enough for us to take your repo and know how to deploy it to see it in action. The testing instructions we request on the submission form should be clear enough that we know what to do, but do not need to be extensive. You can include some examples of utterances.

    We don't need to be able to rebuild it from scratch, just need to see the code and run the bot on its intended platform.

    I hope this was helpful!
    Stefanie

  •   •   almost 9 years ago

    Hi Stefanie,

    Thanks for clarification.
    Still have some doubts on deplolyment files. Our bot consist of Lex ( intents, slots etc) , one more lambda functions, dynamodb tables and few other AWS resources. Do we need to give cloudformation template or shell script which deploys all these components ?

    Lex is not supported in cloudformation yet. How do we give deployment files for lex resources ?

    Regards,
    Atharva

  •   •   almost 9 years ago

    Atharva's question is the one part I still need clarification on too. Thanks.

  • Manager   •   almost 9 years ago

    Hey there!

    Sorry for the delay. I didn't forget about you. I'm trying to get a clearer answer so I can respond appropriately.

    Thanks for your patience and I'll let you know what I find out!

    Stefanie

  •   •   almost 9 years ago

    Any update? I'm waiting to submit my bot for this information.

  • Manager   •   almost 9 years ago

    Hi Matt & Atharva,
    As you know, Amazon Lex chatbots could be any of the following. You might have more than one, of course.

    * Web sites
    * Mobile Apps (iOS, Android)
    * Messenger (Facebook, Twilio SMS, Slack, Kik, etc.)
    * Phone (Amazon Connect)
    * Other forms we probably haven’t thought of

    To truly judge them, we would need access to a running instance of the bot. Here are the suggestions:

    (1) Code in GitHub/BitBucket as specified
    - Including the output from MobileHub if you used that for a mobile app
    - Including the output from an “export bot” utility ( - we can put a script together for this, if you need it)

    (2) Access to the runtime (since we have to be able to use the bot)
    - For web, it can be a site that requires a password
    - For mobile, we will need the installation media to sideload
    - For messenger, it depends on the messenger, but most should be available publicly
    - For phone, we’d need a phone number to call

    (3) Demo video & testing instructions

    Let us know if/when you need an "export" script.
    In the meantime, these details will be added to the contest instructions!

    Thanks for your patience -

    Vic

  •   •   almost 9 years ago

    Hi Vic,
    Export bot script will really help.

    Regarding runtime access, we deployed messenger on facebook, but it is not a public access. Making it public requires several permissions from facebook. One way is we can create a dummy facebook user and share with judges.

    Any pointers on how do we share access with judges ? Similar question was asked in other thread.

    Thanks,
    Atharva

  • Manager   •   almost 9 years ago

    Hey Atharva,

    If you make a Facebook account for judges to test, you'll be able to enter the login details in the Testing Instructions field on your submission.

    Thanks!
    Stefanie

  •   •   almost 9 years ago

    Hi Vic/Stefanie,

    Can you please provide us the script to export the bot code ?

    Thanks
    Rakesh

  •   •   almost 9 years ago

    Hi, I don't think giving Facebook account for the judges to sign in and test the bot will work though. Facebook will prevent any login from different countries as I remembered.

  •   •   almost 9 years ago

    Hey guys, I found this repo from awslabs that has all the tools you need to export/import your bots.

    https://github.com/awslabs/aws-lex-web-ui#use-or-deploy-my-own-bot

    Pro tip, you need to use python2.7.x when you export as python3.x doesn't handle the dictionary parsing the same way.

    'python lex-manager.py -e BOT_NAME'

    Worked beautifully!

  • Manager   •   almost 9 years ago

    Hi all,
    Instead of waiting on a script, we ask that you submit your code, instructions, and the video that shows the bot in-use and in-action. If you are selected in the top candidates, we'll reach out with the export script.

    Thanks,
    Vic

  • Manager   •   almost 9 years ago

    Hey Chatbot Makers!

    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 testing@devpost.com.
    3. Deployment files or access to a working bot, if possible. (See below)
    4. Testing instructions with anything we need to know to test your bot.
    5. A completed Devpost submission form.

    In some cases, exporting your bot may not be possible. If this is the case and we need to see more than your code and video, we will reach out to you. 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 testing@devpost.com to a Slack channel where the bot is running.

    If you have any questions, please let us know!

    Stefanie

Comments are closed.