Talk:Google Test

Computing: Software / Free and open-source software

	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 articles
???	This article has not yet received a rating on the project's importance scale.
	This article is supported by WikiProject Software.
	This article is supported by Free and open-source software (assessed as Low-importance).

This page is badly written and sounds more like an advertisement for Google than anything else. It doesn't read like a page about Google Test. - Anon

Also, in the process of praising Google's almighty testing power, some paragraph are downright wrong: "Instead of categorizations like unit, functional or integration test they have only three categories: small, medium, and large scale tests" The next paragraphs describe the small, medium, and large tests, and how they actually are unit, fonctionnal and acceptance tests. Saucistophe (talk) 09:36, 6 August 2015 (UTC)[reply]

SET vs Software Engineer vs. Developer

What is the difference between these three? This page makes no sense.

Google Test vs. Tests at Google

The main problem of this page is that the two above topics are mixed up. Google Test is a (great) testing framework for C/C++. Google has additionally published a (non-related) book "How Google tests Software", and the definitions of Small, Medium, and Large Tests are from that book. They are not wrong in the sense that Google indeed (according to the book) decided to stop all discussions about whether a test e.g. is still an integration or already an acceptance test, and gave themselves clear technical benchmarks for these three classes of tests; in fact, they also have Gigantic Tests. 5.146.66.242 (talk) 21:09, 4 May 2017 (UTC)[reply]

Fixture Tests

I am taking the liberty of deleting this section without replacement. Fixtures are a standard feature of modern test frameworks, so it is not absolutely necessary for an article on Google Test to even mention it. The information that *was* in the section, however, was complete and utter nonsense and is worse than not mentioning it at all. Fixtures are not "crucial in computer code because it allows the testing of time and memory management", and the source (IBM's "A quick introduction to the Google C++ Testing Framework") does not state so. Instead, it names setting up "time and memory management" as an example of "custom initialization work before executing a unit test", for which test fixtures are a useful feature. The section then goes on to quote a bullet-point list from the source, completely out of context, calling it "details relevant to understanding how fixtures work", when in fact, they are "details that you should be aware of when doing the more important things mentioned in IBM's article, which are not reproduced here on Wikipedia"). 178.113.203.222 (talk) 11:05, 23 June 2018 (UTC)[reply]

Marko Mrkaja

5.10.1985 Visoko,bivši je fudbaler.Igrao na poziciji Golman. Igrao za FK Radnik Hadzici i Fk Romanija pale Mrki 85 (talk) 22:46, 7 November 2023 (UTC)[reply]

Terminology

Did the original author of that framework really thought a "Case" was were you grouped your tests together, like a "Suite Case" or something ? I was shocked when I saw that and this raises question about the quality of the work done by that company. — Preceding unsigned comment added by 2A01:E0A:909:95B0:79DD:7CF1:B256:D707 (talk) 20:03, 18 November 2024 (UTC)[reply]