DevBistro is a major peer review article website that owns the right to several peer reviewed articles and journals. In this paper I summarize the article and offer opinions about the selected topics as well as give clarification of research findings in the article that would aid in the understanding on the topic of testing in operational product line.
Article summary
The article depicts the role of the test manager and what is expected in terms of his or her roles as well as responsibilities in the implementation of a testing process. The author further states that the success of the process would entail the development of a sound infrastructure that facilitates robust communication that is not only cost effective but also efficient in carrying out tests.
The article also provides for methods that address the prevention of defects. It points out testing verification and validation entails two facets. This, the author points that the meaning are always looked from different perspectives. However the article breaks the down to those tests that re undertaken before the product construction and those that are carried out after the building of the product. To illustrate this notion, the article makes it clear that testing before the product is constructed is critical in preventing the occurrence of defects. This is seconded by providing several cost effective methods which the author shows preference for product reviews which the article states can either be technical or peer based review.
The author further promotes the notion that testing organizations are capable of detecting software defects after the product or some of its operational units have been delivered. However the article further illustrates that this is only dependent on product maturity at present which follows a multi-level sequences which includes: design review, unit testing, system testing and user acceptance testing.
The author further stresses out that defect are the most useful deliverables the testing unit keeps. The reason for this as the article pits it is due to the fact that defects are seen as the only product that the testing teams have an in-depth understanding by the project wholly. The article also points out its relevance as it is where the system errors can be noted and followed through. However the article requires that each facet should at least have a name, description, severity description, author and status. This is fundamental in providing the minimal set of metrics.
Conclusion
The growing concern of the author though is centered on the running and management of testing teams which he personally considers a challenging venture in the information technology world. This the author stresses is plagued by the lack of adequate staff, insufficient tools and strained financial resources. The author further advices that the motivation as well as retention of core testing personnel be critically observed in the case that these circumstances occur.
The author through the article further pegs that its achievement will heavily rely on the appropriate modifications of test plans in terms of scope of and the affected timelines. Emphasis is also placed on the clear definition of each member as well as their respective career path.
References
DevBistro. (2011). Testing & The Role of a Test Lead / Manager . Retrieved May 20, 2012, from DevBistro: http://www.devbistro.com/articles/Testing/Role-of-Test-Lead-Manager
