Skip to main content

What topics should we cover if we are planning to appear for an SDET Selenium/Java position (Exp 4-9 years)?


Here are the topics that we should prepare if we are planning to appear for an SDET Selenium/Java position (Exp 4-9 years):


  • Iteration in Java
  • Abstract Class Vs Interface
  • Strings in Java
  • Static Usage in Java
  • Exceptions in Java
  • HashMap in Java
  • Java Annotations
  • Master to Build your own XPATH and CSS
  • Implicit, Explicit and Fluent Waits
  • Handling Frames
  • Data-driven testing using Excel
  • JavaScript Executor
  • Logs Generation (Logging infrastructure with Log4j)
  • Advanced Reporting (Extent, Allure, Klov Report Generation)
  • TestNG Framework
  • Design Pattern (Page Object Model, Fluent, Singleton- Any 1 should be fine)
  • Selenium Grid


And finally:

  • BDD Using Cucumber 
  • Build Management with Maven and/or Gradle
  • Git, GitHub, etc.
  • Continuous Integration with Jenkins, Azure DevOps, Team City, etc. (Any 1 should be fine)

Comments

Popular posts from this blog

How to Unzip files in Selenium (Java)?

1) Using Java (Lengthy way) : Create a utility and use it:>> import java.io.BufferedOutputStream; import org.openqa.selenium.io.Zip; import java.io.File; import java.io.FileInputStream; import java.io.FileOutputStream; import java.io.IOException; import java.util.zip.ZipEntry; import java.util.zip.ZipInputStream;   public class UnzipUtil {     private static final int BUFFER_SIZE = 4096;     public void unzip (String zipFilePath, String destDirectory) throws IOException {         File destDir = new File(destDirectory);         if (!destDir.exists()) {             destDir.mkdir();         }         ZipInputStream zipIn = new ZipInputStream(new FileInputStream(zipFilePath));         ZipEntry entry = zipIn.getNextEntry();         // to iterates over entries in the zip folder         while (en...

The use of Verbose attribute in testNG or POM.xml (maven-surefire-plugin)

At times, we see some weird behavior in your testNG execution and feel that the information displayed is insufficient and would like to see more details. At other times, the output on the console is too verbose and we may want to only see the errors. This is where a verbose attribute can help you- it is used to define the amount of logging to be performed on the console. The verbosity level is 0 to 10, where 10 is most detailed. Once you set it to 10, you'll see that console output will contain information regarding the tests, methods, and listeners, etc. <suite name="Suite" thread-count="5" verbose="10"> Note* You can specify -1 and this will put TestNG in debug mode. The default level is 0. Alternatively, you can set the verbose level through attribute in "maven-surefire-plugin" in pom.xml, as shown in the image. #testNG #automationTesting #verbose # #testAutomation

Encode/Decode the variable/response using Postman itself

We get a lot of use cases where we may have to implement Base64 encoding and/or decoding while building our APIs. And, if you are wondering if it is possible to encode/decode the variable/response using Postman itself or how to encode/decode the token or password in postman and save it in a variable? To Base64 encode/decode, the quickest way is to use JavaScript methods btoa, atob: atob - It turns base64-encoded ASCII data back to binary. btoa - It turns binary data to base64-encoded ASCII. Sample code : var responseBody = pm.response.json(); var parsedPwd = JSON.parse(atob(responseBody.password)); // presuming password is in the payload pm.collectionVariables.set("password", parsedPwd);