Test automation is software development. That means that before you can even start to think about writing and running tests, you'll need to set up a development environment on your machine. This includes completing several steps.
To be able to write and execute code, you'll need an SDK for the language of your choice. So, if you haven't decided on what language you are going to use for the project, this is the moment to do just that.
For most programming languages, setting up the SDK is fairly straightforward. You download the binaries, run an installer or perform the necessary installation instructions, and you should be good to go.
Here are links to official SDK download sites for some of the most popular programming languages:
Well, it depends :) The first and best choice is to ask around in your team or organization to check what version they are using. Then choose that.
If you don't get an answer to that question, your safest bet is to choose the latest LTS (Long-term Support) version for your language.
Test it! Open a new command prompt or terminal and run the command that displays the currently active version of your SDK.
Example: for C#, you can run dotnet --version
.
If that displays the version of the SDK you just installed, you're good to go. If not, fix the problem until it does.
We are not going to write all the code required for our test automation project ourselves. Rather, we will make use of common open-source libraries and tools that were written by other developers for us to use.
To be able to do this, you'll need to configure a tool that can take care of managing these packages for you: the package manager (it's all in the name!).
Most languages include the default package manager with their SDKs. C# / .NET has NuGet, Python has pip and JavaScript / Node.JS has npm. If you use any of these languages, you're good to go.
If you're using Java, there's good and bad news. The good news is: you've got a choice between Maven and Gradle. Both are fine. The bad news is: you need to install and configure those yourself. So do that now, please.
Technically, you can write all your code in Notepad++ or a similar plain text editor. To be an efficient and productive test automation engineer / developer, you'll probably want to use an Integrated Development Environment (IDE). It's basically a text editor for your code on steroids.
There are many, many good IDEs out there, and I am not going to tell you which one to use. Pick what the rest of your team uses, pick what you're comfortable with.
Here are some examples of good IDEs:
Language | Example IDE |
---|---|
Java | IntelliJ, Eclipse |
C# | Visual Studio |
Python | PyCharm |
JavaScript | WebStorm |
And then there's also Visual Studio Code, which is a very good multi-purpose IDE, which means you can use it for every language (given that you install the corresponding plugins).
You have now:
- Set up a Software Development Kit for your language of choice
- Set up the package manager to help you manage tools and libraries for your project
- Set up an IDE to help you write and run code efficiently
Onwards to the next step, where we'll create a new, empty project that is going to contain our tests.