Want to switch from software development to testing domain



  • I have 4 years of experience in software development. But I did software manual testing more than software development. I am good in finding tough functionality related bugs.

    I have passion for software testing rather than software development.

    Please suggest me is it possible to switch in testing domain.



  • It's certainly possible - that's the way I and many others here became testers.

    As Som Ghosh says, you will need to mention in your applications for test positions that you have worked in testing as well as development. I'd suggest you include details of the kind of testing you've done and the scale of the projects that you tested.

    I would recommend that you consider these questions and answer them for yourself:

    • Do you prefer manual testing or automated testing? With your development experience, you will be considered a good fit for automated testing positions and potentially software developer in test positions as well. Some places may not want someone with your development experience in a manual testing role (Note: I do not agree with this view, because in my experience and opinion the development experience helps to isolate problems that non-technical manual testers would have difficulty isolating).
    • Are you willing to take a drop in pay and prestige? This is an unfortunate fact: a lot of places do not treat testers as professionals on par with developers. Tester pay is usually a level or two below developer pay, sometimes more for purely manual testing, and testers are often far below developers in the internal hierarchy when it comes to the equipment they're required to work with (which is "fun" when you as the tester are trying to test software on a system that doesn't meet the minimum requirements for said software. It makes for a potent resource-bound test, but doesn't make the tester's life any easier).
    • Can you advocate for issues you find? This is an important skill that is often overlooked: a tester's role is much more than just finding bugs. A tester needs to give reasons why a bug should be fixed, and to provide managers and leads with enough information to make a good decision about whether software should be released or not. Which leads to:
    • Can you advocate for a release to be delayed? As a tester, you will not be the "quality gate", but you will still have the responsibility to give compelling reasons to delay releases when software your are testing has serious issues. You won't win all these - but you need to have the strength of personality to discuss them with your manager and make sure that your manager knows the risks of releasing in that situation.
    • Can you communicate clearly without giving offense? I've learned in my years testing that what is obvious to me is not necessarily obvious to someone else, and vice versa. If you can communicate with others and tell them their code has problems without offending them, you should be fine.


Suggested Topics

  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2