Talk:Test management tool

	This article is within the scope of WikiProject Computing, a collaborative effort to improve the coverage of computers, computing, and information technology on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.ComputingWikipedia:WikiProject ComputingTemplate:WikiProject ComputingComputing
Low	This article has been rated as Low-importance on the project's importance scale.
	This article is supported by WikiProject Software (assessed as Mid-importance).

List of notable test management tools

Indeed, as it is said in the article comments, the Wikipedia is not a listing service. Even with this in mind I truly believe people would get more out of this page if the list would be extensive. Surprisingly many people working on IT do not know about exactly what test management softwares do, but would like to, and gathering information about them is a lot easier with a list. This is because their approach to testing is usually bit different. TimoPulkkinen (talk) 11:05, 24 September 2013 (UTC)[reply]

And you think by creating a link farm here that more people working in IT will know what test management software does? I think that if we expand the article they will know what it does. That in turn may increase the interest in such tools. That increased interest may increase the notability of individual tools. That in turn should result in their inclusion on Wikipedia and then we can link them here.

We may discuss the different approaches provided that the discussion is verifiable. Walter Görlitz (talk) 13:49, 24 September 2013 (UTC)[reply]

I agree that concentrating on the list of tools is not the correct approach. I think, if the list is an addition to a good text, it helps many readers to understand the area and the actual tools better. Anyway, I will next concentrate on the text about test management tools and after that we can discuss if some additions to the list would have positive effect to the page. TimoPulkkinen (talk) 06:25, 26 September 2013 (UTC)[reply]

If we want to list tools that fail WP:N, then at least we should have independent sources demonstrating they are worth noting at all. --Ronz (talk) 19:30, 12 June 2014 (UTC)[reply]

Fully agree. One step at a time though. We should start by tagging them with {{Better source}} to start with. Walter Görlitz (talk) 19:55, 12 June 2014 (UTC)[reply]

Thanks! I trust your judgement. I just came here cleaning up after 2A02:1810:B881:BF00:F8F7:2AF1:E7E9:E55 (talk · contribs) and didn't notice [1]. --Ronz (talk) 20:01, 12 June 2014 (UTC)[reply]

For my company i had to search over many months for a tool that has the feature to execute tests offline (and sync later). We finally found one tool with this feature. So i would like to add aqua to the list, since this feature might be of a use for many people who are not only testing software.--DonPromillo7 (talk) 09:32, 1 October 2014 (UTC)[reply]

I have added aqua to the list, but i did not find a better reference than the product homepage. So i also added the "better citation needed". If anyone has a better source that would be nice. --DonPromillo7 (talk) 09:42, 1 October 2014 (UTC)[reply]

I've added Rainforest QA to the list of tools, along with a few cites from different sources. I noted on my edit that in full disclosure, I'm on of the co-founders. Rhs98 (talk) 20:36, 8 October 2014 (UTC)[reply]

This edit request by an editor with a conflict of interest was declined. A reviewer felt that this edit would not improve the article.

Hello, my name is Patricia Wagner and I'm an employee of Microsoft. I work in the Cloud+Enterprise division as a content publisher for Visual Studio Team Services, Team Foundation Server, and Application Lifecycle Management products. We are reviewing Wikipedia articles that relate to our areas and would like to update some to better represent the current state and features of our products. Please review the changes below and let me know if they are acceptable to you. Thank you very much for your consideration. We are suggesting these edits to: Update current row for Microsoft Test Manager. Add a new row for Team Foundation Server and Visual Studio Team Services (new) because they have test capabilities that don’t require Test Manager. Update product names and versions. Fix typo in "Team Foundation Serve". Propose friendlier tone to replace “formal speak”. Propose replacing “interface” to describe Test Manager, which is just a tool that “works with” TFS and Team Services. Clarified ambiguous pronouns. Added links to existing Wikipedia pages and sections. Product Creator License Automated unit tests Automated GUI tests Manual tests Defect management Launch date Additional comments Refs Microsoft Test Manager Microsoft proprietary Yes Yes Yes Yes 2010 Microsoft Test Manager is included with Visual Studio Test Professional 2010 - 2015, Visual Studio Ultimate 2010 - 2013, and Visual Studio Enterprise 2015. Test Manager works with features in Team Foundation Server (TFS) and Visual Studio Team Services, and so requires TFS or Team Services. Test Manager supports these testing activities: exploratory testing, test management: test planning, test case generation, manual testing, test automation, integration with build servers for continuous integration and continuous delivery, bug creation and tracking, test results reporting, automated testing in parallel on multiple computers, plus setting up and managing environments. (Visual Studio Lab Management) Team Foundation Server Microsoft proprietary/SaaS Yes Yes Yes Yes 2005 / 2013 Team Foundation Server (TFS) supports these testing activities: test case creation, test management, manual testing, test automation, including automated execution during builds and releases for continuous integration and continuous delivery, and also testing in parallel on multiple computers bug creation and tracking, test results reporting, and automated testing in parallel on multiple computers. Visual Studio Team Services supports these activities as cloud services, plus web performance and load testing.

In the "Microsoft Test Manager" row, In the "Additional comments" column, please use these links for the following link text: Visual Studio Test Professional [1] Visual Studio Ultimate 2010: <ref<https://en.wikipedia.org/wiki/Microsoft_Visual_Studio#Visual_Studio_Ultimate_2010</ref> Team Foundation Server: [2] Visual Studio Team Services: [3] exploratory testing: [4] test management: [5] test planning: [6] test case: [7] manual testing: [8] test automation: [9] continuous integration: [10] continuous delivery: [11] Visual Studio Lab Management: [12]

In the "Ref" column, please insert this reference, which will be [14]: "Difference Between Microsoft Test Manager and Visual Studio Test Professional". [13]

In the new row for "Team Foundation Server and Visual Studio Team Services," in the "Additional comments" column, please use these links for the following link text: Team Foundation Server: [14] test case: [15] test management: [16] manual testing: [17] test automation: [18] continuous integration: [19] continuous delivery: [20] Visual Studio Team Services: [21] load testing: [22]

In the "Ref" column, please insert this reference, which will be [31]: "Visual Studio 2015 – Web-Based Test Case Management with TFS" [23] Thank you very much. Pat MSFT (talk) 18:43, 14 March 2016 (UTC) You need to put the above on the Article's Talk Page, not your talk page. I've deactiveted the template. Ronhjones (Talk) 19:49, 15 April 2016 (UTC)

Hi there. The request is quite outdated, and the information proposed seems to be now present in the article, albeit compressed into 1 row instead of 2. Closing the edit request. Regards, VB00 (talk) 09:33, 31 December 2016 (UTC)[reply]

References

Microsoft requesting edits

Hello, my name is Patricia Wagner and I'm an employee of Microsoft. I work in the Cloud+Enterprise division as a content publisher for Visual Studio Team Services, Team Foundation Server, and Application Lifecycle Management products. We are reviewing Wikipedia articles that relate to our areas and would like to update some to better represent the current state and features of our products. Please review the changes below and let me know if they are acceptable to you. Thank you very much for your consideration.

We are suggesting these edits to:

Update current row for Microsoft Test Manager.
Add a new row for Team Foundation Server and Visual Studio Team Services (new) because they have test capabilities that don’t require Test Manager.
Update product names and versions.
Fix typo in "Team Foundation Serve".
Propose friendlier tone to replace “formal speak”.
Propose replacing “interface” to describe Test Manager, which is just a tool that “works with” TFS and Team Services.
Clarified ambiguous pronouns.
Added links to existing Wikipedia pages and sections.

Product	Creator	License	Automated unit tests	Automated GUI tests	Manual tests	Defect management	Launch date	Additional comments	Refs
Microsoft Test Manager	Microsoft	proprietary	Yes	Yes	Yes	Yes	2010	Microsoft Test Manager is included with Visual Studio Test Professional 2010 - 2015, Visual Studio Ultimate 2010 - 2013, and Visual Studio Enterprise 2015. Test Manager works with features in Team Foundation Server (TFS) and Visual Studio Team Services, and so requires TFS or Team Services. Test Manager supports these testing activities: exploratory testing, test management: test planning, test case generation, manual testing, test automation, integration with build servers for continuous integration and continuous delivery, bug creation and tracking, test results reporting, automated testing in parallel on multiple computers, plus setting up and managing environments. (Visual Studio Lab Management)
Team Foundation Server	Microsoft	proprietary/SaaS	Yes	Yes	Yes	Yes	2005 / 2013	Team Foundation Server (TFS) supports these testing activities: test case creation, test management, manual testing, test automation, including automated execution during builds and releases for continuous integration and continuous delivery, and also testing in parallel on multiple computers bug creation and tracking, test results reporting, and automated testing in parallel on multiple computers. Visual Studio Team Services supports these activities as cloud services, plus web performance and load testing.

In the "Microsoft Test Manager" row, In the "Additional comments" column, please use these links for the following link text:
Visual Studio Test Professional ^[1]
Visual Studio Ultimate 2010: <ref<https://en.wikipedia.org/wiki/Microsoft_Visual_Studio#Visual_Studio_Ultimate_2010</ref>
Team Foundation Server: ^[2]
Visual Studio Team Services: ^[3]
exploratory testing: ^[4]
test management: ^[5]
test planning: ^[6]
test case: ^[7]
manual testing: ^[8]
test automation: ^[9]
continuous integration: ^[10]
continuous delivery: ^[11]
Visual Studio Lab Management: ^[12]

In the "Ref" column, please insert this reference, which will be [14]: "Difference Between Microsoft Test Manager and Visual Studio Test Professional". ^[13]

In the new row for "Team Foundation Server and Visual Studio Team Services," in the "Additional comments" column, please use these links for the following link text:
Team Foundation Server: ^[14]
test case: ^[15]
test management: ^[16]
manual testing: ^[17]
test automation: ^[18]
continuous integration: ^[19]
continuous delivery: ^[20]
Visual Studio Team Services: ^[21] load testing: ^[22]

In the "Ref" column, please insert this reference, which will be [31]: "Visual Studio 2015 – Web-Based Test Case Management with TFS" ^[23]
Thank you very much.
Pat MSFT (talk) 18:43, 14 March 2016 (UTC)[reply]

You need to put the above on the Article's Talk Page, not your talk page. I've deactiveted the template. Ronhjones ^(Talk) 19:49, 15 April 2016 (UTC)[reply]

References

Removal of Link and Reference #23

The reference / link #23 is a link to "qTest Reviews | G2 Crowd". G2 Crowd. Retrieved 2016-08-10. If you visit this link, only the first reviews are visible unless you 'sign in' (join). Only the highest ratings are visible - you can't see what the 'problems' are unless you accept the TOS for G2, which is trying to sell the product. This sets up an conflict of interest (only showing the best). Suggest that the link be removed. 50.206.61.160 (talk) 23:50, 8 November 2016 (UTC)[reply]

That wasn't the case for me. https://www.g2crowd.com/products/qtest/reviews loads fine and I could navigate to four pages deep. I just dismissed the spammy sign-up dialog. Walter Görlitz (talk) 00:31, 9 November 2016 (UTC)[reply]

Rechecked with IE, FF and Chrome. All three re-display the same first page and user cannot get past it. (Would add-block work?)50.206.61.160 (talk) 19:28, 11 November 2016 (UTC)[reply]

Not sure. I'm not running one and I see four pages of reviews. Not sure what's blocking you. Walter Görlitz (talk) 21:38, 11 November 2016 (UTC)[reply]

Historical Evolution of Test Management Tools

Hello, fellow editors,

I am proposing an addition to this article to introduce the historical evolution of the Test Management Tools.

Conflict of Interest Disclosure: Please note that I work for TestQuality.com, which offers a test management tool, that has been developed by BitModern, Inc. I am making this disclosure in accordance with Wikipedia's Conflict of Interest guidelines, and I will not be making any direct edits to the article. My intention is solely to contribute encyclopedic content that improves the article. You can find more details on my user page: [User:Joses3es]. Rationale for Addition:

Historical Development:

Incorporate information on the evolution of test management tools. This narrative can trace their origins from early, rudimentary bug-tracking systems that relied on manual processes and spreadsheets, to the emergence of more sophisticated, integrated platforms.

Proposed Content

I suggest adding a new section, perhaps titled "Historical Evolution of Test Management Tools" or "Test Management History", which could include this paragraph with historic Test Management milestones.

Here's a draft of the content I propose:

The evolution of test management tools began in the late 20th century with rudimentary bug-tracking systems that largely relied on manual processes and spreadsheets. This early phase transitioned into more integrated platforms as software became more complex and development teams expanded. Notable advancements included Mercury Interactive's Test Director, which later evolved into HP Quality Center and Application Lifecycle Management (ALM), and IBM Rational Quality Manager. ^[1] This shift was significantly influenced by the widespread adoption of Agile and DevOps methodologies, which emphasized continuous testing, automation, and enhanced collaboration throughout the software development lifecycle.^[2]

Sources:

1. Test Management Tools: Past, Present, and Future - Calleo Software, accessed May 27, 2025, https://www.calleosoftware.co.uk/software-testing-insights/test-management-tools-past-present-and-future/

2.- The Evolution of Test Management: Tools & Techniques | 42 Interactive, accessed May 27, 2025, https://www.42interactive.com/blog/the-evolution-of-test-management-tools-techniques

^ 1
^ 2

I welcome any feedback, suggestions, or discussions from other editors regarding this proposed addition. Please let me know if this content aligns with the article's scope and Wikipedia's guidelines.

Thank you for your time and consideration.

Jose F. Amoros [User:Joses3es] Jose F. Amoros (talk) 14:31, 6 June 2025 (UTC)[reply]

Please have a look at WP:RS. We shouldn't be using marketing materials like vendor blog posts as sources. MrOllie (talk) 14:44, 6 June 2025 (UTC)[reply]

[1] ttps://en.wikipedia.org/wiki/Microsoft_Visual_Studio#Visual_Studio_Test_Professional

[2] ttps://en.wikipedia.org/wiki/Team_Foundation_Server

[3] ttps://en.wikipedia.org/wiki/Microsoft_Visual_Studio#Team_Services

[4] ttps://en.wikipedia.org/wiki/Exploratory_testing

[5] ttps://en.wikipedia.org/wiki/Test_management

[6] ttps://en.wikipedia.org/wiki/Test_plan

[7] ttps://en.wikipedia.org/wiki/Test_case

[8] ttps://en.wikipedia.org/wiki/Manual_testing

[9] ttps://en.wikipedia.org/wiki/Test_automation

[10] ttps://en.wikipedia.org/wiki/Continuous_integration

[11] ttps://en.wikipedia.org/wiki/Continuous_delivery

[12] ttps://en.wikipedia.org/wiki/Visual_Studio_Lab_Management

[13] ttp://www.edsquared.com/2012/03/28/Difference+Between+Microsoft+Test+Manager+And+Visual+Studio+Test+Professional.aspx

[14] ttps://en.wikipedia.org/wiki/Team_Foundation_Server

[15] ttps://en.wikipedia.org/wiki/Test_case

[16] ttps://en.wikipedia.org/wiki/Test_management

[17] ttps://en.wikipedia.org/wiki/Manual_testing

[18] ttps://en.wikipedia.org/wiki/Test_automation

[19] ttps://en.wikipedia.org/wiki/Continuous_integration

[20] ttps://en.wikipedia.org/wiki/Continuous_delivery

[21] ttps://en.wikipedia.org/wiki/Microsoft_Visual_Studio#Team_Services

[22] ttps://en.wikipedia.org/wiki/Load_testing

[23] ttps://msdn.microsoft.com/magazine/dn890369.aspx

[24] 1

[25] 2

[1]

[2]

[3]

[4]

[5]

[6]

[7]

[8]

[9]

[10]

[11]

[12]

[13]

[14]

[15]

[16]

[17]

[18]

[19]

[20]

[21]

[22]

[23]

[1]

[2]