You could cobble together a Selenium WebDriver framework, one that spun up a browser, identified where the search bar was on Twitter.com, typed in a search keywords, and scraped the screen when the results appeared...
... The problem with this approach? You aren't actually testing the search functionality. You are testing how the web application handles the search functionality. Why not the search functionality itself?
Like the MBTA website we explored back in February, Are You Sure the Bus Line is Listed? Gathering data using REST APIs and REST Assured, much of the data is extracted from an API, an application programming interface.
With this series of blog articles we will be walking through:
1) Setting up a development environment:
- IntelliJ as the integrated development environment (IDE)
- We will be using a programming library called Twitter4J to interact with Twitter's API.
- Since the Test4J programming library is in Java, we will be using that as a programming language.
- Maven handling the third-party dependencies.
3) Searching for that test post we created.
Let's begin!
