Recent Software Testing Techniques
What are the recent software testing technique? can some1 explain briefly the recent software testing techniques and where all it can be applied and how to use ?
Do you mean tools, software, management? What do you mean by testing technique?
If it is interview question... then most probably want to know abt agile, tdd, bdd etc
It is not an interview question, actually i wanted know about the different testing techniques, like Black box testing , white box testing etc, but there are lot of new techniques which are coming in the industries recently like fuzz testing and all, i hope u understand my question now, please let me know if there are any such,
My favorite buzzword is lights out testing. I think it means scripts that run after everyone leaves work for the day.
I can't really say there's something that crazy new, but there seems to be an overall trend of testing becoming more closer integrated with engineering and further away from the business end.
In the past, QA was part of a Business Analyst Units, where they never saw code delivered until they had a beta or release candidate. Now we have a growing trend of Test First
Development, and Continuous Delivery. This brings some interesting new process improvements to the table.
* With modern programming frameworks, less time is spent writing code, and more time is spent writing requirements/tests. For example, it's not unusual of new agile shops to spend 2/3rds of an entire sprint just doing planning and design and only a 1/5th of the sprint doing coding. (so that's about for every week, 3 days of meetings and writing tests cases as a group, 1 day of coding, and 1 day of testing and refactoring)
* Test cases are becoming first class citizens in artifacts created. In the past, test cases were created after requirements docs. But with more time spent in planning, it's becoming more and more common for test cases themselves to be requirements. Some Agile shops are now writing their stories in the form of test cases instead of user story format. This allows test cases to always stay up to date, and developers to have a clear criteria of what the definition of done is, including all error scenarios (which are normally missed by high level user stories)
* CI is the buzz word. Getting more things automated, and getting the automation to run as early as possible. One of the big causes of bad code is other people pulling bad code and building on it, making the problem worse. So most new software development will have a CI system setup to run as many tests as possible upon code check-in, and automatically reject bad code to prevent it from reaching the master branch or trunk.