Software Testers - Past, Present and Future

Software Testers - Past, Present and Future


Early during the last decade, software development companies were producing applications by the bucket-load to keep up with the incredible customer demand. The role of the Software Tester then, was to (in my opinion) detect the critical and major issues, and most minor issues were simply brushed under the carpet to get the product out of the door on time. For the Software Testers, it was (to coin a phrase) "A much simpler time". During this time-frame the Software Testers actively working hard to get themselves recognized as a necessary part of the software development process, and not just some kind of 'bottle-neck' that delays a products release. Credit to the testers for actually achieving that goal!

Having worked so hard to achieve their aim, Software Testers found themselves under threat, a threat which in a way came from inside their own camp. The threat I am talking about was 'Test Automation'. Loose talk around the offices focused on how 'so much more useful' this kind of testing was. Testing could be ran 24 hours a day and repeated many times faster than a manual tester could perform. The humble Software testers were considered a dying breed. But, hang on a minute.....we are still here!

Rather than migrating the manual testing over to automated testing entirely. The move was actually more of a 'leaning' instead. A typical software development company will include only 'some' automated testing. Just tests where automation would enhance the manual testing or save a bit of time. Some testers have switched over to becoming devoted to test automation and that is now their primary job.

So while the road of a Software Tester has been 'uneven' to say the least. They have in fact, now firmly established their role as a necessary part of the software development cycle. Once considered to 'dying out', the Software Testers have not only 'beaten' the threat of test automation, but actively use it alongside their own work to assist it and to enhance it.

So what it is store for the future of Software Testers? Well, software is still going strong and is now present on other platforms. The most popular 'new' platform has to be the 'iPhone'. It pretty much came from nowhere and has now topped 250,000 Apps that have been developed. These iPhone Apps are just regular software applications designed to work on a specific type of hardware. Many software testers are realizing that their software testing skills can be transferred over to this new kind of software development, and are becoming iPhone App Testers. There now exists iPhone App testing companies that are dedicated to providing iPhone App Testers to improve the quality of this rapidly growing phenomenon.

The future looks bright for Software Testers and iPhone App Testers alike, and that's good news for the people who want quality from the software they are using, whether its a PC application, web application or an iPhone App.


Author: James S Clark
Source: Link

Comments

Post a Comment

Popular posts from this blog

What is LCSAJ Testing?

Image
LCSAJ testing requires a model of the source code which identifies control flow jumps (where control flow does not pass to a sequential statement). An LCSAJ (Linear Code Sequence and Jump) is defined by a triple, conventionally identified by line numbers in a source code listing: the start of the linear code sequence, the end of the linear code sequence, and the target line to which control flow is transferred. Test cases shall be designed to exercise LCSAJs. For each test case, the following shall be specified: - the input(s) to the component; - identification of the LCSAJ(s) to be executed by the test case; - the expected outcome of the test case.
Read more

ISEB-ISTQB Sample Exam Paper 12

Image
1. Which of the following statements contains the correct use of the terminology? a) a fault by a person may introduce an error into the software that may cause a failure in operation b) a failure by a person may introduce a fault into the software that may cause an error in operation c) an error made by a person may introduce a fault into the software that may cause a failure in operation d) an error made by a person may introduce a failure into the software that may cause a fault in operation e) a failure by a person may cause an error in the software that may cause a fault in operation 2.   A reliable system will be one that: a) is unlikely to be completed on schedule b) is unlikely to cause a failure c) is likely to be fault-free d) is likely to be liked by the users e) includes a minimum number of components 3.   Which of the following statements about ‘Integration Testing in the Small’ is false? a) It can combine all the components ...
Read more

What is State Transition Testing?

Image
State transition testing uses a model of the states the component may occupy, the transitions between those states, the events which cause those transitions, and the actions which may result from those transitions. The model shall comprise states, transitions, events, actions and their relationships.   The states of the model shall be disjoint, identifiable and finite in number.   Events cause transitions between states, and transitions can return to the same state where they began.   Events will be caused by inputs to the component, and actions in the state transition model may cause outputs from the component. The model will typically be represented as a state transition diagram, state transition model, or a state table. Test cases shall be designed to exercise transitions between states.   A test case may exercise any number of transitions.   For each test case, the following shall be specified: -   the starting state of the component  ...
Read more