Skip to main content

Changes that I saw in Software Testing

Software testing or Quality Control was not a separate department in most of the companies till the year 2000. I never knew that I can turn into a software test engineer or whether there was a career path in the testing stream while I was studying. In the early 2000, Software professional were not interested to move from development to testing. Many of the fresh graduates who joined companies during the 2000-01 time frame very forced to do testing jobs .After the 2001 recession many of the IT Companies started facing competition and quality became one of the key service differentiators. The demand for testing jobs increased during this time and companies started setting up independent testing teams. Anyone who knew how to write test cases or execute test cases got a job. Developers who were not good at coding or logic decided to give a try and many of them failed miserably in testing too. Things went on like this till 2003 after which there was a boom for automation and performance testing. Companies started investing in tools and had planned to automate everything they can. Engineers who have attended basic training on tools and with record/play back experience became automation engineers. In the year 2006 there was a focus on domain knowledge for testers, like a healthcare IT company wanted to recruit testers only with healthcare background. Since there was a huge demand for good testers this move was not very successful. Now I think I have talked enough about the past. What are companies thinking about....most of them wants testers with specialized skills like database testing, security testing, etc?  But do we have right people in our market. ?

Comments

  1. Please participate in this poll to help us understand QA automation better:

    http://polls.linkedin.com/p/70581/lcawa

    ReplyDelete
  2. First of all. Thanks very much for your useful post.

    I just came across your blog and wanted to drop you a note telling you how impressed I was with the information you have posted here.

    Please let me introduce you some info related to this post and I hope that it is useful for software testing community.

    There is a good Software Testing resource site, Have alook

    http://SoftwareTestingNet.com

    simi

    ReplyDelete

Post a Comment

Popular posts from this blog

Quantum Computing Trends

With the advancements in technology, we shifted from traditional computers to its digital version, which included zero’s and one’s and now, to the latest and fastest upgraded computers i.e. Quantum Computers. Built on the pioneering ideas of physicists Richard Feynman and David Deutsch in the 1980s, Quantum Computers leverage the unique properties of matter at nanoscale. Quantum computing uses quantum physics to solve the problems which today’s computers can never tackle. There are two characteristics of quantum computer which make them the computers of the future. First, quantum computing is built on qubits that can be overlays of zero and one i.e. half part of a zero and a half part of a one at the same time. Second, qubits become entangled and exist in groups. Because of its capability to solve problems, high speed and accuracy, quantum computing has immediate applications in fields like pharmaceutical, cryptography, machine learning and search. Realizing the pot...

TDD BDD and SDET REsume

 **TDD vs BDD** Test-Driven Development (TDD) and Behavior-Driven Development (BDD) are both agile methodologies but with distinct focuses and processes. TDD vs BDD a developer-centric practice, emphasizes writing tests before the actual code, guiding software development through small, testable chunks. It's particularly effective in ensuring that the codebase remains bug-free and maintainable. BDD, on the other hand, extends TDD by specifying software behaviors using a language understandable by all stakeholders, including non-technical ones. This approach fosters collaboration and a shared understanding of the project's goals, making it easier to align development with customer needs and expectations. While TDD is focused on the technical aspects and validation of software functionality, BDD is more about clear communication and the behavior of the application from the user's perspective. **SDET Resume** An SDET Resume should effectively showcase a blend of software dev...

7 Software Testing Books Worth Reading!