Most developers seem to agree that testing is good, but developers frequently disagree about how to test. In this article, I’ll break down some common misconceptions and hopefully teach you a few…
ClassMock is a framework that helps the creation of unit tests for components that use reflection or annotations. In this kind of classes, the behavior is dependent of the class structure. This way, each test case usually works with a different class created specifically for the test. With ClassMock is possible to define and generate classes in runtime, allowing a better test readability and logic sharing between tests.
For those of you who've got into it you'll know that test driven development is great. It gives you the confidence to change code safe in the knowledge that if something breaks you'll know about it. Except for those bits you don't know how to test. Until now XML has been one of them. Oh sure you can use "<stuff></stuff>".equals("<stuff></stuff>"); but is that really gonna work when some joker decides to output a <stuff/>? -- damned right it's not ;-)
I googled test patterns in Go, then I invoked the Spirits of the Core Library. As soon as I realised where to look at, I finally saw a sign. It was Brad Fitzpatrick.
I did a talk at TestBash Germany last week that sparked lots of positive response, but also some critique. Critique is fair: It was a 30 minute inspirational talk in which I wanted to explain why Immanuel Kant’s work “Critique of Pure Reason” matters to testers. Quite a few people found me afterwards, asked me…
Abbot helps you test your Java UI. It comprises Abbot, which lets you programmatically drive UI components, and Costello (built on Abbot) which allows you to easily launch, explore and control an application. The framework may be used with both scripts and compiled code.
AceUnit (Advanced C and Embedded Unit) ist ein komfortables Framework für Unit-Tests von C-Code. AceUnit orientiert sich am Stil von JUnit 4.x und ist einfach, modular und flexibel. AceUnit kann in Umgebungen mit geringen Ressourcen verwendet werden, beispielsweise in der Entwicklung eingebetteter Systeme.
S. Tan, D. Marinov, L. Tan, and G. Leavens. Software Testing, Verification and Validation (ICST), 2012 IEEE Fifth International Conference on, page 260-269. (April 2012)
S. Vegas, and V. Basili. Empirical Software Engineering, 10 (4):
437-466(2005)MR: Versucht die Antwort auf die Frage zu erleichtern: Wie soll indentifiziert werden, welches Testkriteria passen am besten zu meinem Testselektionsproblem?
Bei IST-SPL könnte es zur Begründung des eingesetzten Überdeckungskriteriums herangezogen werden..
M. Smucker, J. Allan, and B. Carterette. CIKM '07: Proceedings of the sixteenth ACM conference on Conference on information and knowledge management, page 623--632. New York, NY, USA, ACM, (2007)