What a QA role in TestVagrant looks like?

Disclaimer: Not a post to promote my Org. Read it if you want to understand what we do at TestVagrant and what you can expect from your career as a QA here.
Almost 4 years back we created the company called TestVagrant and the prime intention was to make testing very intelligent and innovative. We want to make testing lean, more efficient, foster intelligence in solution which we owned and built. We wanted to challenge the assumptions of the testing and create something which is more intuitive and value addition to the software development process. And this happens when you own the design when you can influence it and change it based on the knowledge and skill you have acquired over a period of time.
End of the day we wanted everyone to believe in the work they are doing, enjoy the work, experiment with what they are learning and have the courage to question the status quo and above all feel free to implement their ideas. We code to test and make testing faster and accurate.
Generally, the shackles of enterprise company (and deep funded startup which operates like enterprise) are so strong that the majority of the QA is hired to do the job of pattern following and not really challenge the pattern (refers to the existing solution). The reason could be long and various, some worth listing here is:
  • environment and culture is not open for the change
  • process and practice which prevents people to bring change and new ideas
  • no risk appetite of the leaders at the various level
We wanted to be a tech company specialized in Testing where we work on “hard to solve” QA problems with our coaching and excellent tech skills. We custom develop testing solutions for companies who want to “go to market” faster with exceptionally high quality.
Who should work with us? 
We want designers in testing (passionate coders in the testing world) who take pride in building the test solution from scratch, willing to make it fail-safe, willing to learn a new programming language and come out of comfort zone to experiment something new and radical. If you are looking to work in your comfort zone (or let’s say just Java, Selenium, Appium etc.) then I am afraid TestVagrant may not be the right place for you. We want testers who want to push the limits of testing to fasten the entire software development process and keep the app quality exceptionally high. We strongly believe that the goal of QA is to release software products with acceptable quality. We help the company accelerate the time to market with intelligent and innovative testing solutions and techniques.
If this excites you then drop in your resume to career@testvagrant.com and we would love to take it forward from there.
 
 
 
 
Happy Reading ! 
 

Comments

Post a Comment

Your comments will be reviewed and then published !

Popular posts from this blog

Defect Tracking System – Wastage of Money & Time ???

Image
As a QA I have been logging bugs since 5 years. But what do we do with that ? A typical flow: If this is the only thing we need to do then why taking so much of pain to have a defect tracking system . To log a standard bug (Standard Bug= Broken Functionality), we need to write steps to reproduce, pre-requisites (if any), expected result, actual result, priority, severity, snapshot (if any), Test environment details and finally save it. This takes around roughly 3-5 minutes to log a bug. To say truth, I have never seen any report coming out of defect tracking system which is of use in analyzing the pattern of bug or finding out any trend in them. All I have seen apart from tracking usage, is the summary of bugs with count based on Priority and Severity. Is that the only purpose of Defect Tracking System? If that is the case then why not use a Google spreadsheet rather then investing money of the company and time of QA in a bug logging system. I am sure if we mine the data which i
Read More »

The 3 qualities that will always help you become better at almost anything…

Image
Have we ever noticed how excited we are when we start anything? But it’s a sad fact that 70% of people abandon what they have started with so much energy and love. It could be as small as building a hobby or starting a pet project or even an activity or a side learning we started. “ Well begun is half done .” Aristotle did say this but we are judged for how we have finished something. You separate yourself fro m  the masses when you choose to give that task a finish.  The first quality is finishing off what you started and it helps develop mental stamina or willpower.   It builds confidence and inculcates as a habit in a long run. You don’t need to sign up for the mammoth activity to build this habit, even finishing mundane day-to-day routine tasks will help. Diligence — the quality of working carefully and with a lot of effort Diligence is a quality that almost never will get unnoticed. It’s one of the underlying traits of great works or success. The key to mediocrity on the o
Read More »

Test Case Paths : Happy, Sad & Bad

Image
I came back from the background of writing test cases which were categorized in either Positive or Negative test cases. Positive test cases were business flows which may or may not give any result but they will certainly not give any exception or error. Negative test cases are those test cases which were bound to result into some exception or better expressed as error causing scenarios.  Then those positive test cases were prioritized as High/Medium/Low . Finally it used to result in quite a comprehensive test case document. Then it will go through the process of review and few more updates or change of priority etc. Certainly it is a tedious process. Here in ThoughtWorks I got introduced to different way of categorizing test cases called “ Happy/Sad/Bad ”. A test case which results you in a positive result is a Happy path , for e.g. entering proper username and password on login page. A test case which yields no result like entering invalid username and invalid password on a logi
Read More »