The Maiden Things You Need To Know

Selenium is really full at a specific set of things. If you cognize what those are and stick to them then you will be able to easily write reliable, scalable, and maintainable tests that you and your team can rely.

But before we dig in, there are a few things you & # x27; ll want to cognize before you write your first test.

Define a Test Strategy

A great way to increase your chances of automated web prove success is to focus your efforts by mapping out a test strategy. The better way to do that is to reply four questions:

1. How perform your business make money (or render value for the end-user)?

2. How do your users use your application?

3. What browsers are your users using?

4. What things have broken in the covering before?

After answering these, you will receive a good understanding of the functionality and browser that matter most for the covering you are screen. This will help you narrow down your initial efforts to the things that matter most.

From the result you should be capable to progress a prioritized list (or backlog) of critical business functionality, a little list of the browser to concenter on, and include the wild parts of your application to catch out for. This prioritized list will help you make sure you & # x27; re on the correct path (e.g., focusing on thing that matter for the concern and its users).

Pro tip: Tools like SUSA can handle this autonomously — upload your app and get results without writing a single test script.

Pick a Programming Language

In order to act good with Selenium, you need to choose a programming language to write your acceptance tests in. Conventional wisdom will tell you to choose the same language as what the coating is written in. That way if you get stuck you can ask the developers on your squad for help. But if you & # x27; re not proficient in this words (or new to ontogeny), then your progression will be slow and you & # x27; ll likely end up asking for more developer help than they have time for -- hindering your mechanization efforts and setting you up for failure.

A great way to determine which language to go with is to answer one mere question: Who will own the automated tests?

Also, as you are considering which language to go with, consider what open source frameworks already subsist for the languages you & # x27; re eyeing. Going with one will save you a lot of time and give you a horde of functionality out of the box that you would differently have to progress and keep yourself -- and it & # x27; s FREE.

You can see a list of available open source Selenium frameworkshere.

Choosing a programming language for automated testing is not a conclusion that should be taken softly. If you & # x27; re simply starting out (or seem to port your tests) then considering and discussing these things will help perspective you for long term success.

For this course we & # x27; ll be using the Java programming language. If you want help installing Java, then check out one of the following links:

• Linux

• Mac

• Windows

Choose an Editor

In order to be productive when writing Java code, you will need to use an merged development environment (IDE). Here are some of the more popular single:

• Eclipse

• IntelliJ

Download the eBook

To access the balance of the bootcamp series,.