Early in the
year 2002, David Foster (then at Galton Technologies) invited a group of
IT certification industry representatives to a Performance Testing Summit.
His goal was to increase the validity of IT certification tests and thus
to add value to the process of certification testing across the industry.
On March 14th and 15th, 2002, this invited group met in Park City, Utah, and began brainstorming to explore the barriers that existed to the widespread acceptance of demonstrably valid testing, including performance testing. During those two days, the group came up with a list of barriers spread across some 18 categories.
The group met again in July of 2002, this time with the goal of starting to create solutions for the barriers already noted. As part of this meeting, some categories of barriers were combined and working groups were created to begin the creation of guidelines and best practices, grounded in our collective experience, to transcend the barriers.
In January of 2003 the group met again, this time to bring more structure to the organization. The name "Performance Testing Council" was adopted and further committee work resulting in various documents (available in the Members portion of this web site) that addressing solutions to the barriers delineated in previous meetings.
Meetings since then have focussed on bringing a standardization to the domain of performance testing that is needed so that test developers need not "reinvent the wheel.
On March 14th and 15th, 2002, this invited group met in Park City, Utah, and began brainstorming to explore the barriers that existed to the widespread acceptance of demonstrably valid testing, including performance testing. During those two days, the group came up with a list of barriers spread across some 18 categories.
The group met again in July of 2002, this time with the goal of starting to create solutions for the barriers already noted. As part of this meeting, some categories of barriers were combined and working groups were created to begin the creation of guidelines and best practices, grounded in our collective experience, to transcend the barriers.
In January of 2003 the group met again, this time to bring more structure to the organization. The name "Performance Testing Council" was adopted and further committee work resulting in various documents (available in the Members portion of this web site) that addressing solutions to the barriers delineated in previous meetings.
Meetings since then have focussed on bringing a standardization to the domain of performance testing that is needed so that test developers need not "reinvent the wheel.
