About Test Focus
Many wish for excellence, but few work for it as they are not prepared to make the necessary sacrifices.
Why use a team instead of a high performance coach, mentor, or consultant
Who should be interested?
The common theme in examining their achievements is that a strong vision, a long journey, hard work, a few intermediate setbacks, and many successes were necessary to bring them to this point who have attained excellence.
Test Focus, Volume 12 Number 3, 3rd Quarter 2011
We all from time-to-time notice leaders, business persons, celebrities, or
For a testing centre to survive and flourish, the following environmental
- A testing centre of excellence will operate best in companies that are mature enough
- Willingness to measure
- Accept the challenges of attaining excellence
Each of these critical aspects is best supported by a team
- What’s On - Events
- Book Reviews
- Testing Fun
Last modified: June 21, 2016
This Site is best viewed at 1024X768 resolution.
Hiring for effective test teams
I had to put together a test team which made me think about the types of people required and their roles. It’s hard to judge how a candidate will behave in a team during an interview. In future, I will require candidates to take a test to gain insight into their personalities. It can be very easy in a mad rush to fill seats on a test project and to lose sight of the fact that people’s characters can be used as tools for optimum performance. I,ve found that with a little patience and many more interviews, there is always someone better suited than the last person. Disclaimer: I write from personal experience, I’m not formally educated in social, behavioural or human sciences. I will use the words character, nature and personality interchangeably without consideration for the finer differences, as described by above-mentioned fields of study.
This is an over-arching classification and all the personality types can exist in any of the classes. The empirical description of an A-class tester is someone with a passion for testing. They are self-driven, motivated, and do everything they can to further their understanding of testing. They will stick with trusted industry practices when there is chaos, simply because they have experience of the practice adding value. They will try new things in an attempt to better their work. An A-class tester may be driven by career aspirations or a real, consuming interest in testing. A B-class tester doesn’t have the passion of the A-class tester, but he delivers nonetheless. They are competent, reliable team members, with value to add, and a genuine interest in what they do. With the correct leadership they can be inspired into A-class testerhood. This group is often in testing by accident, or because of career growth decisions within an organisation. Coming into testing from a business super-user function, soon to leave testing for a middle management position, or to become a business analyst. The description for these individuals is just-passing-through. It takes extreme commitment and a strong will for this class of tester to become A-class testers.
I want to refer to an article by Lloyd Roden of Grove Consultants. Lloyd discussed 4 types of testers, knowing your team in this framework, and how to get the best out of your team. Included in the article is a test questionnaire to help classify team members it is done after the style of the DISC profile. It is focused on finding good candidates while sifting through resumés. She also wrote an outstanding piece on the classes of testers that I discussed. She has more interesting resources on her blog, including a very clever interview question for testers. Comments, remarks, opinions, and critique in this piece are expressly the view of the author of the piece, and do not necessarily reflect those of the editorial board of Test Focus, its staff or its publishers.
Things like integrity, honesty and responsibility cannot be determined by any of these tests. It’s likely that no person will fall a 100 % into any pigeonhole. There are grey areas, borderline cases and overlaps. If you keep these profiles in mind while selecting team members, know what you are looking for and do some sort of test, the difference in results can be remarkable.
Software testing methods and tools
Every product ever manufactured has to be tested to make sure that it is fit for purpose. Various testing methodologies are used to test the products and these approaches and strategies are focused on verifying if the product works accordingly to its specification. Here is everything you need to know about software testing and the strategies used for testing it.
Testing methodologies and its importance
These testing methodologies are in fact a series of approaches that are meant to ensure is the software application is functional and that it will not lead to side effects. It will be tested in various ways for everything – if it fails, it has to be in a safe way. These methodologies include everything from unit testing individual modules to checking the entire system for performance, security and everything else.
There are actually two times of testing: non-functional testing and functional testing. If the non-functional testing includes methodologies for usability, performance, compatibility and security testing, the functional testing refers to testing of system, unit, integration and acceptance. Whenever a software is tested, thorough investigations are made and each factor or component has to be fully tested and checked.
Many tools were developed in order to test software applications. Because the software projects today are considerably more complex than several years before, the testing tools are rapidly changing and improving to meet the specified requirements. Even platforms and software applications used for people are rigorously checked to function properly and successfully operate in all the anticipated environments.
Quality from the beginning
Any software is meant to be tested manually and automatically. Some manufacturers also use exploratory software testing methods, but most of them might put under question why does it have to implement unit and integration tests, when there are some methodologies for functionality that test the entire system. The answer is that if these procedures are undertaken, the speed of recovery and performance will also be tested.
Software testing is not as expensive as some people would say. In fact, testing early software applications and detecting errors even since their development will help reducing some costs. The manufacturer will not have to pay more for maintenance or correction and they will also avoid resulting in improper design of their software application. Although some of these methodologies are time-consuming, they represent a productivity activity with countless benefits in the future.
Due to the fact testing depends on the source code, not all fully-developed products are tested. Developing test cases and reviewing requirements are independent from the developed code, yet certain testing methodologies can be used in this case, too. Incremental or iterative approach as a development life cycle model will help reduce this incidence and test the software even though it was not fully developed.
Although the management team, project managers and even clients are convinced that their software is bug-free, nobody can guarantee that the application is 100% bug-free. Even when the best professionals used their most capable testing skills, some issues can appear. Despite all of these, using the software testing methods will prove to be extremely beneficial for both the manufacturer and client.