Wiki Sayfaları
Abstract Class Array Class Compositions and Associations(Siniflarin Olusumu ve Birlikteliyi) Compiling and Interpreting Java Code(Java Kodunu Derleme) Degiskenler(Variables) ECLIPSE & JIRA & MYLYN Üçlüsü Enum Extends Olunan Class’larda Constructor iliskisi Final HIBERNATE : Repeated column in mapping for entity: ... (should be mapped with insert=false update= Hibernate ile @Any kullanımı Initialization Blocks(Class’ta Bloglarin Calisma Prensibi ) instanceof keyword Interface Class JAVA PACKAGE java.io.Serializable java.util.regex.Matcher and java.util.regex.Pattern java.util.Scanner and java.util.Formatter Jsf 2.0 ile Custom Component OlustrumaJsf 2.0 ile Custom Component Olustruma Labeled Statements Object Passing Variables into Methods Primitive type(Ilkel veri tipleri) Programming with Java Operators and Strings(Java Operatorleri ve String mothodlari) Programming with Java Statements(Java Programlama Ifadeleri) Raporu Ziplenmesi ve Zipten Cikarilmasi String , StringBuffer , StringBuilder System.out.printf
TDD ile Uygulama Geliştirme Tomcatde JSESSIONID Yönetimi TreeSet Uygulamasi Varargs Wicket EKÜ (Eller Klavye Üzerinde) çalışma sorularıReklamlar
TDD ile Uygulama Geliştirme
Etiketler:
TDD Derlemeleri
A Set of Unit Testing Rules by Michael Feathers [http://www.artima.com/weblogs/viewpost.jsp?thread=126923]
In Extreme Programming, the typical way of handling it is to periodically go back and optimize your tests as they get too slow. In many cases this works well, but the amount of optimization that you have to do can be rather large if you haven’t been conscious of how long your tests run during development.The tests hit a server and went through session beans, entity beans, down to the bowels of the database and then up again. Their refrain? “We don’t like writing unit tests any more; they take too long to run.
When you pull the database, sockets, or file system access into your unit tests, they aren’t really about those methods any more; they are about the integration of your code with that other software.
TDD Videoları
A Set of Unit Testing Rules by Michael Feathers [http://www.artima.com/weblogs/viewpost.jsp?thread=126923]
In Extreme Programming, the typical way of handling it is to periodically go back and optimize your tests as they get too slow. In many cases this works well, but the amount of optimization that you have to do can be rather large if you haven’t been conscious of how long your tests run during development.The tests hit a server and went through session beans, entity beans, down to the bowels of the database and then up again. Their refrain? “We don’t like writing unit tests any more; they take too long to run.
A test is not a unit test if:
- It talks to the database
- It communicates across the network
- It touches the file system
- It can't run at the same time as any of your other unit tests
- You have to do special things to your environment (such as editing config files) to run it.
When you pull the database, sockets, or file system access into your unit tests, they aren’t really about those methods any more; they are about the integration of your code with that other software.
TDD Videoları
Getting Started with Tdd in Java using Eclipse from Brett L. Schuchert on Vimeo.
Tartışma
ya da