Skip to main content

So why did you write "this" certificate?

This is going to be an eternal post which I would modify as and when I find new reasons for writing certificates.
Though I personally don't admire certificates but happened to write one (QC 9.2) on my own. This happened last year when I was told about a project which needed experience on QC and client had asked have QC certified resource working on it. Well exam was really easy and I happen to clear it. Irony is project never materialized and I never got to work on QC. Happened to mention about certification on my resume and under the influence of this group removed it.

Of late I have been interviewing testing candidates and a few of them have certification batch with them. And we all know most famous certification batch in market is ISTQB (I must appreciate their marketing for sure and hope they contribute a share of their earnings to some open source testing projects. Though I am not very hopeful of this.).

I am listing here the responses I receive from the candidates -
  1. One candidate having more than 2 years of  experience said - "I wanted to learn testing concepts". My response - "So you were not aware of testing concepts for past two years". I can't recall the response of Candidate.
  2. One candidate said - "I have written foundation level exam for ISTQB". My question - "So what did you learn?". Candidate - "Nothing much but I am planning to write advance level and would definitely learn from it." !@#!@#!@#!$@$$!@
  3. Another candidate said - "Certification fetches you better salary", I can only imagine how much money I have lost so far.
This is an incomplete blog and would update this when I receive new answers.

Comments

Popular posts from this blog

How can you save resources when instantiaing driver?

I asked on my previous post about what was wrong in instantiating driver on set up method? And here is the solution video on my YouTube channel (After 5 years of gap I finally added new video tutorial :)) The solution described on video tutorial uses following set up - public class BaseClassOnDemandDriverSetup { private WebDriver driver ; @BeforeMethod public void setupTest () { // Any other set up goes here } @AfterMethod public void teardown () { if ( driver != null ) { driver .quit() ; } } public WebDriver getDriver () { if ( driver == null ) { WebDriverManager. chromedriver ().setup() ; driver = new ChromeDriver() ; } return driver ; } }

Security Testing and Selenium

I have come across many articles which talk of carrying out security testing with selenium however I found it very cumbersome to set up such tests. This is what this tutorial is going to make easy for you. It cover. My next Security Testing and Selenium YouTube video covers following - Importance of having security testing on CI What is dynamic application security testing Recommended tools from https://owasp.org/www-community/Vulnerability_Scanning_Tools What is https://owasp.org/ ?   Using https://www.zaproxy.org/    Project setup  <dependency> <groupId> org.zaproxy </groupId> <artifactId> zap-clientapi </artifactId> <version> 1.9.0 </version> </dependency> <dependency> <groupId> org.zaproxy </groupId> <artifactId> zap </artifactId> <version> 2.10.0 </version> </dependency> Start ZAP daemom (headless) mode  ./zap.sh -daemon -host 127.0.0.1 -port 8080 -config api.addrs.a

Using chrome console to test xPath and css selectors

Since the advent of selenium there have been many plugin to test xPath / css selectors but you don’t need any of them if you have chrome browser. Using Chrome console you can test both xPath and css selectors. Launch website to be tested in chrome browser and hit F-12 and you would see chrome console opened in lower pane of application - Hit escape key and console would open another pane to write element locators - And now you can start writing xPath or css selectors in chrome console and test them - The syntax for writing css id - $$(“ ”) And hit the enter key. If your expression is right then html snippet of the application element corresponding to the css selector would be displayed - If you mouse over the html snippet in chrome console then it would highlight the corresponding element in application - If you want to clean console of previously written element selectors then just hit ctrl+L keys and chrome console would be empty again. Pro