Skip to main content

So what did testing certificate yield me

I was being asked to write CSTE since almost commencement of my career. There was one extremely diligent (and I mean it) manager with my previous employer who would always ask us to write CSTE or some other testing certificate.
And I always showed my reluctance towards it. Not because I have any grudge against CSTE (though have extreme grudge against ISTQB) but I have not seen any relation between certificate and testing competency.
I have worked with

  • Exceptional testers without certificate
  • Exceptional testers with certificate
  • Unexceptional testers without  certificate
  • Unexceptional testers with certificate

I could never drew any conclusion between testing competency and certificate.

Back to my manager and I. Soon I confronted a condition. I could get to work on my new assignment only if I wrote QC-9.2, client imposition.
I was darn bored of not having association with any project and decided to write this certificate. Those days it was 9.2, must be 10+ now.
It was hardly any study for 1 week, questions were objective and I easily cleared the exam. And so as anyone else with little brain and time in hand.
So did I get to work for the project? No, project never move beyond pipe line and I was employed in another project working on TestComplete for testing winform application. And yes this time without writing any certification.

Now back to CSTE, we were asked to write CSTE mandatorily. It was as if, more experienced you are more certificates you are ought to have in your profile.
Seeing my past experience I was more reluctant than ever to write any more certificate.
Same diligent manager was promoted as senior manager then associate vice president and then vice president and I still did not write the certificate.

Same manager is not there with my previous employer and I am also working in a new org and yet I am not a certified tester. I am glad that my new job is never going to force me to write any certificate.
And if you have not read this yet then do it first in your leisure time -
I also remember a post on decertifying yourself, though can't Google it now.


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 What is ?   Using    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  ./ -daemon -host -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