Weitere Kapitel dieses Buchs durch Wischen aufrufen
As a consultant, most customers that call me to help them start working with test automation start with the questions: “Which tools are there?” and “which tools should I use”? If you’re in that situation yourself, then you’re probably asking this question too. The short answer to the first question is that there are a bazillion tools out there for test automation. Oh, and there’s Selenium, too, of course, so there are bazillion and one. And the short answer to the second question is the classical consultant’s answer: “It depends.”
Bitte loggen Sie sich ein, um Zugang zu diesem Inhalt zu erhalten
Sie möchten Zugang zu diesem Inhalt erhalten? Dann informieren Sie sich jetzt über unsere Produkte:
See the description of “sociable” tests at https://martinfowler.com/bliki/UnitTest.html . Other relevant references: https://martinfowler.com/articles/is-tdd-dead/ and http://www.se-radio.net/2010/09/episode-167-the-history-of-junit-and-the-future-of-testing-with-kent-beck/ (around minutes 22–26).
IDE is an acronym for Integrated Development Environment. These are applications that allow developers to write, edit, compile, and debug their code; and carry many other actions that are related to the development of the code.
Some languages are compiled into byte-code that is run by a dedicated runtime engine. The Java Virtual Machine (JVM) and .Net Common Langauge Runtime (CLR) are the most known ones. Libraries that are compiled for these engines can be consumed by applications that are written in any language that can also be compiled for the same engine. So, for example, the WebDriver library for Java can be consumed by tests written in Scala and Groovy, and the C# (.Net) binding can be consumed by tests written in VB.Net and F#.
- People and Tools
- Chapter 3
Neuer Inhalt/© ITandMEDIA