Creating A Python Automation Bot

Automation bots are very useful. We can automate all the daily tasks in our life with the use of automation bots. Technologies like Python help make bots easy. In this blog, we will learn how to create a python automation bot.

Content table

1. Why Selenium BOT?
2. What is a BOT?
3. Applications of BOT
4. Creating a simple BOT using live examples.
5. Use Cases
6. Conclusion

You can also check out our video on Automation Bot Using Python

Why Selenium BOT

Selenium BOT is a super fast and easy-to-use chat BOT that can be used to improve customer engagement, increase sales and reduce the cost of service. It instantly builds FAQs for your customers from your website or mobile app content, enabling you to create personalized conversations with each visitor.

• Open Source
• Multi-Language Support (Python, Java, Ruby, JavaScript)
• Multi-Browser Support (Chrome, Firefox, IE, Safari, Opera, Edge)
• Multi-OS support (Linux, Windows, Mac, Android, iOS)
• Reusable
• Flexible
• Easy to Implement
• Good Community

Selenium is a tool designed for automating web browsers programmatically. Selenium’s primary use is for automated software testing. However, it is also commonly used for scraping content, rendering Javascript if necessary, and building any other activity requiring automation in the browser, such as BOTs.

One of the advantages of Selenium is that it supports nearly all popular browsers such as Chrome, Firefox, Safari, Internet Explorer and others. Furthermore, this is accessible through a uniform API that can be used with almost any programming language.

Challenges

1. Mobile number verification:

While creating a new account in Amazon, the login process initiates an Amazon authentication link for authentication purposes. We faced this issue and we needed to manage the link every time that Amazon sends us. This was time taking.

2. AmazonCaptcha:

Amazon checks whether you’re human or bot by showing you a captcha page (also known as a robot check page) when they detect you are rapidly requesting pages in an unusual fashion. We implemented the “Amazoncaptcha” pkg to bypass this verification.

3. User session management: 

Managed users’ login sessions to reduce the time on the login process and improved the shopping experience with quick order placements. 

4. Unwanted pop-up faces on the website:

Some unwanted pop-ups came while purchasing the product like popular products listing ads and recommended products.

Technologies :

Python, Selenium, BeautifulSoup and Amazon Captcha

Use Case 2- Inbox-IT BOT

We had a client, they needed to automate the manual process on their platforms.

Our client had two platforms:

– inbox-it.co(Main Site): It was built using wordpress.

– inboxitads.com(Control Panel): Build using PHP.

• Task was to automate user account creation, so when a user signs up on the main platform, then their account is created automatically on the control panel. 
• Second thing they wanted to do was to automate requests for campaign creation for the user.
• They also had campaign data containing the information about different domain businesses including click time & open time of the email. 

Challenges

• Frequent Changes to the main platform by client: The client was making changes to the main website(platform 1), like response change of the webhook.
• File upload progress: While uploading a file to the control panel(platform 2), the progress bar would get stuck at 35% usually.

Technologies :

 Python, Selenium, Flask, and Pymongo

Boundaries of Selenium test automation

Here are some scenarios where performing Selenium test automation won’t be helpful:

• We need to constantly remind ourselves that automation is to help us save time, money and effort. Suppose any automated script time or execution time is exceeding the time taken to run manually. In that case, the same may not be the best scenario to automate in the real world, unless the automated work reduces the time in the long run effectively.
• Just how exploratory testing is impossible, automating everything is also a bad move in many cases. Prioritizing what tests to automate first and how quickly to integrate the created automated tests to CI-CD pipelines to add value in the development lifecycle is way more important than automating each and every use case in the project.