Expertiza_Wiki - User contributions [en]

CSC/ECE 517 Fall 2009/wiki2 13 StaticDynamic

2009-10-09T02:41:02Z

Los Bravo: /* Example */

'''Design Patterns from a Static/Dynamic Point of View'''

Clearly, Ruby offers more concise realizations of certain design patterns than Java does. Is this typical of dynamic o-o languages? Are there design patterns that any dynamically typed language can realize better than a statically typed language? Are there instances when a different pattern should be used in a dynamic language than a static language?

== Introduction ==
=== Design Pattern ===
A design pattern is a general reusable solution to a commonly occurring problem in software design. A design pattern is not a finished design that can be transformed directly into code. It is a description or template for how to solve a problem that can be used in many different situations. Object-oriented design patterns typically show relationships and interactions between classes or objects, without specifying the final application classes or objects that are involved.

[http://www.dofactory.com/Patterns/Patterns.aspx [1]]
{| border="1"
|-
!Name !! Description
|-
| Creational Patterns
|-
| Abstract Factory || Creates an instance of several families of classes
|-
| Builder || Separates object construction from its representation
|-
| Factory Method || Creates an instance of several derived classes
|-
| Prototype || A fully initialized instance to be copied or cloned
|-
| Singleton || A class of which only a single instance can exist
|-
| Structural Patterns
|-
| Adapter || Match interfaces of different classes
|-
| Bridge || Separates an object’s interface from its implementation
|-
| Composite || A tree structure of simple and composite objects
|-
| Decorator || Add responsibilities to objects dynamically
|-
| Facade || A single class that represents an entire subsystem
|-
| Flyweight || A fine-grained instance used for efficient sharing
|-
| Proxy || An object representing another object
|-
| Behavioral Patterns
|-
| Chain of Resp. || A way of passing a request between a chain of objects
|-
| Command || Encapsulate a command request as an object
|-
| Interpreter || A way to include language elements in a program
|-
| Iterator || Sequentially access the elements of a collection
|-
| Mediator || Defines simplified communication between classes
|-
| Memento || Capture and restore an object's internal state
|-
| Observer || A way of notifying change to a number of classes
|-
| State || Alter an object's behavior when its state changes
|-
| Strategy || Encapsulates an algorithm inside a class
|-
| Template Method || Defer the exact steps of an algorithm to a subclass
|-
| Visitor || Defines a new operation to a class without change
|}

=== Static/Dynamic Type Languages ===
Types usually have associations either with values in memory or with objects such as variables. Because any value simply consists of a sequence of bits in a computer, hardware makes no distinction even between memory addresses, instruction code, characters, integers and floating-point numbers. Assignment to a type informs programs and programmers how those bit collections should be treated.

Major functions provided by type systems include:

* Safety - Use of types may allow a compiler to detect meaningless or probably invalid code. For example, we can identify an expression "Hello, World" as invalid because the rules of arithmetic do not specify how to divide an integer by a string. As discussed below, strong typing offers more safety, but generally does not guarantee complete safety (see type-safety for more information).
* Optimization - Static type-checking may provide useful compile-time information. For example, if a type requires that a value must align in memory at a multiple of 4 bytes, the compiler may be able to use more efficient machine instructions.
* Documentation - In more expressive type systems, types can serve as a form of documentation, since they can illustrate the intent of the programmer. For instance, timestamps may be represented as integers—but if a programmer declares a function as returning a timestamp type rather than merely an integer type, this documents part of the meaning of the function.
* Abstraction (or modularity) - Types allow programmers to think about programs at a higher level than the bit or byte, not bothering with low-level implementation. For example, programmers can think of a string as a collection of character values instead of as a mere array of bytes. Or, types can allow programmers to express the interface between two subsystems. This helps localize the definitions required for interoperability of the subsystems and prevents inconsistencies when those subsystems communicate.

==== Static Type Languages ====
A programming language is said to use static typing when type checking is performed during compile-time as opposed to run-time.

C++, C#, Java

==== Dynamic Type Languages ====
A programming language is said to be dynamically typed, or just 'dynamic', when the majority of its type checking is performed at run-time as opposed to at compile-time.

Ruby, Python

== Example ==

[http://i.cmpnet.com/ddj/ddj/images/ddj9708d/9708df6.gif [2]]
Many software designers view patterns as a form of language-independent design. Pattern-Oriented Software Architectures: A System of Patterns, edited by Frank Buschmann (John Wiley & Sons, 1996), for instance, divides patterns into three main groups -- architectural patterns, design patterns, and idioms. Only the idioms (defined as "low-level patterns specific to a program language") are language dependent -- the other patterns (and the implicit pattern language) rise above the level of programming language, much as the unified modeling language (UML) provides a common way to express designs.

This idea of language independence is seductive. It is also misleading. While patterns are language independent, language choice limits the patterns that are possible, easily supported, and useful. Language also affects how applications are structured.

To illustrate, we'll examine a pattern often used with Objective-C, but not usually used (or used differently) with C++. Both languages are object-oriented extensions of C. The main difference between them is that C++ has compile-time binding and fairly strong typing while Objective-C uses the Smalltalk object model of dynamic binding and weak typing. We'll be examining facade, commonly found in Objective-C programming. While simple, facade illustrates some of the key Objective-C programming techniques

====The Facade Pattern====

Lets examine a commonly used architectural pattern that describes a way to structure applications to take advantage of this flexibility.

Previously with structured programming, saving an application's state was simple. Programs were divided into data and functions, and saving consisted of calling the function that wrote the data to some storage area. In object-oriented applications, things become a little more difficult. To the extent that you practice information hiding, object serialization is the natural approach to take.

Unfortunately, if m is the number of object references and n is the number of objects, serialization is O(mlog(n)). This is far too slow for serialization to be the saving mechanism in many applications.

But an Objective-C program that uses the four previous patterns will almost certainly use lots of facades as well. Notice here[http://i.cmpnet.com/ddj/ddj/images/ddj9708d/9708df6.gif [3]]that Facades look a lot like cut points in the object graph. This leads to the natural Objective-C solution to the speed problem for object serialization: Serialize each facade to a separate Serializer (make each facade responsible for serializing the subsystem it abstracts).

This can get complicated. If an object outside a subsystem bypasses a facade (and messages an object in a subsystem directly), then extra care must be taken during serialization (to avoid serializing objects to more than one location). And, deserializing (opening) becomes trickier as well -- objects that bypass a facade will need to find objects within the subsystem. In practice, this comes down to making the facades used in serialization Singletons and making certain that all connections to objects in the subsystem are mediated by the facade (so that, during deserialization, the connection can be restored).

== Conclusion ==

There are various levels of design recognition for generating repeatable solutions to commonly occurring programming problems in software design. Design patterns in this case have been met with criticism in whether it negates the agile product development process. From our example above we have shown that when implementing patterns across various languages of varying type systems a design pattern may not always resolve common problems efficiently. Thus, the idea of a language independent pattern recognition solution must be evaluated thoroughly when in considering from a static and dynamic point of view.

== References ==

All sources used to create this wiki are linked in the above text.

CSC/ECE 517 Fall 2009/wiki2 13 StaticDynamic

2009-10-09T02:26:55Z

Los Bravo: /* Example */

'''Design Patterns from a Static/Dynamic Point of View'''

Clearly, Ruby offers more concise realizations of certain design patterns than Java does. Is this typical of dynamic o-o languages? Are there design patterns that any dynamically typed language can realize better than a statically typed language? Are there instances when a different pattern should be used in a dynamic language than a static language?

== Introduction ==
=== Design Pattern ===
A design pattern is a general reusable solution to a commonly occurring problem in software design. A design pattern is not a finished design that can be transformed directly into code. It is a description or template for how to solve a problem that can be used in many different situations. Object-oriented design patterns typically show relationships and interactions between classes or objects, without specifying the final application classes or objects that are involved.

[http://www.dofactory.com/Patterns/Patterns.aspx [1]]
{| border="1"
|-
!Name !! Description
|-
| Creational Patterns
|-
| Abstract Factory || Creates an instance of several families of classes
|-
| Builder || Separates object construction from its representation
|-
| Factory Method || Creates an instance of several derived classes
|-
| Prototype || A fully initialized instance to be copied or cloned
|-
| Singleton || A class of which only a single instance can exist
|-
| Structural Patterns
|-
| Adapter || Match interfaces of different classes
|-
| Bridge || Separates an object’s interface from its implementation
|-
| Composite || A tree structure of simple and composite objects
|-
| Decorator || Add responsibilities to objects dynamically
|-
| Facade || A single class that represents an entire subsystem
|-
| Flyweight || A fine-grained instance used for efficient sharing
|-
| Proxy || An object representing another object
|-
| Behavioral Patterns
|-
| Chain of Resp. || A way of passing a request between a chain of objects
|-
| Command || Encapsulate a command request as an object
|-
| Interpreter || A way to include language elements in a program
|-
| Iterator || Sequentially access the elements of a collection
|-
| Mediator || Defines simplified communication between classes
|-
| Memento || Capture and restore an object's internal state
|-
| Observer || A way of notifying change to a number of classes
|-
| State || Alter an object's behavior when its state changes
|-
| Strategy || Encapsulates an algorithm inside a class
|-
| Template Method || Defer the exact steps of an algorithm to a subclass
|-
| Visitor || Defines a new operation to a class without change
|}

=== Static/Dynamic Type Languages ===
Types usually have associations either with values in memory or with objects such as variables. Because any value simply consists of a sequence of bits in a computer, hardware makes no distinction even between memory addresses, instruction code, characters, integers and floating-point numbers. Assignment to a type informs programs and programmers how those bit collections should be treated.

Major functions provided by type systems include:

* Safety - Use of types may allow a compiler to detect meaningless or probably invalid code. For example, we can identify an expression "Hello, World" as invalid because the rules of arithmetic do not specify how to divide an integer by a string. As discussed below, strong typing offers more safety, but generally does not guarantee complete safety (see type-safety for more information).
* Optimization - Static type-checking may provide useful compile-time information. For example, if a type requires that a value must align in memory at a multiple of 4 bytes, the compiler may be able to use more efficient machine instructions.
* Documentation - In more expressive type systems, types can serve as a form of documentation, since they can illustrate the intent of the programmer. For instance, timestamps may be represented as integers—but if a programmer declares a function as returning a timestamp type rather than merely an integer type, this documents part of the meaning of the function.
* Abstraction (or modularity) - Types allow programmers to think about programs at a higher level than the bit or byte, not bothering with low-level implementation. For example, programmers can think of a string as a collection of character values instead of as a mere array of bytes. Or, types can allow programmers to express the interface between two subsystems. This helps localize the definitions required for interoperability of the subsystems and prevents inconsistencies when those subsystems communicate.

==== Static Type Languages ====
A programming language is said to use static typing when type checking is performed during compile-time as opposed to run-time.

C++, C#, Java

==== Dynamic Type Languages ====
A programming language is said to be dynamically typed, or just 'dynamic', when the majority of its type checking is performed at run-time as opposed to at compile-time.

Ruby, Python

== Example ==

[http://i.cmpnet.com/ddj/ddj/images/ddj9708d/9708df6.gif [2]]
Many software designers view patterns as a form of language-independent design. Pattern-Oriented Software Architectures: A System of Patterns, edited by Frank Buschmann (John Wiley & Sons, 1996), for instance, divides patterns into three main groups -- architectural patterns, design patterns, and idioms. Only the idioms (defined as "low-level patterns specific to a program language") are language dependent -- the other patterns (and the implicit pattern language) rise above the level of programming language, much as the unified modeling language (UML) provides a common way to express designs.

This idea of language independence is seductive. It is also misleading. While patterns are language independent, language choice limits the patterns that are possible, easily supported, and useful. Language also affects how applications are structured.

To illustrate, we'll examine a pattern often used with Objective-C, but not usually used (or used differently) with C++. Both languages are object-oriented extensions of C. The main difference between them is that C++ has compile-time binding and fairly strong typing while Objective-C uses the Smalltalk object model of dynamic binding and weak typing. We'll examining facade, commonly found in Objective-C programming. While simple, facade illustrates some of the key Objective-C programming techniques (although I use NextStep classes and frameworks to illustrate points, what I say also holds true for more generic Objective-C environments).

====The Facade Pattern====

Lets examine a commonly used architectural pattern that describes a way to structure applications to take advantage of this flexibility.

Previously with structured programming, saving an application's state was simple. Programs were divided into data and functions, and saving consisted of calling the function that wrote the data to some storage area. In object-oriented applications, things become a little more difficult. To the extent that you practice information hiding, object serialization is the natural approach to take.

Unfortunately, if m is the number of object references and n is the number of objects, serialization is O(mlog(n)). This is far too slow for serialization to be the saving mechanism in many applications.

But an Objective-C program that uses the four previous patterns will almost certainly use lots of facades as well. Notice here[http://i.cmpnet.com/ddj/ddj/images/ddj9708d/9708df6.gif [3]]that Facades look a lot like cut points in the object graph. This leads to the natural Objective-C solution to the speed problem for object serialization: Serialize each facade to a separate Serializer (make each facade responsible for serializing the subsystem it abstracts).

This can get complicated. If an object outside a subsystem bypasses a facade (and messages an object in a subsystem directly), then extra care must be taken during serialization (to avoid serializing objects to more than one location). And, deserializing (opening) becomes trickier as well -- objects that bypass a facade will need to find objects within the subsystem. In practice, this comes down to making the facades used in serialization Singletons and making certain that all connections to objects in the subsystem are mediated by the facade (so that, during deserialization, the connection can be restored).

== Conclusion ==

There are various levels of design recognition for generating repeatable solutions to commonly occurring programming problems in software design. Design patterns in this case have been met with criticism in whether it negates the agile product development process. From our example above we have shown that when implementing patterns across various languages of varying type systems a design pattern may not always resolve common problems efficiently. Thus, the idea of a language independent pattern recognition solution must be evaluated thoroughly when in considering from a static and dynamic point of view.

== References ==

All sources used to create this wiki are linked in the above text.

CSC/ECE 517 Fall 2009/wiki2 13 StaticDynamic

2009-10-09T02:10:15Z

Los Bravo: /* The Facade Pattern */

'''Design Patterns from a Static/Dynamic Point of View'''

Clearly, Ruby offers more concise realizations of certain design patterns than Java does. Is this typical of dynamic o-o languages? Are there design patterns that any dynamically typed language can realize better than a statically typed language? Are there instances when a different pattern should be used in a dynamic language than a static language?

== Introduction ==
=== Design Pattern ===
A design pattern is a general reusable solution to a commonly occurring problem in software design. A design pattern is not a finished design that can be transformed directly into code. It is a description or template for how to solve a problem that can be used in many different situations. Object-oriented design patterns typically show relationships and interactions between classes or objects, without specifying the final application classes or objects that are involved.

[http://www.dofactory.com/Patterns/Patterns.aspx [1]]
{| border="1"
|-
!Name !! Description
|-
| Creational Patterns
|-
| Abstract Factory || Creates an instance of several families of classes
|-
| Builder || Separates object construction from its representation
|-
| Factory Method || Creates an instance of several derived classes
|-
| Prototype || A fully initialized instance to be copied or cloned
|-
| Singleton || A class of which only a single instance can exist
|-
| Structural Patterns
|-
| Adapter || Match interfaces of different classes
|-
| Bridge || Separates an object’s interface from its implementation
|-
| Composite || A tree structure of simple and composite objects
|-
| Decorator || Add responsibilities to objects dynamically
|-
| Facade || A single class that represents an entire subsystem
|-
| Flyweight || A fine-grained instance used for efficient sharing
|-
| Proxy || An object representing another object
|-
| Behavioral Patterns
|-
| Chain of Resp. || A way of passing a request between a chain of objects
|-
| Command || Encapsulate a command request as an object
|-
| Interpreter || A way to include language elements in a program
|-
| Iterator || Sequentially access the elements of a collection
|-
| Mediator || Defines simplified communication between classes
|-
| Memento || Capture and restore an object's internal state
|-
| Observer || A way of notifying change to a number of classes
|-
| State || Alter an object's behavior when its state changes
|-
| Strategy || Encapsulates an algorithm inside a class
|-
| Template Method || Defer the exact steps of an algorithm to a subclass
|-
| Visitor || Defines a new operation to a class without change
|}

=== Static/Dynamic Type Languages ===
Types usually have associations either with values in memory or with objects such as variables. Because any value simply consists of a sequence of bits in a computer, hardware makes no distinction even between memory addresses, instruction code, characters, integers and floating-point numbers. Assignment to a type informs programs and programmers how those bit collections should be treated.

Major functions provided by type systems include:

* Safety - Use of types may allow a compiler to detect meaningless or probably invalid code. For example, we can identify an expression "Hello, World" as invalid because the rules of arithmetic do not specify how to divide an integer by a string. As discussed below, strong typing offers more safety, but generally does not guarantee complete safety (see type-safety for more information).
* Optimization - Static type-checking may provide useful compile-time information. For example, if a type requires that a value must align in memory at a multiple of 4 bytes, the compiler may be able to use more efficient machine instructions.
* Documentation - In more expressive type systems, types can serve as a form of documentation, since they can illustrate the intent of the programmer. For instance, timestamps may be represented as integers—but if a programmer declares a function as returning a timestamp type rather than merely an integer type, this documents part of the meaning of the function.
* Abstraction (or modularity) - Types allow programmers to think about programs at a higher level than the bit or byte, not bothering with low-level implementation. For example, programmers can think of a string as a collection of character values instead of as a mere array of bytes. Or, types can allow programmers to express the interface between two subsystems. This helps localize the definitions required for interoperability of the subsystems and prevents inconsistencies when those subsystems communicate.

==== Static Type Languages ====
A programming language is said to use static typing when type checking is performed during compile-time as opposed to run-time.

C++, C#, Java

==== Dynamic Type Languages ====
A programming language is said to be dynamically typed, or just 'dynamic', when the majority of its type checking is performed at run-time as opposed to at compile-time.

Ruby, Python

== Example ==

[http://i.cmpnet.com/ddj/ddj/images/ddj9708d/9708df6.gif [2]]
Many software designers view patterns as a form of language-independent design. Pattern-Oriented Software Architectures: A System of Patterns, edited by Frank Buschmann (John Wiley & Sons, 1996), for instance, divides patterns into three main groups -- architectural patterns, design patterns, and idioms. Only the idioms (defined as "low-level patterns specific to a program language") are language dependent -- the other patterns (and the implicit pattern language) rise above the level of programming language, much as the unified modeling language (UML) provides a common way to express designs.

This idea of language independence is seductive. It is also misleading. While patterns are language independent, language choice limits the patterns that are possible, easily supported, and useful. Language also affects how applications are structured.

To illustrate, I'll examine some patterns often used with Objective-C, but not usually used (or used differently) with C++. Both languages are object-oriented extensions of C. The main difference between them is that C++ has compile-time binding and fairly strong typing while Objective-C uses the Smalltalk object model of dynamic binding and weak typing. I'll start by examining two idioms commonly found in Objective-C programming. While simple, these idioms illustrate some of the key Objective-C programming techniques (although I use NextStep classes and frameworks to illustrate points, what I say also holds true for more generic Objective-C environments). I'll also examine how three standard design patterns -- Visitor, Command, and Facade -- are implemented in Objective-C.

====The Facade Pattern====

Lets examine a commonly used architectural pattern that describes a way to structure applications to take advantage of this flexibility.

Previously with structured programming, saving an application's state was simple. Programs were divided into data and functions, and saving consisted of calling the function that wrote the data to some storage area. In object-oriented applications, things become a little more difficult. To the extent that you practice information hiding, object serialization is the natural approach to take.

Unfortunately, if m is the number of object references and n is the number of objects, serialization is O(mlog(n)). This is far too slow for serialization to be the saving mechanism in many applications.

But an Objective-C program that uses the four previous patterns will almost certainly use lots of facades as well. Notice here[http://i.cmpnet.com/ddj/ddj/images/ddj9708d/9708df6.gif [3]]that Facades look a lot like cut points in the object graph. This leads to the natural Objective-C solution to the speed problem for object serialization: Serialize each facade to a separate Serializer (make each facade responsible for serializing the subsystem it abstracts).

This can get complicated. If an object outside a subsystem bypasses a facade (and messages an object in a subsystem directly), then extra care must be taken during serialization (to avoid serializing objects to more than one location). And, deserializing (opening) becomes trickier as well -- objects that bypass a facade will need to find objects within the subsystem. In practice, this comes down to making the facades used in serialization Singletons and making certain that all connections to objects in the subsystem are mediated by the facade (so that, during deserialization, the connection can be restored).

== Conclusion ==

There are various levels of design recognition for generating repeatable solutions to commonly occurring programming problems in software design. Design patterns in this case have been met with criticism in whether it negates the agile product development process. From our example above we have shown that when implementing patterns across various languages of varying type systems a design pattern may not always resolve common problems efficiently. Thus, the idea of a language independent pattern recognition solution must be evaluated thoroughly when in considering from a static and dynamic point of view.

== References ==

All sources used to create this wiki are linked in the above text.

CSC/ECE 517 Fall 2009/wiki2 13 StaticDynamic

2009-10-09T02:08:14Z

Los Bravo: /* Objective- C Idiom 1 */

'''Design Patterns from a Static/Dynamic Point of View'''

Clearly, Ruby offers more concise realizations of certain design patterns than Java does. Is this typical of dynamic o-o languages? Are there design patterns that any dynamically typed language can realize better than a statically typed language? Are there instances when a different pattern should be used in a dynamic language than a static language?

== Introduction ==
=== Design Pattern ===
A design pattern is a general reusable solution to a commonly occurring problem in software design. A design pattern is not a finished design that can be transformed directly into code. It is a description or template for how to solve a problem that can be used in many different situations. Object-oriented design patterns typically show relationships and interactions between classes or objects, without specifying the final application classes or objects that are involved.

[http://www.dofactory.com/Patterns/Patterns.aspx [1]]
{| border="1"
|-
!Name !! Description
|-
| Creational Patterns
|-
| Abstract Factory || Creates an instance of several families of classes
|-
| Builder || Separates object construction from its representation
|-
| Factory Method || Creates an instance of several derived classes
|-
| Prototype || A fully initialized instance to be copied or cloned
|-
| Singleton || A class of which only a single instance can exist
|-
| Structural Patterns
|-
| Adapter || Match interfaces of different classes
|-
| Bridge || Separates an object’s interface from its implementation
|-
| Composite || A tree structure of simple and composite objects
|-
| Decorator || Add responsibilities to objects dynamically
|-
| Facade || A single class that represents an entire subsystem
|-
| Flyweight || A fine-grained instance used for efficient sharing
|-
| Proxy || An object representing another object
|-
| Behavioral Patterns
|-
| Chain of Resp. || A way of passing a request between a chain of objects
|-
| Command || Encapsulate a command request as an object
|-
| Interpreter || A way to include language elements in a program
|-
| Iterator || Sequentially access the elements of a collection
|-
| Mediator || Defines simplified communication between classes
|-
| Memento || Capture and restore an object's internal state
|-
| Observer || A way of notifying change to a number of classes
|-
| State || Alter an object's behavior when its state changes
|-
| Strategy || Encapsulates an algorithm inside a class
|-
| Template Method || Defer the exact steps of an algorithm to a subclass
|-
| Visitor || Defines a new operation to a class without change
|}

=== Static/Dynamic Type Languages ===
Types usually have associations either with values in memory or with objects such as variables. Because any value simply consists of a sequence of bits in a computer, hardware makes no distinction even between memory addresses, instruction code, characters, integers and floating-point numbers. Assignment to a type informs programs and programmers how those bit collections should be treated.

Major functions provided by type systems include:

* Safety - Use of types may allow a compiler to detect meaningless or probably invalid code. For example, we can identify an expression "Hello, World" as invalid because the rules of arithmetic do not specify how to divide an integer by a string. As discussed below, strong typing offers more safety, but generally does not guarantee complete safety (see type-safety for more information).
* Optimization - Static type-checking may provide useful compile-time information. For example, if a type requires that a value must align in memory at a multiple of 4 bytes, the compiler may be able to use more efficient machine instructions.
* Documentation - In more expressive type systems, types can serve as a form of documentation, since they can illustrate the intent of the programmer. For instance, timestamps may be represented as integers—but if a programmer declares a function as returning a timestamp type rather than merely an integer type, this documents part of the meaning of the function.
* Abstraction (or modularity) - Types allow programmers to think about programs at a higher level than the bit or byte, not bothering with low-level implementation. For example, programmers can think of a string as a collection of character values instead of as a mere array of bytes. Or, types can allow programmers to express the interface between two subsystems. This helps localize the definitions required for interoperability of the subsystems and prevents inconsistencies when those subsystems communicate.

==== Static Type Languages ====
A programming language is said to use static typing when type checking is performed during compile-time as opposed to run-time.

C++, C#, Java

==== Dynamic Type Languages ====
A programming language is said to be dynamically typed, or just 'dynamic', when the majority of its type checking is performed at run-time as opposed to at compile-time.

Ruby, Python

== Example ==

[http://i.cmpnet.com/ddj/ddj/images/ddj9708d/9708df6.gif [2]]
Many software designers view patterns as a form of language-independent design. Pattern-Oriented Software Architectures: A System of Patterns, edited by Frank Buschmann (John Wiley & Sons, 1996), for instance, divides patterns into three main groups -- architectural patterns, design patterns, and idioms. Only the idioms (defined as "low-level patterns specific to a program language") are language dependent -- the other patterns (and the implicit pattern language) rise above the level of programming language, much as the unified modeling language (UML) provides a common way to express designs.

This idea of language independence is seductive. It is also misleading. While patterns are language independent, language choice limits the patterns that are possible, easily supported, and useful. Language also affects how applications are structured.

To illustrate, I'll examine some patterns often used with Objective-C, but not usually used (or used differently) with C++. Both languages are object-oriented extensions of C. The main difference between them is that C++ has compile-time binding and fairly strong typing while Objective-C uses the Smalltalk object model of dynamic binding and weak typing. I'll start by examining two idioms commonly found in Objective-C programming. While simple, these idioms illustrate some of the key Objective-C programming techniques (although I use NextStep classes and frameworks to illustrate points, what I say also holds true for more generic Objective-C environments). I'll also examine how three standard design patterns -- Visitor, Command, and Facade -- are implemented in Objective-C.

====The Facade Pattern====

You might have noticed a common thread in the patterns just discussed. Both of the idioms involve ways to break out pieces of code and put them in shared libraries or bundles. The design patterns show how to decouple objects from each other for maximal flexibility. I'll now examine a commonly used architectural pattern that describes a way to structure applications to take advantage of this flexibility.

In the good old days of structured programming, saving an application's state was simple. Programs were divided into data and functions, and saving consisted of calling the function that wrote the data to some storage area. In object-oriented applications, things become a little more difficult. To the extent that you practice information hiding, object serialization is the natural approach to take.

Unfortunately, if m is the number of object references and n is the number of objects, serialization is O(mlog(n)). This is far too slow for serialization to be the saving mechanism in many applications.

But an Objective-C program that uses the four previous patterns will almost certainly use lots of facades as well. Notice in Figure 6 that Facades look a lot like cut points in the object graph. This leads to the natural Objective-C solution to the speed problem for object serialization: Serialize each facade to a separate Serializer (make each facade responsible for serializing the subsystem it abstracts).

This can get complicated. If an object outside a subsystem bypasses a facade (and messages an object in a subsystem directly), then extra care must be taken during serialization (to avoid serializing objects to more than one location). And, deserializing (opening) becomes trickier as well -- objects that bypass a facade will need to find objects within the subsystem. In practice, this comes down to making the facades used in serialization Singletons and making certain that all connections to objects in the subsystem are mediated by the facade (so that, during deserialization, the connection can be restored).

== Conclusion ==

There are various levels of design recognition for generating repeatable solutions to commonly occurring programming problems in software design. Design patterns in this case have been met with criticism in whether it negates the agile product development process. From our example above we have shown that when implementing patterns across various languages of varying type systems a design pattern may not always resolve common problems efficiently. Thus, the idea of a language independent pattern recognition solution must be evaluated thoroughly when in considering from a static and dynamic point of view.

== References ==

All sources used to create this wiki are linked in the above text.

CSC/ECE 517 Fall 2009/wiki2 13 StaticDynamic

2009-10-09T01:59:26Z

Los Bravo: /* References */

'''Design Patterns from a Static/Dynamic Point of View'''

Clearly, Ruby offers more concise realizations of certain design patterns than Java does. Is this typical of dynamic o-o languages? Are there design patterns that any dynamically typed language can realize better than a statically typed language? Are there instances when a different pattern should be used in a dynamic language than a static language?

== Introduction ==
=== Design Pattern ===
A design pattern is a general reusable solution to a commonly occurring problem in software design. A design pattern is not a finished design that can be transformed directly into code. It is a description or template for how to solve a problem that can be used in many different situations. Object-oriented design patterns typically show relationships and interactions between classes or objects, without specifying the final application classes or objects that are involved.

[http://www.dofactory.com/Patterns/Patterns.aspx [1]]
{| border="1"
|-
!Name !! Description
|-
| Creational Patterns
|-
| Abstract Factory || Creates an instance of several families of classes
|-
| Builder || Separates object construction from its representation
|-
| Factory Method || Creates an instance of several derived classes
|-
| Prototype || A fully initialized instance to be copied or cloned
|-
| Singleton || A class of which only a single instance can exist
|-
| Structural Patterns
|-
| Adapter || Match interfaces of different classes
|-
| Bridge || Separates an object’s interface from its implementation
|-
| Composite || A tree structure of simple and composite objects
|-
| Decorator || Add responsibilities to objects dynamically
|-
| Facade || A single class that represents an entire subsystem
|-
| Flyweight || A fine-grained instance used for efficient sharing
|-
| Proxy || An object representing another object
|-
| Behavioral Patterns
|-
| Chain of Resp. || A way of passing a request between a chain of objects
|-
| Command || Encapsulate a command request as an object
|-
| Interpreter || A way to include language elements in a program
|-
| Iterator || Sequentially access the elements of a collection
|-
| Mediator || Defines simplified communication between classes
|-
| Memento || Capture and restore an object's internal state
|-
| Observer || A way of notifying change to a number of classes
|-
| State || Alter an object's behavior when its state changes
|-
| Strategy || Encapsulates an algorithm inside a class
|-
| Template Method || Defer the exact steps of an algorithm to a subclass
|-
| Visitor || Defines a new operation to a class without change
|}

=== Static/Dynamic Type Languages ===
Types usually have associations either with values in memory or with objects such as variables. Because any value simply consists of a sequence of bits in a computer, hardware makes no distinction even between memory addresses, instruction code, characters, integers and floating-point numbers. Assignment to a type informs programs and programmers how those bit collections should be treated.

Major functions provided by type systems include:

* Safety - Use of types may allow a compiler to detect meaningless or probably invalid code. For example, we can identify an expression "Hello, World" as invalid because the rules of arithmetic do not specify how to divide an integer by a string. As discussed below, strong typing offers more safety, but generally does not guarantee complete safety (see type-safety for more information).
* Optimization - Static type-checking may provide useful compile-time information. For example, if a type requires that a value must align in memory at a multiple of 4 bytes, the compiler may be able to use more efficient machine instructions.
* Documentation - In more expressive type systems, types can serve as a form of documentation, since they can illustrate the intent of the programmer. For instance, timestamps may be represented as integers—but if a programmer declares a function as returning a timestamp type rather than merely an integer type, this documents part of the meaning of the function.
* Abstraction (or modularity) - Types allow programmers to think about programs at a higher level than the bit or byte, not bothering with low-level implementation. For example, programmers can think of a string as a collection of character values instead of as a mere array of bytes. Or, types can allow programmers to express the interface between two subsystems. This helps localize the definitions required for interoperability of the subsystems and prevents inconsistencies when those subsystems communicate.

==== Static Type Languages ====
A programming language is said to use static typing when type checking is performed during compile-time as opposed to run-time.

C++, C#, Java

==== Dynamic Type Languages ====
A programming language is said to be dynamically typed, or just 'dynamic', when the majority of its type checking is performed at run-time as opposed to at compile-time.

Ruby, Python

== Example ==

[http://i.cmpnet.com/ddj/ddj/images/ddj9708d/9708df6.gif [2]]
Many software designers view patterns as a form of language-independent design. Pattern-Oriented Software Architectures: A System of Patterns, edited by Frank Buschmann (John Wiley & Sons, 1996), for instance, divides patterns into three main groups -- architectural patterns, design patterns, and idioms. Only the idioms (defined as "low-level patterns specific to a program language") are language dependent -- the other patterns (and the implicit pattern language) rise above the level of programming language, much as the unified modeling language (UML) provides a common way to express designs.

This idea of language independence is seductive. It is also misleading. While patterns are language independent, language choice limits the patterns that are possible, easily supported, and useful. Language also affects how applications are structured.

To illustrate, I'll examine some patterns often used with Objective-C, but not usually used (or used differently) with C++. Both languages are object-oriented extensions of C. The main difference between them is that C++ has compile-time binding and fairly strong typing while Objective-C uses the Smalltalk object model of dynamic binding and weak typing. I'll start by examining two idioms commonly found in Objective-C programming. While simple, these idioms illustrate some of the key Objective-C programming techniques (although I use NextStep classes and frameworks to illustrate points, what I say also holds true for more generic Objective-C environments). I'll also examine how three standard design patterns -- Visitor, Command, and Facade -- are implemented in Objective-C.

====Objective- C Idiom 1====

Use Weakly Typed Delegation to Implement Secondary Roles of Framework Objects. A framework is a set of objects designed to help users create a specific type of application or a specific part of an application. For most problem domains, there is a set of core abstractions that are independent of the framework. For example, consider a framework that helps you create a GUI. Almost every such framework includes an "Application" object. In NextStep and it is an Application, in Delphi's VCL it is TApplication, but the basic abstraction is the same. Similarly, all such frameworks contain some form of "Window," "Subview," "Button," and "Textfield." These framework objects are often the leaves on the framework's object graph.

Framework objects have a clearly defined role within any application. Application objects route events, and Window objects provide a place to draw. However, programmers often subclass objects to allow them to play a secondary role within an application. For example, Textfields are often subclassed within an application, giving them the ability to validate user input.

Standard object-oriented design principles suggest that secondary roles be implemented via the Strategy pattern. Since frameworks are usually developed separately and implemented as shared libraries, using a strongly typed language results in Figure 1[http://i.cmpnet.com/ddj/ddj/images/ddj9708d/9708df1.gif [3]]. However, Figure 1[http://i.cmpnet.com/ddj/ddj/images/ddj9708d/9708df1.gif [3]] can cause problems over the application life cycle. NextStep's Application object, for example, acquired nine new delegate methods between versions 2.0 and 3.3 of the framework. These were gradual modifications brought about by changes in how people use computers, as well as changes made to remedy oversights in the original design. In Figure 1[http://i.cmpnet.com/ddj/ddj/images/ddj9708d/9708df1.gif [3]], each of these changes would have required a recompilation of the application and a new release. Moreover, existing copies of the application installed on users' machines would need to be updated.

One solution to this problem is to implement a strict versioning system. For example, the Windows machine I use has three distinct versions of MSVCRT**.DLL, and five versions of MFC**.DLL. If I try to launch my copy of Visual Eiffel, an alert dialog tells me I have the wrong version of CT13D32.DLL.

At best, strict versioning is a stop-gap solution. Depending on my applications, I might load all five versions of MFC**.DLL into memory, defeating the point of shared libraries. Additionally, older applications won't automatically inherit new functionality (or have bugs repaired) -- they still use the older version of the framework. Moreover, minor updates to an application can become complex; if you want to use a feature found in the new version of the framework, you must update every object that depends on the framework (including all the strategy objects).

The Objective-C approach removes the abstract base class, giving the framework object a more complex setDelegate method. The framework object defines a set of strategic methods it will call if they are defined. Then, inside the setDelegate method, run-time type information (RTTI) determines which methods the delegate has implemented. If the delegate doesn't implement the strategic method, the framework object doesn't call it. This is illustrated in Listing One where the new delegate object is queried about each function. If the new delegate implements the function, the method pointer is obtained.

This approach eliminates the versioning problem -- older applications work with new frameworks. For example, most applications compiled under NextStep 2.0 can run using the shared libraries of NextStep 3.3. If the application needs to be updated to take advantage of a new feature in the framework, the necessary code change is minimal because only the object getting updated needs to be modified.

The essence of this idiom is the principle that the framework and application should evolve independently. It is not easy to see how to do this in a statically typed language.

== Conclusion ==

There are various levels of design recognition for generating repeatable solutions to commonly occurring programming problems in software design. Design patterns in this case have been met with criticism in whether it negates the agile product development process. From our example above we have shown that when implementing patterns across various languages of varying type systems a design pattern may not always resolve common problems efficiently. Thus, the idea of a language independent pattern recognition solution must be evaluated thoroughly when in considering from a static and dynamic point of view.

== References ==

All sources used to create this wiki are linked in the above text.

CSC/ECE 517 Fall 2009/wiki2 13 StaticDynamic

2009-10-09T01:57:00Z

Los Bravo: /* Objective- C Idiom 1 */

'''Design Patterns from a Static/Dynamic Point of View'''

Clearly, Ruby offers more concise realizations of certain design patterns than Java does. Is this typical of dynamic o-o languages? Are there design patterns that any dynamically typed language can realize better than a statically typed language? Are there instances when a different pattern should be used in a dynamic language than a static language?

== Introduction ==
=== Design Pattern ===
A design pattern is a general reusable solution to a commonly occurring problem in software design. A design pattern is not a finished design that can be transformed directly into code. It is a description or template for how to solve a problem that can be used in many different situations. Object-oriented design patterns typically show relationships and interactions between classes or objects, without specifying the final application classes or objects that are involved.

[http://www.dofactory.com/Patterns/Patterns.aspx [1]]
{| border="1"
|-
!Name !! Description
|-
| Creational Patterns
|-
| Abstract Factory || Creates an instance of several families of classes
|-
| Builder || Separates object construction from its representation
|-
| Factory Method || Creates an instance of several derived classes
|-
| Prototype || A fully initialized instance to be copied or cloned
|-
| Singleton || A class of which only a single instance can exist
|-
| Structural Patterns
|-
| Adapter || Match interfaces of different classes
|-
| Bridge || Separates an object’s interface from its implementation
|-
| Composite || A tree structure of simple and composite objects
|-
| Decorator || Add responsibilities to objects dynamically
|-
| Facade || A single class that represents an entire subsystem
|-
| Flyweight || A fine-grained instance used for efficient sharing
|-
| Proxy || An object representing another object
|-
| Behavioral Patterns
|-
| Chain of Resp. || A way of passing a request between a chain of objects
|-
| Command || Encapsulate a command request as an object
|-
| Interpreter || A way to include language elements in a program
|-
| Iterator || Sequentially access the elements of a collection
|-
| Mediator || Defines simplified communication between classes
|-
| Memento || Capture and restore an object's internal state
|-
| Observer || A way of notifying change to a number of classes
|-
| State || Alter an object's behavior when its state changes
|-
| Strategy || Encapsulates an algorithm inside a class
|-
| Template Method || Defer the exact steps of an algorithm to a subclass
|-
| Visitor || Defines a new operation to a class without change
|}

=== Static/Dynamic Type Languages ===
Types usually have associations either with values in memory or with objects such as variables. Because any value simply consists of a sequence of bits in a computer, hardware makes no distinction even between memory addresses, instruction code, characters, integers and floating-point numbers. Assignment to a type informs programs and programmers how those bit collections should be treated.

Major functions provided by type systems include:

* Safety - Use of types may allow a compiler to detect meaningless or probably invalid code. For example, we can identify an expression "Hello, World" as invalid because the rules of arithmetic do not specify how to divide an integer by a string. As discussed below, strong typing offers more safety, but generally does not guarantee complete safety (see type-safety for more information).
* Optimization - Static type-checking may provide useful compile-time information. For example, if a type requires that a value must align in memory at a multiple of 4 bytes, the compiler may be able to use more efficient machine instructions.
* Documentation - In more expressive type systems, types can serve as a form of documentation, since they can illustrate the intent of the programmer. For instance, timestamps may be represented as integers—but if a programmer declares a function as returning a timestamp type rather than merely an integer type, this documents part of the meaning of the function.
* Abstraction (or modularity) - Types allow programmers to think about programs at a higher level than the bit or byte, not bothering with low-level implementation. For example, programmers can think of a string as a collection of character values instead of as a mere array of bytes. Or, types can allow programmers to express the interface between two subsystems. This helps localize the definitions required for interoperability of the subsystems and prevents inconsistencies when those subsystems communicate.

==== Static Type Languages ====
A programming language is said to use static typing when type checking is performed during compile-time as opposed to run-time.

C++, C#, Java

==== Dynamic Type Languages ====
A programming language is said to be dynamically typed, or just 'dynamic', when the majority of its type checking is performed at run-time as opposed to at compile-time.

Ruby, Python

== Example ==

[http://i.cmpnet.com/ddj/ddj/images/ddj9708d/9708df6.gif [2]]
Many software designers view patterns as a form of language-independent design. Pattern-Oriented Software Architectures: A System of Patterns, edited by Frank Buschmann (John Wiley & Sons, 1996), for instance, divides patterns into three main groups -- architectural patterns, design patterns, and idioms. Only the idioms (defined as "low-level patterns specific to a program language") are language dependent -- the other patterns (and the implicit pattern language) rise above the level of programming language, much as the unified modeling language (UML) provides a common way to express designs.

This idea of language independence is seductive. It is also misleading. While patterns are language independent, language choice limits the patterns that are possible, easily supported, and useful. Language also affects how applications are structured.

To illustrate, I'll examine some patterns often used with Objective-C, but not usually used (or used differently) with C++. Both languages are object-oriented extensions of C. The main difference between them is that C++ has compile-time binding and fairly strong typing while Objective-C uses the Smalltalk object model of dynamic binding and weak typing. I'll start by examining two idioms commonly found in Objective-C programming. While simple, these idioms illustrate some of the key Objective-C programming techniques (although I use NextStep classes and frameworks to illustrate points, what I say also holds true for more generic Objective-C environments). I'll also examine how three standard design patterns -- Visitor, Command, and Facade -- are implemented in Objective-C.

====Objective- C Idiom 1====

Use Weakly Typed Delegation to Implement Secondary Roles of Framework Objects. A framework is a set of objects designed to help users create a specific type of application or a specific part of an application. For most problem domains, there is a set of core abstractions that are independent of the framework. For example, consider a framework that helps you create a GUI. Almost every such framework includes an "Application" object. In NextStep and it is an Application, in Delphi's VCL it is TApplication, but the basic abstraction is the same. Similarly, all such frameworks contain some form of "Window," "Subview," "Button," and "Textfield." These framework objects are often the leaves on the framework's object graph.

Framework objects have a clearly defined role within any application. Application objects route events, and Window objects provide a place to draw. However, programmers often subclass objects to allow them to play a secondary role within an application. For example, Textfields are often subclassed within an application, giving them the ability to validate user input.

Standard object-oriented design principles suggest that secondary roles be implemented via the Strategy pattern. Since frameworks are usually developed separately and implemented as shared libraries, using a strongly typed language results in Figure 1[http://i.cmpnet.com/ddj/ddj/images/ddj9708d/9708df1.gif [3]]. However, Figure 1[http://i.cmpnet.com/ddj/ddj/images/ddj9708d/9708df1.gif [3]] can cause problems over the application life cycle. NextStep's Application object, for example, acquired nine new delegate methods between versions 2.0 and 3.3 of the framework. These were gradual modifications brought about by changes in how people use computers, as well as changes made to remedy oversights in the original design. In Figure 1[http://i.cmpnet.com/ddj/ddj/images/ddj9708d/9708df1.gif [3]], each of these changes would have required a recompilation of the application and a new release. Moreover, existing copies of the application installed on users' machines would need to be updated.

One solution to this problem is to implement a strict versioning system. For example, the Windows machine I use has three distinct versions of MSVCRT**.DLL, and five versions of MFC**.DLL. If I try to launch my copy of Visual Eiffel, an alert dialog tells me I have the wrong version of CT13D32.DLL.

At best, strict versioning is a stop-gap solution. Depending on my applications, I might load all five versions of MFC**.DLL into memory, defeating the point of shared libraries. Additionally, older applications won't automatically inherit new functionality (or have bugs repaired) -- they still use the older version of the framework. Moreover, minor updates to an application can become complex; if you want to use a feature found in the new version of the framework, you must update every object that depends on the framework (including all the strategy objects).

The Objective-C approach removes the abstract base class, giving the framework object a more complex setDelegate method. The framework object defines a set of strategic methods it will call if they are defined. Then, inside the setDelegate method, run-time type information (RTTI) determines which methods the delegate has implemented. If the delegate doesn't implement the strategic method, the framework object doesn't call it. This is illustrated in Listing One where the new delegate object is queried about each function. If the new delegate implements the function, the method pointer is obtained.

This approach eliminates the versioning problem -- older applications work with new frameworks. For example, most applications compiled under NextStep 2.0 can run using the shared libraries of NextStep 3.3. If the application needs to be updated to take advantage of a new feature in the framework, the necessary code change is minimal because only the object getting updated needs to be modified.

The essence of this idiom is the principle that the framework and application should evolve independently. It is not easy to see how to do this in a statically typed language.

== Conclusion ==

There are various levels of design recognition for generating repeatable solutions to commonly occurring programming problems in software design. Design patterns in this case have been met with criticism in whether it negates the agile product development process. From our example above we have shown that when implementing patterns across various languages of varying type systems a design pattern may not always resolve common problems efficiently. Thus, the idea of a language independent pattern recognition solution must be evaluated thoroughly when in considering from a static and dynamic point of view.

== References ==

CSC/ECE 517 Fall 2009/wiki2 13 StaticDynamic

2009-10-09T01:53:40Z

Los Bravo: /* The Facade Pattern */

'''Design Patterns from a Static/Dynamic Point of View'''

Clearly, Ruby offers more concise realizations of certain design patterns than Java does. Is this typical of dynamic o-o languages? Are there design patterns that any dynamically typed language can realize better than a statically typed language? Are there instances when a different pattern should be used in a dynamic language than a static language?

== Introduction ==
=== Design Pattern ===
A design pattern is a general reusable solution to a commonly occurring problem in software design. A design pattern is not a finished design that can be transformed directly into code. It is a description or template for how to solve a problem that can be used in many different situations. Object-oriented design patterns typically show relationships and interactions between classes or objects, without specifying the final application classes or objects that are involved.

[http://www.dofactory.com/Patterns/Patterns.aspx [1]]
{| border="1"
|-
!Name !! Description
|-
| Creational Patterns
|-
| Abstract Factory || Creates an instance of several families of classes
|-
| Builder || Separates object construction from its representation
|-
| Factory Method || Creates an instance of several derived classes
|-
| Prototype || A fully initialized instance to be copied or cloned
|-
| Singleton || A class of which only a single instance can exist
|-
| Structural Patterns
|-
| Adapter || Match interfaces of different classes
|-
| Bridge || Separates an object’s interface from its implementation
|-
| Composite || A tree structure of simple and composite objects
|-
| Decorator || Add responsibilities to objects dynamically
|-
| Facade || A single class that represents an entire subsystem
|-
| Flyweight || A fine-grained instance used for efficient sharing
|-
| Proxy || An object representing another object
|-
| Behavioral Patterns
|-
| Chain of Resp. || A way of passing a request between a chain of objects
|-
| Command || Encapsulate a command request as an object
|-
| Interpreter || A way to include language elements in a program
|-
| Iterator || Sequentially access the elements of a collection
|-
| Mediator || Defines simplified communication between classes
|-
| Memento || Capture and restore an object's internal state
|-
| Observer || A way of notifying change to a number of classes
|-
| State || Alter an object's behavior when its state changes
|-
| Strategy || Encapsulates an algorithm inside a class
|-
| Template Method || Defer the exact steps of an algorithm to a subclass
|-
| Visitor || Defines a new operation to a class without change
|}

=== Static/Dynamic Type Languages ===
Types usually have associations either with values in memory or with objects such as variables. Because any value simply consists of a sequence of bits in a computer, hardware makes no distinction even between memory addresses, instruction code, characters, integers and floating-point numbers. Assignment to a type informs programs and programmers how those bit collections should be treated.

Major functions provided by type systems include:

* Safety - Use of types may allow a compiler to detect meaningless or probably invalid code. For example, we can identify an expression "Hello, World" as invalid because the rules of arithmetic do not specify how to divide an integer by a string. As discussed below, strong typing offers more safety, but generally does not guarantee complete safety (see type-safety for more information).
* Optimization - Static type-checking may provide useful compile-time information. For example, if a type requires that a value must align in memory at a multiple of 4 bytes, the compiler may be able to use more efficient machine instructions.
* Documentation - In more expressive type systems, types can serve as a form of documentation, since they can illustrate the intent of the programmer. For instance, timestamps may be represented as integers—but if a programmer declares a function as returning a timestamp type rather than merely an integer type, this documents part of the meaning of the function.
* Abstraction (or modularity) - Types allow programmers to think about programs at a higher level than the bit or byte, not bothering with low-level implementation. For example, programmers can think of a string as a collection of character values instead of as a mere array of bytes. Or, types can allow programmers to express the interface between two subsystems. This helps localize the definitions required for interoperability of the subsystems and prevents inconsistencies when those subsystems communicate.

==== Static Type Languages ====
A programming language is said to use static typing when type checking is performed during compile-time as opposed to run-time.

C++, C#, Java

==== Dynamic Type Languages ====
A programming language is said to be dynamically typed, or just 'dynamic', when the majority of its type checking is performed at run-time as opposed to at compile-time.

Ruby, Python

== Example ==

[http://i.cmpnet.com/ddj/ddj/images/ddj9708d/9708df6.gif [2]]
Many software designers view patterns as a form of language-independent design. Pattern-Oriented Software Architectures: A System of Patterns, edited by Frank Buschmann (John Wiley & Sons, 1996), for instance, divides patterns into three main groups -- architectural patterns, design patterns, and idioms. Only the idioms (defined as "low-level patterns specific to a program language") are language dependent -- the other patterns (and the implicit pattern language) rise above the level of programming language, much as the unified modeling language (UML) provides a common way to express designs.

This idea of language independence is seductive. It is also misleading. While patterns are language independent, language choice limits the patterns that are possible, easily supported, and useful. Language also affects how applications are structured.

To illustrate, I'll examine some patterns often used with Objective-C, but not usually used (or used differently) with C++. Both languages are object-oriented extensions of C. The main difference between them is that C++ has compile-time binding and fairly strong typing while Objective-C uses the Smalltalk object model of dynamic binding and weak typing. I'll start by examining two idioms commonly found in Objective-C programming. While simple, these idioms illustrate some of the key Objective-C programming techniques (although I use NextStep classes and frameworks to illustrate points, what I say also holds true for more generic Objective-C environments). I'll also examine how three standard design patterns -- Visitor, Command, and Facade -- are implemented in Objective-C.

====Objective- C Idiom 1====

Use Weakly Typed Delegation to Implement Secondary Roles of Framework Objects. A framework is a set of objects designed to help users create a specific type of application or a specific part of an application. For most problem domains, there is a set of core abstractions that are independent of the framework. For example, consider a framework that helps you create a GUI. Almost every such framework includes an "Application" object. In NextStep and it is an Application, in Delphi's VCL it is TApplication, but the basic abstraction is the same. Similarly, all such frameworks contain some form of "Window," "Subview," "Button," and "Textfield." These framework objects are often the leaves on the framework's object graph.

Framework objects have a clearly defined role within any application. Application objects route events, and Window objects provide a place to draw. However, programmers often subclass objects to allow them to play a secondary role within an application. For example, Textfields are often subclassed within an application, giving them the ability to validate user input.

Standard object-oriented design principles suggest that secondary roles be implemented via the Strategy pattern. Since frameworks are usually developed separately and implemented as shared libraries, using a strongly typed language results in Figure 1. However, Figure 1 can cause problems over the application life cycle. NextStep's Application object, for example, acquired nine new delegate methods between versions 2.0 and 3.3 of the framework. These were gradual modifications brought about by changes in how people use computers, as well as changes made to remedy oversights in the original design. In Figure 1, each of these changes would have required a recompilation of the application and a new release. Moreover, existing copies of the application installed on users' machines would need to be updated.

One solution to this problem is to implement a strict versioning system. For example, the Windows machine I use has three distinct versions of MSVCRT**.DLL, and five versions of MFC**.DLL. If I try to launch my copy of Visual Eiffel, an alert dialog tells me I have the wrong version of CT13D32.DLL.

At best, strict versioning is a stop-gap solution. Depending on my applications, I might load all five versions of MFC**.DLL into memory, defeating the point of shared libraries. Additionally, older applications won't automatically inherit new functionality (or have bugs repaired) -- they still use the older version of the framework. Moreover, minor updates to an application can become complex; if you want to use a feature found in the new version of the framework, you must update every object that depends on the framework (including all the strategy objects).

The Objective-C approach removes the abstract base class, giving the framework object a more complex setDelegate method. The framework object defines a set of strategic methods it will call if they are defined. Then, inside the setDelegate method, run-time type information (RTTI) determines which methods the delegate has implemented. If the delegate doesn't implement the strategic method, the framework object doesn't call it. This is illustrated in Listing One where the new delegate object is queried about each function. If the new delegate implements the function, the method pointer is obtained.

This approach eliminates the versioning problem -- older applications work with new frameworks. For example, most applications compiled under NextStep 2.0 can run using the shared libraries of NextStep 3.3. If the application needs to be updated to take advantage of a new feature in the framework, the necessary code change is minimal because only the object getting updated needs to be modified.

The essence of this idiom is the principle that the framework and application should evolve independently. It is not easy to see how to do this in a statically typed language.

== Conclusion ==

There are various levels of design recognition for generating repeatable solutions to commonly occurring programming problems in software design. Design patterns in this case have been met with criticism in whether it negates the agile product development process. From our example above we have shown that when implementing patterns across various languages of varying type systems a design pattern may not always resolve common problems efficiently. Thus, the idea of a language independent pattern recognition solution must be evaluated thoroughly when in considering from a static and dynamic point of view.

== References ==

CSC/ECE 517 Fall 2009/wiki2 13 StaticDynamic

2009-10-09T01:45:08Z

Los Bravo: /* Conclusion */

'''Design Patterns from a Static/Dynamic Point of View'''

Clearly, Ruby offers more concise realizations of certain design patterns than Java does. Is this typical of dynamic o-o languages? Are there design patterns that any dynamically typed language can realize better than a statically typed language? Are there instances when a different pattern should be used in a dynamic language than a static language?

== Introduction ==
=== Design Pattern ===
A design pattern is a general reusable solution to a commonly occurring problem in software design. A design pattern is not a finished design that can be transformed directly into code. It is a description or template for how to solve a problem that can be used in many different situations. Object-oriented design patterns typically show relationships and interactions between classes or objects, without specifying the final application classes or objects that are involved.

[http://www.dofactory.com/Patterns/Patterns.aspx [1]]
{| border="1"
|-
!Name !! Description
|-
| Creational Patterns
|-
| Abstract Factory || Creates an instance of several families of classes
|-
| Builder || Separates object construction from its representation
|-
| Factory Method || Creates an instance of several derived classes
|-
| Prototype || A fully initialized instance to be copied or cloned
|-
| Singleton || A class of which only a single instance can exist
|-
| Structural Patterns
|-
| Adapter || Match interfaces of different classes
|-
| Bridge || Separates an object’s interface from its implementation
|-
| Composite || A tree structure of simple and composite objects
|-
| Decorator || Add responsibilities to objects dynamically
|-
| Facade || A single class that represents an entire subsystem
|-
| Flyweight || A fine-grained instance used for efficient sharing
|-
| Proxy || An object representing another object
|-
| Behavioral Patterns
|-
| Chain of Resp. || A way of passing a request between a chain of objects
|-
| Command || Encapsulate a command request as an object
|-
| Interpreter || A way to include language elements in a program
|-
| Iterator || Sequentially access the elements of a collection
|-
| Mediator || Defines simplified communication between classes
|-
| Memento || Capture and restore an object's internal state
|-
| Observer || A way of notifying change to a number of classes
|-
| State || Alter an object's behavior when its state changes
|-
| Strategy || Encapsulates an algorithm inside a class
|-
| Template Method || Defer the exact steps of an algorithm to a subclass
|-
| Visitor || Defines a new operation to a class without change
|}

=== Static/Dynamic Type Languages ===
Types usually have associations either with values in memory or with objects such as variables. Because any value simply consists of a sequence of bits in a computer, hardware makes no distinction even between memory addresses, instruction code, characters, integers and floating-point numbers. Assignment to a type informs programs and programmers how those bit collections should be treated.

Major functions provided by type systems include:

* Safety - Use of types may allow a compiler to detect meaningless or probably invalid code. For example, we can identify an expression "Hello, World" as invalid because the rules of arithmetic do not specify how to divide an integer by a string. As discussed below, strong typing offers more safety, but generally does not guarantee complete safety (see type-safety for more information).
* Optimization - Static type-checking may provide useful compile-time information. For example, if a type requires that a value must align in memory at a multiple of 4 bytes, the compiler may be able to use more efficient machine instructions.
* Documentation - In more expressive type systems, types can serve as a form of documentation, since they can illustrate the intent of the programmer. For instance, timestamps may be represented as integers—but if a programmer declares a function as returning a timestamp type rather than merely an integer type, this documents part of the meaning of the function.
* Abstraction (or modularity) - Types allow programmers to think about programs at a higher level than the bit or byte, not bothering with low-level implementation. For example, programmers can think of a string as a collection of character values instead of as a mere array of bytes. Or, types can allow programmers to express the interface between two subsystems. This helps localize the definitions required for interoperability of the subsystems and prevents inconsistencies when those subsystems communicate.

==== Static Type Languages ====
A programming language is said to use static typing when type checking is performed during compile-time as opposed to run-time.

C++, C#, Java

==== Dynamic Type Languages ====
A programming language is said to be dynamically typed, or just 'dynamic', when the majority of its type checking is performed at run-time as opposed to at compile-time.

Ruby, Python

== Example ==

[http://i.cmpnet.com/ddj/ddj/images/ddj9708d/9708df6.gif [2]]
Many software designers view patterns as a form of language-independent design. Pattern-Oriented Software Architectures: A System of Patterns, edited by Frank Buschmann (John Wiley & Sons, 1996), for instance, divides patterns into three main groups -- architectural patterns, design patterns, and idioms. Only the idioms (defined as "low-level patterns specific to a program language") are language dependent -- the other patterns (and the implicit pattern language) rise above the level of programming language, much as the unified modeling language (UML) provides a common way to express designs.

This idea of language independence is seductive. It is also misleading. While patterns are language independent, language choice limits the patterns that are possible, easily supported, and useful. Language also affects how applications are structured.

To illustrate, I'll examine some patterns often used with Objective-C, but not usually used (or used differently) with C++. Both languages are object-oriented extensions of C. The main difference between them is that C++ has compile-time binding and fairly strong typing while Objective-C uses the Smalltalk object model of dynamic binding and weak typing. I'll start by examining two idioms commonly found in Objective-C programming. While simple, these idioms illustrate some of the key Objective-C programming techniques (although I use NextStep classes and frameworks to illustrate points, what I say also holds true for more generic Objective-C environments). I'll also examine how three standard design patterns -- Visitor, Command, and Facade -- are implemented in Objective-C.

====The Facade Pattern====

You might have noticed a common thread in the patterns just discussed. Both of the idioms involve ways to break out pieces of code and put them in shared libraries or bundles. The design patterns show how to decouple objects from each other for maximal flexibility. I'll now examine a commonly used architectural pattern that describes a way to structure applications to take advantage of this flexibility. In the good old days of structured programming, saving an application's state was simple. Programs were divided into data and functions, and saving consisted of calling the function that wrote the data to some storage area. In object-oriented applications, things become a little more difficult. To the extent that you practice information hiding, object serialization is the natural approach to take. Unfortunately, if m is the number of object references and n is the number of objects, serialization is O(mlog(n)). This is far too slow for serialization to be the saving mechanism in many applications.

But an Objective-C program that uses the four previous patterns will almost certainly use lots of facades as well. Notice here[http://www.ddj.com/184410252 [3]] that Facades look a lot like cut points in the object graph. This leads to the natural Objective-C solution to the speed problem for object serialization: Serialize each facade to a separate Serializer (make each facade responsible for serializing the subsystem it abstracts).

This can get complicated. If an object outside a subsystem bypasses a facade (and messages an object in a subsystem directly), then extra care must be taken during serialization (to avoid serializing objects to more than one location). And, deserializing (opening) becomes trickier as well -- objects that bypass a facade will need to find objects within the subsystem. In practice, this comes down to making the facades used in serialization Singletons and making certain that all connections to objects in the subsystem are mediated by the facade (so that, during deserialization, the connection can be restored).

== Conclusion ==

There are various levels of design recognition for generating repeatable solutions to commonly occurring programming problems in software design. Design patterns in this case have been met with criticism in whether it negates the agile product development process. From our example above we have shown that when implementing patterns across various languages of varying type systems a design pattern may not always resolve common problems efficiently. Thus, the idea of a language independent pattern recognition solution must be evaluated thoroughly when in considering from a static and dynamic point of view.

== References ==

CSC/ECE 517 Fall 2009/wiki2 13 StaticDynamic

2009-10-09T01:40:48Z

Los Bravo: /* Conclusion */

'''Design Patterns from a Static/Dynamic Point of View'''

Clearly, Ruby offers more concise realizations of certain design patterns than Java does. Is this typical of dynamic o-o languages? Are there design patterns that any dynamically typed language can realize better than a statically typed language? Are there instances when a different pattern should be used in a dynamic language than a static language?

== Introduction ==
=== Design Pattern ===
A design pattern is a general reusable solution to a commonly occurring problem in software design. A design pattern is not a finished design that can be transformed directly into code. It is a description or template for how to solve a problem that can be used in many different situations. Object-oriented design patterns typically show relationships and interactions between classes or objects, without specifying the final application classes or objects that are involved.

[http://www.dofactory.com/Patterns/Patterns.aspx [1]]
{| border="1"
|-
!Name !! Description
|-
| Creational Patterns
|-
| Abstract Factory || Creates an instance of several families of classes
|-
| Builder || Separates object construction from its representation
|-
| Factory Method || Creates an instance of several derived classes
|-
| Prototype || A fully initialized instance to be copied or cloned
|-
| Singleton || A class of which only a single instance can exist
|-
| Structural Patterns
|-
| Adapter || Match interfaces of different classes
|-
| Bridge || Separates an object’s interface from its implementation
|-
| Composite || A tree structure of simple and composite objects
|-
| Decorator || Add responsibilities to objects dynamically
|-
| Facade || A single class that represents an entire subsystem
|-
| Flyweight || A fine-grained instance used for efficient sharing
|-
| Proxy || An object representing another object
|-
| Behavioral Patterns
|-
| Chain of Resp. || A way of passing a request between a chain of objects
|-
| Command || Encapsulate a command request as an object
|-
| Interpreter || A way to include language elements in a program
|-
| Iterator || Sequentially access the elements of a collection
|-
| Mediator || Defines simplified communication between classes
|-
| Memento || Capture and restore an object's internal state
|-
| Observer || A way of notifying change to a number of classes
|-
| State || Alter an object's behavior when its state changes
|-
| Strategy || Encapsulates an algorithm inside a class
|-
| Template Method || Defer the exact steps of an algorithm to a subclass
|-
| Visitor || Defines a new operation to a class without change
|}

=== Static/Dynamic Type Languages ===
Types usually have associations either with values in memory or with objects such as variables. Because any value simply consists of a sequence of bits in a computer, hardware makes no distinction even between memory addresses, instruction code, characters, integers and floating-point numbers. Assignment to a type informs programs and programmers how those bit collections should be treated.

Major functions provided by type systems include:

* Safety - Use of types may allow a compiler to detect meaningless or probably invalid code. For example, we can identify an expression "Hello, World" as invalid because the rules of arithmetic do not specify how to divide an integer by a string. As discussed below, strong typing offers more safety, but generally does not guarantee complete safety (see type-safety for more information).
* Optimization - Static type-checking may provide useful compile-time information. For example, if a type requires that a value must align in memory at a multiple of 4 bytes, the compiler may be able to use more efficient machine instructions.
* Documentation - In more expressive type systems, types can serve as a form of documentation, since they can illustrate the intent of the programmer. For instance, timestamps may be represented as integers—but if a programmer declares a function as returning a timestamp type rather than merely an integer type, this documents part of the meaning of the function.
* Abstraction (or modularity) - Types allow programmers to think about programs at a higher level than the bit or byte, not bothering with low-level implementation. For example, programmers can think of a string as a collection of character values instead of as a mere array of bytes. Or, types can allow programmers to express the interface between two subsystems. This helps localize the definitions required for interoperability of the subsystems and prevents inconsistencies when those subsystems communicate.

==== Static Type Languages ====
A programming language is said to use static typing when type checking is performed during compile-time as opposed to run-time.

C++, C#, Java

==== Dynamic Type Languages ====
A programming language is said to be dynamically typed, or just 'dynamic', when the majority of its type checking is performed at run-time as opposed to at compile-time.

Ruby, Python

== Example ==

[http://i.cmpnet.com/ddj/ddj/images/ddj9708d/9708df6.gif [2]]
Many software designers view patterns as a form of language-independent design. Pattern-Oriented Software Architectures: A System of Patterns, edited by Frank Buschmann (John Wiley & Sons, 1996), for instance, divides patterns into three main groups -- architectural patterns, design patterns, and idioms. Only the idioms (defined as "low-level patterns specific to a program language") are language dependent -- the other patterns (and the implicit pattern language) rise above the level of programming language, much as the unified modeling language (UML) provides a common way to express designs.

This idea of language independence is seductive. It is also misleading. While patterns are language independent, language choice limits the patterns that are possible, easily supported, and useful. Language also affects how applications are structured.

To illustrate, I'll examine some patterns often used with Objective-C, but not usually used (or used differently) with C++. Both languages are object-oriented extensions of C. The main difference between them is that C++ has compile-time binding and fairly strong typing while Objective-C uses the Smalltalk object model of dynamic binding and weak typing. I'll start by examining two idioms commonly found in Objective-C programming. While simple, these idioms illustrate some of the key Objective-C programming techniques (although I use NextStep classes and frameworks to illustrate points, what I say also holds true for more generic Objective-C environments). I'll also examine how three standard design patterns -- Visitor, Command, and Facade -- are implemented in Objective-C.

====The Facade Pattern====

You might have noticed a common thread in the patterns just discussed. Both of the idioms involve ways to break out pieces of code and put them in shared libraries or bundles. The design patterns show how to decouple objects from each other for maximal flexibility. I'll now examine a commonly used architectural pattern that describes a way to structure applications to take advantage of this flexibility. In the good old days of structured programming, saving an application's state was simple. Programs were divided into data and functions, and saving consisted of calling the function that wrote the data to some storage area. In object-oriented applications, things become a little more difficult. To the extent that you practice information hiding, object serialization is the natural approach to take. Unfortunately, if m is the number of object references and n is the number of objects, serialization is O(mlog(n)). This is far too slow for serialization to be the saving mechanism in many applications.

But an Objective-C program that uses the four previous patterns will almost certainly use lots of facades as well. Notice here[http://www.ddj.com/184410252 [3]] that Facades look a lot like cut points in the object graph. This leads to the natural Objective-C solution to the speed problem for object serialization: Serialize each facade to a separate Serializer (make each facade responsible for serializing the subsystem it abstracts).

This can get complicated. If an object outside a subsystem bypasses a facade (and messages an object in a subsystem directly), then extra care must be taken during serialization (to avoid serializing objects to more than one location). And, deserializing (opening) becomes trickier as well -- objects that bypass a facade will need to find objects within the subsystem. In practice, this comes down to making the facades used in serialization Singletons and making certain that all connections to objects in the subsystem are mediated by the facade (so that, during deserialization, the connection can be restored).

== Conclusion ==

There are various levels of design recognition for generating repeatable solutions to commonly occurring programming problems in software design. Design patterns in this case have been met with criticism in whether it negates the agile product development process. The idea of a language independent pattern recognition solution must be evaluated thoroughly when in considering from a static and dynamic point of view.

== References ==

CSC/ECE 517 Fall 2009/wiki2 13 StaticDynamic

2009-10-09T01:23:40Z

Los Bravo: /* The Facade Pattern */

'''Design Patterns from a Static/Dynamic Point of View'''

Clearly, Ruby offers more concise realizations of certain design patterns than Java does. Is this typical of dynamic o-o languages? Are there design patterns that any dynamically typed language can realize better than a statically typed language? Are there instances when a different pattern should be used in a dynamic language than a static language?

== Introduction ==
=== Design Pattern ===
A design pattern is a general reusable solution to a commonly occurring problem in software design. A design pattern is not a finished design that can be transformed directly into code. It is a description or template for how to solve a problem that can be used in many different situations. Object-oriented design patterns typically show relationships and interactions between classes or objects, without specifying the final application classes or objects that are involved.

[http://www.dofactory.com/Patterns/Patterns.aspx [1]]
{| border="1"
|-
!Name !! Description
|-
| Creational Patterns
|-
| Abstract Factory || Creates an instance of several families of classes
|-
| Builder || Separates object construction from its representation
|-
| Factory Method || Creates an instance of several derived classes
|-
| Prototype || A fully initialized instance to be copied or cloned
|-
| Singleton || A class of which only a single instance can exist
|-
| Structural Patterns
|-
| Adapter || Match interfaces of different classes
|-
| Bridge || Separates an object’s interface from its implementation
|-
| Composite || A tree structure of simple and composite objects
|-
| Decorator || Add responsibilities to objects dynamically
|-
| Facade || A single class that represents an entire subsystem
|-
| Flyweight || A fine-grained instance used for efficient sharing
|-
| Proxy || An object representing another object
|-
| Behavioral Patterns
|-
| Chain of Resp. || A way of passing a request between a chain of objects
|-
| Command || Encapsulate a command request as an object
|-
| Interpreter || A way to include language elements in a program
|-
| Iterator || Sequentially access the elements of a collection
|-
| Mediator || Defines simplified communication between classes
|-
| Memento || Capture and restore an object's internal state
|-
| Observer || A way of notifying change to a number of classes
|-
| State || Alter an object's behavior when its state changes
|-
| Strategy || Encapsulates an algorithm inside a class
|-
| Template Method || Defer the exact steps of an algorithm to a subclass
|-
| Visitor || Defines a new operation to a class without change
|}

=== Static/Dynamic Type Languages ===
Types usually have associations either with values in memory or with objects such as variables. Because any value simply consists of a sequence of bits in a computer, hardware makes no distinction even between memory addresses, instruction code, characters, integers and floating-point numbers. Assignment to a type informs programs and programmers how those bit collections should be treated.

Major functions provided by type systems include:

* Safety - Use of types may allow a compiler to detect meaningless or probably invalid code. For example, we can identify an expression "Hello, World" as invalid because the rules of arithmetic do not specify how to divide an integer by a string. As discussed below, strong typing offers more safety, but generally does not guarantee complete safety (see type-safety for more information).
* Optimization - Static type-checking may provide useful compile-time information. For example, if a type requires that a value must align in memory at a multiple of 4 bytes, the compiler may be able to use more efficient machine instructions.
* Documentation - In more expressive type systems, types can serve as a form of documentation, since they can illustrate the intent of the programmer. For instance, timestamps may be represented as integers—but if a programmer declares a function as returning a timestamp type rather than merely an integer type, this documents part of the meaning of the function.
* Abstraction (or modularity) - Types allow programmers to think about programs at a higher level than the bit or byte, not bothering with low-level implementation. For example, programmers can think of a string as a collection of character values instead of as a mere array of bytes. Or, types can allow programmers to express the interface between two subsystems. This helps localize the definitions required for interoperability of the subsystems and prevents inconsistencies when those subsystems communicate.

==== Static Type Languages ====
A programming language is said to use static typing when type checking is performed during compile-time as opposed to run-time.

C++, C#, Java

==== Dynamic Type Languages ====
A programming language is said to be dynamically typed, or just 'dynamic', when the majority of its type checking is performed at run-time as opposed to at compile-time.

Ruby, Python

== Example ==

[http://i.cmpnet.com/ddj/ddj/images/ddj9708d/9708df6.gif [2]]
Many software designers view patterns as a form of language-independent design. Pattern-Oriented Software Architectures: A System of Patterns, edited by Frank Buschmann (John Wiley & Sons, 1996), for instance, divides patterns into three main groups -- architectural patterns, design patterns, and idioms. Only the idioms (defined as "low-level patterns specific to a program language") are language dependent -- the other patterns (and the implicit pattern language) rise above the level of programming language, much as the unified modeling language (UML) provides a common way to express designs.

This idea of language independence is seductive. It is also misleading. While patterns are language independent, language choice limits the patterns that are possible, easily supported, and useful. Language also affects how applications are structured.

To illustrate, I'll examine some patterns often used with Objective-C, but not usually used (or used differently) with C++. Both languages are object-oriented extensions of C. The main difference between them is that C++ has compile-time binding and fairly strong typing while Objective-C uses the Smalltalk object model of dynamic binding and weak typing. I'll start by examining two idioms commonly found in Objective-C programming. While simple, these idioms illustrate some of the key Objective-C programming techniques (although I use NextStep classes and frameworks to illustrate points, what I say also holds true for more generic Objective-C environments). I'll also examine how three standard design patterns -- Visitor, Command, and Facade -- are implemented in Objective-C.

====The Facade Pattern====

You might have noticed a common thread in the patterns just discussed. Both of the idioms involve ways to break out pieces of code and put them in shared libraries or bundles. The design patterns show how to decouple objects from each other for maximal flexibility. I'll now examine a commonly used architectural pattern that describes a way to structure applications to take advantage of this flexibility. In the good old days of structured programming, saving an application's state was simple. Programs were divided into data and functions, and saving consisted of calling the function that wrote the data to some storage area. In object-oriented applications, things become a little more difficult. To the extent that you practice information hiding, object serialization is the natural approach to take. Unfortunately, if m is the number of object references and n is the number of objects, serialization is O(mlog(n)). This is far too slow for serialization to be the saving mechanism in many applications.

But an Objective-C program that uses the four previous patterns will almost certainly use lots of facades as well. Notice here[http://www.ddj.com/184410252 [3]] that Facades look a lot like cut points in the object graph. This leads to the natural Objective-C solution to the speed problem for object serialization: Serialize each facade to a separate Serializer (make each facade responsible for serializing the subsystem it abstracts).

This can get complicated. If an object outside a subsystem bypasses a facade (and messages an object in a subsystem directly), then extra care must be taken during serialization (to avoid serializing objects to more than one location). And, deserializing (opening) becomes trickier as well -- objects that bypass a facade will need to find objects within the subsystem. In practice, this comes down to making the facades used in serialization Singletons and making certain that all connections to objects in the subsystem are mediated by the facade (so that, during deserialization, the connection can be restored).

== Conclusion ==
== References ==

CSC/ECE 517 Fall 2009/wiki2 13 StaticDynamic

2009-10-09T01:22:32Z

Los Bravo: /* Example */

'''Design Patterns from a Static/Dynamic Point of View'''

Clearly, Ruby offers more concise realizations of certain design patterns than Java does. Is this typical of dynamic o-o languages? Are there design patterns that any dynamically typed language can realize better than a statically typed language? Are there instances when a different pattern should be used in a dynamic language than a static language?

== Introduction ==
=== Design Pattern ===
A design pattern is a general reusable solution to a commonly occurring problem in software design. A design pattern is not a finished design that can be transformed directly into code. It is a description or template for how to solve a problem that can be used in many different situations. Object-oriented design patterns typically show relationships and interactions between classes or objects, without specifying the final application classes or objects that are involved.

[http://www.dofactory.com/Patterns/Patterns.aspx [1]]
{| border="1"
|-
!Name !! Description
|-
| Creational Patterns
|-
| Abstract Factory || Creates an instance of several families of classes
|-
| Builder || Separates object construction from its representation
|-
| Factory Method || Creates an instance of several derived classes
|-
| Prototype || A fully initialized instance to be copied or cloned
|-
| Singleton || A class of which only a single instance can exist
|-
| Structural Patterns
|-
| Adapter || Match interfaces of different classes
|-
| Bridge || Separates an object’s interface from its implementation
|-
| Composite || A tree structure of simple and composite objects
|-
| Decorator || Add responsibilities to objects dynamically
|-
| Facade || A single class that represents an entire subsystem
|-
| Flyweight || A fine-grained instance used for efficient sharing
|-
| Proxy || An object representing another object
|-
| Behavioral Patterns
|-
| Chain of Resp. || A way of passing a request between a chain of objects
|-
| Command || Encapsulate a command request as an object
|-
| Interpreter || A way to include language elements in a program
|-
| Iterator || Sequentially access the elements of a collection
|-
| Mediator || Defines simplified communication between classes
|-
| Memento || Capture and restore an object's internal state
|-
| Observer || A way of notifying change to a number of classes
|-
| State || Alter an object's behavior when its state changes
|-
| Strategy || Encapsulates an algorithm inside a class
|-
| Template Method || Defer the exact steps of an algorithm to a subclass
|-
| Visitor || Defines a new operation to a class without change
|}

=== Static/Dynamic Type Languages ===
Types usually have associations either with values in memory or with objects such as variables. Because any value simply consists of a sequence of bits in a computer, hardware makes no distinction even between memory addresses, instruction code, characters, integers and floating-point numbers. Assignment to a type informs programs and programmers how those bit collections should be treated.

Major functions provided by type systems include:

* Safety - Use of types may allow a compiler to detect meaningless or probably invalid code. For example, we can identify an expression "Hello, World" as invalid because the rules of arithmetic do not specify how to divide an integer by a string. As discussed below, strong typing offers more safety, but generally does not guarantee complete safety (see type-safety for more information).
* Optimization - Static type-checking may provide useful compile-time information. For example, if a type requires that a value must align in memory at a multiple of 4 bytes, the compiler may be able to use more efficient machine instructions.
* Documentation - In more expressive type systems, types can serve as a form of documentation, since they can illustrate the intent of the programmer. For instance, timestamps may be represented as integers—but if a programmer declares a function as returning a timestamp type rather than merely an integer type, this documents part of the meaning of the function.
* Abstraction (or modularity) - Types allow programmers to think about programs at a higher level than the bit or byte, not bothering with low-level implementation. For example, programmers can think of a string as a collection of character values instead of as a mere array of bytes. Or, types can allow programmers to express the interface between two subsystems. This helps localize the definitions required for interoperability of the subsystems and prevents inconsistencies when those subsystems communicate.

==== Static Type Languages ====
A programming language is said to use static typing when type checking is performed during compile-time as opposed to run-time.

C++, C#, Java

==== Dynamic Type Languages ====
A programming language is said to be dynamically typed, or just 'dynamic', when the majority of its type checking is performed at run-time as opposed to at compile-time.

Ruby, Python

== Example ==

[http://i.cmpnet.com/ddj/ddj/images/ddj9708d/9708df6.gif [2]]
Many software designers view patterns as a form of language-independent design. Pattern-Oriented Software Architectures: A System of Patterns, edited by Frank Buschmann (John Wiley & Sons, 1996), for instance, divides patterns into three main groups -- architectural patterns, design patterns, and idioms. Only the idioms (defined as "low-level patterns specific to a program language") are language dependent -- the other patterns (and the implicit pattern language) rise above the level of programming language, much as the unified modeling language (UML) provides a common way to express designs.

This idea of language independence is seductive. It is also misleading. While patterns are language independent, language choice limits the patterns that are possible, easily supported, and useful. Language also affects how applications are structured.

To illustrate, I'll examine some patterns often used with Objective-C, but not usually used (or used differently) with C++. Both languages are object-oriented extensions of C. The main difference between them is that C++ has compile-time binding and fairly strong typing while Objective-C uses the Smalltalk object model of dynamic binding and weak typing. I'll start by examining two idioms commonly found in Objective-C programming. While simple, these idioms illustrate some of the key Objective-C programming techniques (although I use NextStep classes and frameworks to illustrate points, what I say also holds true for more generic Objective-C environments). I'll also examine how three standard design patterns -- Visitor, Command, and Facade -- are implemented in Objective-C.

====The Facade Pattern====

You might have noticed a common thread in the patterns just discussed. Both of the idioms involve ways to break out pieces of code and put them in shared libraries or bundles. The design patterns show how to decouple objects from each other for maximal flexibility. I'll now examine a commonly used architectural pattern that describes a way to structure applications to take advantage of this flexibility. In the good old days of structured programming, saving an application's state was simple. Programs were divided into data and functions, and saving consisted of calling the function that wrote the data to some storage area. In object-oriented applications, things become a little more difficult. To the extent that you practice information hiding, object serialization is the natural approach to take. Unfortunately, if m is the number of object references and n is the number of objects, serialization is O(mlog(n)). This is far too slow for serialization to be the saving mechanism in many applications.

But an Objective-C program that uses the four previous patterns will almost certainly use lots of facades as well. Notice here[http://www.ddj.com/184410252 [3]] that Facades look a lot like cut points in the object graph. This leads to the natural Objective-C solution to the speed problem for object serialization: Serialize each facade to a separate Serializer (make each facade responsible for serializing the subsystem it abstracts). This can get complicated. If an object outside a subsystem bypasses a facade (and messages an object in a subsystem directly), then extra care must be taken during serialization (to avoid serializing objects to more than one location). And, deserializing (opening) becomes trickier as well -- objects that bypass a facade will need to find objects within the subsystem. In practice, this comes down to making the facades used in serialization Singletons and making certain that all connections to objects in the subsystem are mediated by the facade (so that, during deserialization, the connection can be restored).

== Conclusion ==
== References ==

CSC/ECE 517 Fall 2009/wiki2 13 StaticDynamic

2009-10-09T01:06:38Z

Los Bravo: /* Description */

'''Design Patterns from a Static/Dynamic Point of View'''

Clearly, Ruby offers more concise realizations of certain design patterns than Java does. Is this typical of dynamic o-o languages? Are there design patterns that any dynamically typed language can realize better than a statically typed language? Are there instances when a different pattern should be used in a dynamic language than a static language?

== Introduction ==
=== Design Pattern ===
A design pattern is a general reusable solution to a commonly occurring problem in software design. A design pattern is not a finished design that can be transformed directly into code. It is a description or template for how to solve a problem that can be used in many different situations. Object-oriented design patterns typically show relationships and interactions between classes or objects, without specifying the final application classes or objects that are involved.

[http://www.dofactory.com/Patterns/Patterns.aspx [1]]
{| border="1"
|-
!Name !! Description
|-
| Creational Patterns
|-
| Abstract Factory || Creates an instance of several families of classes
|-
| Builder || Separates object construction from its representation
|-
| Factory Method || Creates an instance of several derived classes
|-
| Prototype || A fully initialized instance to be copied or cloned
|-
| Singleton || A class of which only a single instance can exist
|-
| Structural Patterns
|-
| Adapter || Match interfaces of different classes
|-
| Bridge || Separates an object’s interface from its implementation
|-
| Composite || A tree structure of simple and composite objects
|-
| Decorator || Add responsibilities to objects dynamically
|-
| Facade || A single class that represents an entire subsystem
|-
| Flyweight || A fine-grained instance used for efficient sharing
|-
| Proxy || An object representing another object
|-
| Behavioral Patterns
|-
| Chain of Resp. || A way of passing a request between a chain of objects
|-
| Command || Encapsulate a command request as an object
|-
| Interpreter || A way to include language elements in a program
|-
| Iterator || Sequentially access the elements of a collection
|-
| Mediator || Defines simplified communication between classes
|-
| Memento || Capture and restore an object's internal state
|-
| Observer || A way of notifying change to a number of classes
|-
| State || Alter an object's behavior when its state changes
|-
| Strategy || Encapsulates an algorithm inside a class
|-
| Template Method || Defer the exact steps of an algorithm to a subclass
|-
| Visitor || Defines a new operation to a class without change
|}

=== Static/Dynamic Type Languages ===
Types usually have associations either with values in memory or with objects such as variables. Because any value simply consists of a sequence of bits in a computer, hardware makes no distinction even between memory addresses, instruction code, characters, integers and floating-point numbers. Assignment to a type informs programs and programmers how those bit collections should be treated.

Major functions provided by type systems include:

* Safety - Use of types may allow a compiler to detect meaningless or probably invalid code. For example, we can identify an expression "Hello, World" as invalid because the rules of arithmetic do not specify how to divide an integer by a string. As discussed below, strong typing offers more safety, but generally does not guarantee complete safety (see type-safety for more information).
* Optimization - Static type-checking may provide useful compile-time information. For example, if a type requires that a value must align in memory at a multiple of 4 bytes, the compiler may be able to use more efficient machine instructions.
* Documentation - In more expressive type systems, types can serve as a form of documentation, since they can illustrate the intent of the programmer. For instance, timestamps may be represented as integers—but if a programmer declares a function as returning a timestamp type rather than merely an integer type, this documents part of the meaning of the function.
* Abstraction (or modularity) - Types allow programmers to think about programs at a higher level than the bit or byte, not bothering with low-level implementation. For example, programmers can think of a string as a collection of character values instead of as a mere array of bytes. Or, types can allow programmers to express the interface between two subsystems. This helps localize the definitions required for interoperability of the subsystems and prevents inconsistencies when those subsystems communicate.

==== Static Type Languages ====
A programming language is said to use static typing when type checking is performed during compile-time as opposed to run-time.

C++, C#, Java

==== Dynamic Type Languages ====
A programming language is said to be dynamically typed, or just 'dynamic', when the majority of its type checking is performed at run-time as opposed to at compile-time.

Ruby, Python

== Example ==

[http://i.cmpnet.com/ddj/ddj/images/ddj9708d/9708df6.gif [2]]
Many software designers view patterns as a form of language-independent design. Pattern-Oriented Software Architectures: A System of Patterns, edited by Frank Buschmann (John Wiley & Sons, 1996), for instance, divides patterns into three main groups -- architectural patterns, design patterns, and idioms. Only the idioms (defined as "low-level patterns specific to a program language") are language dependent -- the other patterns (and the implicit pattern language) rise above the level of programming language, much as the unified modeling language (UML) provides a common way to express designs.

This idea of language independence is seductive. It is also misleading. While patterns are language independent, language choice limits the patterns that are possible, easily supported, and useful. Language also affects how applications are structured.

To illustrate, I'll examine some patterns often used with Objective-C, but not usually used (or used differently) with C++. Both languages are object-oriented extensions of C. The main difference between them is that C++ has compile-time binding and fairly strong typing while Objective-C uses the Smalltalk object model of dynamic binding and weak typing. I'll start by examining two idioms commonly found in Objective-C programming. While simple, these idioms illustrate some of the key Objective-C programming techniques (although I use NextStep classes and frameworks to illustrate points, what I say also holds true for more generic Objective-C environments). I'll also examine how three standard design patterns -- Visitor, Command, and Facade -- are implemented in Objective-C.

====The Facade Pattern====

You might have noticed a common thread in the patterns just discussed. Both of the idioms involve ways to break out pieces of code and put them in shared libraries or bundles. The design patterns show how to decouple objects from each other for maximal flexibility. I'll now examine a commonly used architectural pattern that describes a way to structure applications to take advantage of this flexibility. In the good old days of structured programming, saving an application's state was simple. Programs were divided into data and functions, and saving consisted of calling the function that wrote the data to some storage area. In object-oriented applications, things become a little more difficult. To the extent that you practice information hiding, object serialization is the natural approach to take. Unfortunately, if m is the number of object references and n is the number of objects, serialization is O(mlog(n)). This is far too slow for serialization to be the saving mechanism in many applications.

But an Objective-C program that uses the four previous patterns will almost certainly use lots of facades as well. Notice here that Facades look a lot like cut points in the object graph. This leads to the natural Objective-C solution to the speed problem for object serialization: Serialize each facade to a separate Serializer (make each facade responsible for serializing the subsystem it abstracts). This can get complicated. If an object outside a subsystem bypasses a facade (and messages an object in a subsystem directly), then extra care must be taken during serialization (to avoid serializing objects to more than one location). And, deserializing (opening) becomes trickier as well -- objects that bypass a facade will need to find objects within the subsystem. In practice, this comes down to making the facades used in serialization Singletons and making certain that all connections to objects in the subsystem are mediated by the facade (so that, during deserialization, the connection can be restored).

== Conclusion ==
== References ==

CSC/ECE 517 Fall 2009/wiki2 13 StaticDynamic

2009-10-09T01:05:23Z

Los Bravo: /* Example */

'''Design Patterns from a Static/Dynamic Point of View'''

Clearly, Ruby offers more concise realizations of certain design patterns than Java does. Is this typical of dynamic o-o languages? Are there design patterns that any dynamically typed language can realize better than a statically typed language? Are there instances when a different pattern should be used in a dynamic language than a static language?

== Introduction ==
=== Design Pattern ===
A design pattern is a general reusable solution to a commonly occurring problem in software design. A design pattern is not a finished design that can be transformed directly into code. It is a description or template for how to solve a problem that can be used in many different situations. Object-oriented design patterns typically show relationships and interactions between classes or objects, without specifying the final application classes or objects that are involved.

[http://www.dofactory.com/Patterns/Patterns.aspx [1]]
{| border="1"
|-
!Name !! Description
|-
| Creational Patterns
|-
| Abstract Factory || Creates an instance of several families of classes
|-
| Builder || Separates object construction from its representation
|-
| Factory Method || Creates an instance of several derived classes
|-
| Prototype || A fully initialized instance to be copied or cloned
|-
| Singleton || A class of which only a single instance can exist
|-
| Structural Patterns
|-
| Adapter || Match interfaces of different classes
|-
| Bridge || Separates an object’s interface from its implementation
|-
| Composite || A tree structure of simple and composite objects
|-
| Decorator || Add responsibilities to objects dynamically
|-
| Facade || A single class that represents an entire subsystem
|-
| Flyweight || A fine-grained instance used for efficient sharing
|-
| Proxy || An object representing another object
|-
| Behavioral Patterns
|-
| Chain of Resp. || A way of passing a request between a chain of objects
|-
| Command || Encapsulate a command request as an object
|-
| Interpreter || A way to include language elements in a program
|-
| Iterator || Sequentially access the elements of a collection
|-
| Mediator || Defines simplified communication between classes
|-
| Memento || Capture and restore an object's internal state
|-
| Observer || A way of notifying change to a number of classes
|-
| State || Alter an object's behavior when its state changes
|-
| Strategy || Encapsulates an algorithm inside a class
|-
| Template Method || Defer the exact steps of an algorithm to a subclass
|-
| Visitor || Defines a new operation to a class without change
|}

=== Static/Dynamic Type Languages ===
Types usually have associations either with values in memory or with objects such as variables. Because any value simply consists of a sequence of bits in a computer, hardware makes no distinction even between memory addresses, instruction code, characters, integers and floating-point numbers. Assignment to a type informs programs and programmers how those bit collections should be treated.

Major functions provided by type systems include:

* Safety - Use of types may allow a compiler to detect meaningless or probably invalid code. For example, we can identify an expression "Hello, World" as invalid because the rules of arithmetic do not specify how to divide an integer by a string. As discussed below, strong typing offers more safety, but generally does not guarantee complete safety (see type-safety for more information).
* Optimization - Static type-checking may provide useful compile-time information. For example, if a type requires that a value must align in memory at a multiple of 4 bytes, the compiler may be able to use more efficient machine instructions.
* Documentation - In more expressive type systems, types can serve as a form of documentation, since they can illustrate the intent of the programmer. For instance, timestamps may be represented as integers—but if a programmer declares a function as returning a timestamp type rather than merely an integer type, this documents part of the meaning of the function.
* Abstraction (or modularity) - Types allow programmers to think about programs at a higher level than the bit or byte, not bothering with low-level implementation. For example, programmers can think of a string as a collection of character values instead of as a mere array of bytes. Or, types can allow programmers to express the interface between two subsystems. This helps localize the definitions required for interoperability of the subsystems and prevents inconsistencies when those subsystems communicate.

==== Static Type Languages ====
A programming language is said to use static typing when type checking is performed during compile-time as opposed to run-time.

C++, C#, Java

==== Dynamic Type Languages ====
A programming language is said to be dynamically typed, or just 'dynamic', when the majority of its type checking is performed at run-time as opposed to at compile-time.

Ruby, Python

== Example ==

=Description=
[http://i.cmpnet.com/ddj/ddj/images/ddj9708d/9708df6.gif [2]]
Many software designers view patterns as a form of language-independent design. Pattern-Oriented Software Architectures: A System of Patterns, edited by Frank Buschmann (John Wiley & Sons, 1996), for instance, divides patterns into three main groups -- architectural patterns, design patterns, and idioms. Only the idioms (defined as "low-level patterns specific to a program language") are language dependent -- the other patterns (and the implicit pattern language) rise above the level of programming language, much as the unified modeling language (UML) provides a common way to express designs.

This idea of language independence is seductive. It is also misleading. While patterns are language independent, language choice limits the patterns that are possible, easily supported, and useful. Language also affects how applications are structured.

To illustrate, I'll examine some patterns often used with Objective-C, but not usually used (or used differently) with C++. Both languages are object-oriented extensions of C. The main difference between them is that C++ has compile-time binding and fairly strong typing while Objective-C uses the Smalltalk object model of dynamic binding and weak typing. I'll start by examining two idioms commonly found in Objective-C programming. While simple, these idioms illustrate some of the key Objective-C programming techniques (although I use NextStep classes and frameworks to illustrate points, what I say also holds true for more generic Objective-C environments). I'll also examine how three standard design patterns -- Visitor, Command, and Facade -- are implemented in Objective-C.

The Facade Pattern

You might have noticed a common thread in the patterns just discussed. Both of the idioms involve ways to break out pieces of code and put them in shared libraries or bundles. The design patterns show how to decouple objects from each other for maximal flexibility. I'll now examine a commonly used architectural pattern that describes a way to structure applications to take advantage of this flexibility. In the good old days of structured programming, saving an application's state was simple. Programs were divided into data and functions, and saving consisted of calling the function that wrote the data to some storage area. In object-oriented applications, things become a little more difficult. To the extent that you practice information hiding, object serialization is the natural approach to take. Unfortunately, if m is the number of object references and n is the number of objects, serialization is O(mlog(n)). This is far too slow for serialization to be the saving mechanism in many applications.

But an Objective-C program that uses the four previous patterns will almost certainly use lots of facades as well. Notice here that Facades look a lot like cut points in the object graph. This leads to the natural Objective-C solution to the speed problem for object serialization: Serialize each facade to a separate Serializer (make each facade responsible for serializing the subsystem it abstracts). This can get complicated. If an object outside a subsystem bypasses a facade (and messages an object in a subsystem directly), then extra care must be taken during serialization (to avoid serializing objects to more than one location). And, deserializing (opening) becomes trickier as well -- objects that bypass a facade will need to find objects within the subsystem. In practice, this comes down to making the facades used in serialization Singletons and making certain that all connections to objects in the subsystem are mediated by the facade (so that, during deserialization, the connection can be restored).

== Conclusion ==
== References ==

CSC/ECE 517 Fall 2009/wiki2 13 StaticDynamic

2009-10-09T01:01:55Z

Los Bravo: /* Example */

'''Design Patterns from a Static/Dynamic Point of View'''

Clearly, Ruby offers more concise realizations of certain design patterns than Java does. Is this typical of dynamic o-o languages? Are there design patterns that any dynamically typed language can realize better than a statically typed language? Are there instances when a different pattern should be used in a dynamic language than a static language?

== Introduction ==
=== Design Pattern ===
A design pattern is a general reusable solution to a commonly occurring problem in software design. A design pattern is not a finished design that can be transformed directly into code. It is a description or template for how to solve a problem that can be used in many different situations. Object-oriented design patterns typically show relationships and interactions between classes or objects, without specifying the final application classes or objects that are involved.

[http://www.dofactory.com/Patterns/Patterns.aspx [1]]
{| border="1"
|-
!Name !! Description
|-
| Creational Patterns
|-
| Abstract Factory || Creates an instance of several families of classes
|-
| Builder || Separates object construction from its representation
|-
| Factory Method || Creates an instance of several derived classes
|-
| Prototype || A fully initialized instance to be copied or cloned
|-
| Singleton || A class of which only a single instance can exist
|-
| Structural Patterns
|-
| Adapter || Match interfaces of different classes
|-
| Bridge || Separates an object’s interface from its implementation
|-
| Composite || A tree structure of simple and composite objects
|-
| Decorator || Add responsibilities to objects dynamically
|-
| Facade || A single class that represents an entire subsystem
|-
| Flyweight || A fine-grained instance used for efficient sharing
|-
| Proxy || An object representing another object
|-
| Behavioral Patterns
|-
| Chain of Resp. || A way of passing a request between a chain of objects
|-
| Command || Encapsulate a command request as an object
|-
| Interpreter || A way to include language elements in a program
|-
| Iterator || Sequentially access the elements of a collection
|-
| Mediator || Defines simplified communication between classes
|-
| Memento || Capture and restore an object's internal state
|-
| Observer || A way of notifying change to a number of classes
|-
| State || Alter an object's behavior when its state changes
|-
| Strategy || Encapsulates an algorithm inside a class
|-
| Template Method || Defer the exact steps of an algorithm to a subclass
|-
| Visitor || Defines a new operation to a class without change
|}

=== Static/Dynamic Type Languages ===
Types usually have associations either with values in memory or with objects such as variables. Because any value simply consists of a sequence of bits in a computer, hardware makes no distinction even between memory addresses, instruction code, characters, integers and floating-point numbers. Assignment to a type informs programs and programmers how those bit collections should be treated.

Major functions provided by type systems include:

* Safety - Use of types may allow a compiler to detect meaningless or probably invalid code. For example, we can identify an expression "Hello, World" as invalid because the rules of arithmetic do not specify how to divide an integer by a string. As discussed below, strong typing offers more safety, but generally does not guarantee complete safety (see type-safety for more information).
* Optimization - Static type-checking may provide useful compile-time information. For example, if a type requires that a value must align in memory at a multiple of 4 bytes, the compiler may be able to use more efficient machine instructions.
* Documentation - In more expressive type systems, types can serve as a form of documentation, since they can illustrate the intent of the programmer. For instance, timestamps may be represented as integers—but if a programmer declares a function as returning a timestamp type rather than merely an integer type, this documents part of the meaning of the function.
* Abstraction (or modularity) - Types allow programmers to think about programs at a higher level than the bit or byte, not bothering with low-level implementation. For example, programmers can think of a string as a collection of character values instead of as a mere array of bytes. Or, types can allow programmers to express the interface between two subsystems. This helps localize the definitions required for interoperability of the subsystems and prevents inconsistencies when those subsystems communicate.

==== Static Type Languages ====
A programming language is said to use static typing when type checking is performed during compile-time as opposed to run-time.

C++, C#, Java

==== Dynamic Type Languages ====
A programming language is said to be dynamically typed, or just 'dynamic', when the majority of its type checking is performed at run-time as opposed to at compile-time.

Ruby, Python

== Example ==

Many software designers view patterns as a form of language-independent design. Pattern-Oriented Software Architectures: A System of Patterns, edited by Frank Buschmann (John Wiley & Sons, 1996), for instance, divides patterns into three main groups -- architectural patterns, design patterns, and idioms. Only the idioms (defined as "low-level patterns specific to a program language") are language dependent -- the other patterns (and the implicit pattern language) rise above the level of programming language, much as the unified modeling language (UML) provides a common way to express designs.

This idea of language independence is seductive. It is also misleading. While patterns are language independent, language choice limits the patterns that are possible, easily supported, and useful. Language also affects how applications are structured.

To illustrate, I'll examine some patterns often used with Objective-C, but not usually used (or used differently) with C++. Both languages are object-oriented extensions of C. The main difference between them is that C++ has compile-time binding and fairly strong typing while Objective-C uses the Smalltalk object model of dynamic binding and weak typing. I'll start by examining two idioms commonly found in Objective-C programming. While simple, these idioms illustrate some of the key Objective-C programming techniques (although I use NextStep classes and frameworks to illustrate points, what I say also holds true for more generic Objective-C environments). I'll also examine how three standard design patterns -- Visitor, Command, and Facade -- are implemented in Objective-C.

The Facade Pattern

You might have noticed a common thread in the patterns just discussed. Both of the idioms involve ways to break out pieces of code and put them in shared libraries or bundles. The design patterns show how to decouple objects from each other for maximal flexibility. I'll now examine a commonly used architectural pattern that describes a way to structure applications to take advantage of this flexibility. In the good old days of structured programming, saving an application's state was simple. Programs were divided into data and functions, and saving consisted of calling the function that wrote the data to some storage area. In object-oriented applications, things become a little more difficult. To the extent that you practice information hiding, object serialization is the natural approach to take. Unfortunately, if m is the number of object references and n is the number of objects, serialization is O(mlog(n)). This is far too slow for serialization to be the saving mechanism in many applications.

But an Objective-C program that uses the four previous patterns will almost certainly use lots of facades as well. Notice here that Facades look a lot like cut points in the object graph. This leads to the natural Objective-C solution to the speed problem for object serialization: Serialize each facade to a separate Serializer (make each facade responsible for serializing the subsystem it abstracts). This can get complicated. If an object outside a subsystem bypasses a facade (and messages an object in a subsystem directly), then extra care must be taken during serialization (to avoid serializing objects to more than one location). And, deserializing (opening) becomes trickier as well -- objects that bypass a facade will need to find objects within the subsystem. In practice, this comes down to making the facades used in serialization Singletons and making certain that all connections to objects in the subsystem are mediated by the facade (so that, during deserialization, the connection can be restored).

== Conclusion ==
== References ==

CSC/ECE 517 Fall 2009/wiki1b team1

2009-09-28T20:12:11Z

Los Bravo: /* TDD: Test Driven Development */

CSC/ECE 517 Fall 2009

'''
== Resources for Rails (other than IDEs) ==
'''

IDEs are a valuable resource for Rails development, however there are many other resources and tools
that can either replace or supplement IDEs.

'''Resources for Rails other than IDEs
'''

'''''Rails API''''' - http://api.rubyonrails.org/

This site documents Rails files, classes and methods that can be used to build a Rails application.

'''''Rails Forum''''' - http://railsforum.com/

A discussion forum covering all aspects of Rails for beginners and experts including planning,
programming, extensions and production.

'''''Introducing Ruby on Rails'''''

Part 1 http://www.softwaredeveloper.com/features/intro-to-ruby-on-rails-042507/

Part 2 http://www.softwaredeveloper.com/features/intro-to-ruby-on-rails-part-two-043007/

An excellent introduction to Rails for novices

'''''Installers'''
''

Windows: InstantRails - http://instantrails.rubyforge.org/wiki/wiki.pl

An all in one, single click installer for Windows that includes a Rails server.

Mac: Locomotive - http://locomotive.raaum.org/

'''''Rails Projects''''' - http://www.workingwithrails.com/

A Database of Rails projects, programmers and websites

'''''Rails plugins''''' - http://agilewebdevelopment.com/

A collection of Rails open source plugins, searchable by category or keyword.

'''''Sample Rails''''' - http://snippets.dzone.com/tag/rails

A collection of Rails code snippets.

'''''Agile Rails book''''' - http://www.amazon.com/gp/product/097669400X/002-0481267-8083260?v=glance&n=283155

An excellent resource for learning how to apply Agile programming concepts to Rails.

'''''Rails cheatsheet''''' - http://www.blainekendall.com/uploads/RubyOnRails-Cheatsheet-BlaineKendall.pdf

One user's list of best practices, gotchas and quirks of developing with Rails.

'''''Rails best practices''''' - http://www.therailsway.com/

An official best practices list for programming in Rails.

'''''Advanced Rails''''' - http://webonrails.com/

A resource for the advanced Rails programmer.

'''''Rails Blog''''' - http://weblog.rubyonrails.org/

An online community of updates about current happenings with the Rails platform.

'''''Rails Guides''''' - http://guides.rubyonrails.org/

An all in one resource for learning Rails including Howtos, security and contributing to the Rails community.

'''''Authoring Rails plugins''''' - http://nubyonrails.com/articles/2006/05/04/the-complete-guide-to-rails-plugins-part-i

A complete guide to authoring your own Rails plugins.

'''

== '''Tools for Rails (other than IDEs)''' ==
'''

'''Test Unit'''
The Rails stack uses Test::Unit, known as the default Ruby unit testing framework shipping with Ruby. There are various plugins and extension that could be used with Rails built-in Test::Unit to extend its functionality for support of TDD and BDD testing practices.

[http://wiki.rubyonrails.org/addons/testing]
The link provides additional information in the form of supporting resources, whitepapers, examples, and plug-in documentation

'''Example'''
[http://wiki.rubyonrails.org/testing/test-unitrequire]

Image:class CalculatorTest < Test::Unit::TestCase
def test_add_two_numbers_for_the_sum
calculator = Calculator.new
assert_equal 4, calculator.sum(2, 2)
end
end

== TDD: Test Driven Development ==

Test Driven Development is a combination of refactoring and test first development, a form of development where the test is

written prior to completed production code. The goal of TDD is the specification of requirements and not the validation of

requirements. There are a few testing frameworks that are used to implement the TDD programming technique.

[http://ruby.about.com/b/2009/01/28/test-driven-development-with-rails.htm]
This link provides a comprehensive overview of test driven development practices and available resources for implementation.

'''RSpec'''
RSpec is a testing framework for Behavior Driven Development, complete with its own expectations, matchers and mocking and

stubbing facilities. It goes along hand in hand with Cucumber, though it plays nicely with many other testing frameworks as well.

''Example:''

The following code will fail during execution. ''Expresses some basic desired behavior''[http://rspec.info/]

<nowiki>#</nowiki> bowling_spec.rb
require ‘bowling’
describe Bowling do
it "should score 0 for gutter game" do
bowling = Bowling.new
20.times { bowling.hit(0) }
bowling.score.should == 0
end
end

The following code pass execution. ''Just enough code to make it pass.''[http://rspec.info/]

<nowiki>#</nowiki> bowling.rb
class Bowling
def hit(pins)
end
def score
0
end
end

[http://www.ibm.com/developerworks/web/library/wa-rspec/]
The link provides a brief overview of RSpec with a comprehensive series of examples and a conceptual view of Rpecs step by step

implementation process

'''Cucumber'''
Cucumber is used with TDD and BDD within other testing frameworks such as RSpec by letting software development teams describe how

software should behave in plain text. The text is written in a business-readable domain-specific language and serves as

documentation, automated tests and development-aid - all rolled into one format.

''Cucumber Example:''
Feature: Log in and out
As an administrator
I want to restrict access to certain portions of my site
In order to prevent users from changing the content
Scenario: Logging in
Given I am not logged in as an administrator
When I go to the administrative page
And I fill in the fields
| Username | admin |
| Password | secret |
And I press "Log in"
Then I should be on the administrative page
And I should see "Log out"
Scenario: Logging out
...

[http://cukes.info/]
The link provides a detail decription, definition, and examples of Cucumber implementation best practices and supported

frameworks.

''Another Cucumber Example:''
Scenario: See all vendors
Given I am logged in as a user in the administrator role
And There are 3 vendors
When I go to the manage vendors page
Then I should see the first 3 vendor names

'''Shoulda'''
An extension to Test::Unit with additional helpers, macros, and assertions.

[http://www.thoughtbot.com/projects/shoulda]
The link provides a more conclusive definition of Shoulda along with installation facts and working examples of the Shoulda

testing framework within Ruby's built in Test::Unit

''Shoulda Example with Test::Unit''[http://robots.thoughtbot.com/post/159805987/speculating-with-shoulda]

class UserTest < ActiveRecord::TestCase
should_belong_to :account
should_have_many :posts
should_validate_presence_of :email
should_allow_values_for :email, "test@example.com"
should_not_allow_values_for :email, "test"
end

== BDD: Behavior Driven Development ==
[http://eggsonbread.com/2009/07/22/behavior-driven-development-in-a-nutshell/]
Behavior driven development was born from the concepts behind the implementation of TDD. It brings together strands from

TestDrivenDevelopment and DomainDrivenDesign into an integrated whole, making the relationship between these two powerful

approaches to software development more evident. Most test driven development testing frameworks such as RSpec and Cucumber also support behavior driven development testing.

[http://behaviour-driven.org/]
The link supports BDDs definition with additional links to more viable behavior driven development resources.

----

'''Other Test Tool Resources'''

''Watir:'' is an open-source library for automating web browsers. It allows you to write tests that are easy to read and maintain. It

is simple and flexible.
[http://wtr.rubyforge.org/]
The link provides an overview of Watir with installation specifications, examples, and supported platforms

''NullDB:'' [http://avdi.org/projects/nulldb/]
a way to speed up testing by avoiding database use.

''Bleakhouse:'' memory leak detection
[http://www.rubyinside.com/bleakhouse-tool-to-find-memory-leaks-in-your-rails-applications-470.html]
The link gives additional information on Bleakhouse profiling for memory leaks

''ruby-debug:''
Other than the extensive use of breakpoints Rails provides little to streamline the debugging process. Ruby-debug provides Rails with a plug-in extending the functionality of Rails built in debugger.

[http://rubyforge.org/softwaremap/trove_list.php?form_cat=47]
The link provides twenty additional debug resources available for RoR

== '''Conclusion''' ==

Rails is a very comprehensive development environment for Ruby with numerous extensions, plugins, and other resources outside of IDEs to strengthen the functionality of the open source web application framework.

== References ==

''All sources used to create this wiki are linked in the above text.''

CSC/ECE 517 Fall 2009/wiki1b team1

2009-09-28T20:11:32Z

Los Bravo: /* TDD: Test Driven Development */

CSC/ECE 517 Fall 2009

'''
== Resources for Rails (other than IDEs) ==
'''

IDEs are a valuable resource for Rails development, however there are many other resources and tools
that can either replace or supplement IDEs.

'''Resources for Rails other than IDEs
'''

'''''Rails API''''' - http://api.rubyonrails.org/

This site documents Rails files, classes and methods that can be used to build a Rails application.

'''''Rails Forum''''' - http://railsforum.com/

A discussion forum covering all aspects of Rails for beginners and experts including planning,
programming, extensions and production.

'''''Introducing Ruby on Rails'''''

Part 1 http://www.softwaredeveloper.com/features/intro-to-ruby-on-rails-042507/

Part 2 http://www.softwaredeveloper.com/features/intro-to-ruby-on-rails-part-two-043007/

An excellent introduction to Rails for novices

'''''Installers'''
''

Windows: InstantRails - http://instantrails.rubyforge.org/wiki/wiki.pl

An all in one, single click installer for Windows that includes a Rails server.

Mac: Locomotive - http://locomotive.raaum.org/

'''''Rails Projects''''' - http://www.workingwithrails.com/

A Database of Rails projects, programmers and websites

'''''Rails plugins''''' - http://agilewebdevelopment.com/

A collection of Rails open source plugins, searchable by category or keyword.

'''''Sample Rails''''' - http://snippets.dzone.com/tag/rails

A collection of Rails code snippets.

'''''Agile Rails book''''' - http://www.amazon.com/gp/product/097669400X/002-0481267-8083260?v=glance&n=283155

An excellent resource for learning how to apply Agile programming concepts to Rails.

'''''Rails cheatsheet''''' - http://www.blainekendall.com/uploads/RubyOnRails-Cheatsheet-BlaineKendall.pdf

One user's list of best practices, gotchas and quirks of developing with Rails.

'''''Rails best practices''''' - http://www.therailsway.com/

An official best practices list for programming in Rails.

'''''Advanced Rails''''' - http://webonrails.com/

A resource for the advanced Rails programmer.

'''''Rails Blog''''' - http://weblog.rubyonrails.org/

An online community of updates about current happenings with the Rails platform.

'''''Rails Guides''''' - http://guides.rubyonrails.org/

An all in one resource for learning Rails including Howtos, security and contributing to the Rails community.

'''''Authoring Rails plugins''''' - http://nubyonrails.com/articles/2006/05/04/the-complete-guide-to-rails-plugins-part-i

A complete guide to authoring your own Rails plugins.

'''

== '''Tools for Rails (other than IDEs)''' ==
'''

'''Test Unit'''
The Rails stack uses Test::Unit, known as the default Ruby unit testing framework shipping with Ruby. There are various plugins and extension that could be used with Rails built-in Test::Unit to extend its functionality for support of TDD and BDD testing practices.

[http://wiki.rubyonrails.org/addons/testing]
The link provides additional information in the form of supporting resources, whitepapers, examples, and plug-in documentation

'''Example'''
[http://wiki.rubyonrails.org/testing/test-unitrequire]

Image:class CalculatorTest < Test::Unit::TestCase
def test_add_two_numbers_for_the_sum
calculator = Calculator.new
assert_equal 4, calculator.sum(2, 2)
end
end

== TDD: Test Driven Development ==

Test Driven Development is a combination of refactoring and test first development, a form of development where the test is

written prior to completed production code. The goal of TDD is the specification of requirements and not the validation of

requirements. There are a few testing frameworks that are used to implement the TDD programming technique.

[http://ruby.about.com/b/2009/01/28/test-driven-development-with-rails.htm]
This link provides a comprehensive overview of test driven development practices and available resources for implementation.

'''RSpec'''
RSpec is a testing framework for Behavior Driven Development, complete with its own expectations, matchers and mocking and

stubbing facilities. It goes along hand in hand with Cucumber, though it plays nicely with many other testing frameworks as well.

''Example:''

The following code will fail during execution. ''Expresses some basic desired behavior''[http://rspec.info/]

<nowiki>#</nowiki> bowling_spec.rb
require ‘bowling’
describe Bowling do
it "should score 0 for gutter game" do
bowling = Bowling.new
20.times { bowling.hit(0) }
bowling.score.should == 0
end
end

The following code pass execution. ''Just enough code to make it pass.''[http://rspec.info/]

<nowiki>#</nowiki> bowling.rb
class Bowling
def hit(pins)
end
def score
0
end
end

[http://www.ibm.com/developerworks/web/library/wa-rspec/]
The link provides a brief overview of RSpec with a comprehensive series of examples and a conceptual view of Rpecs step by step

implementation process

'''Cucumber'''
Cucumber is used with TDD and BDD within other testing frameworks such as RSpec by letting software development teams describe how

software should behave in plain text. The text is written in a business-readable domain-specific language and serves as

documentation, automated tests and development-aid - all rolled into one format.

''Cucumber Example:''
Feature: Log in and out
As an administrator
I want to restrict access to certain portions of my site
In order to prevent users from changing the content
Scenario: Logging in
Given I am not logged in as an administrator
When I go to the administrative page
And I fill in the fields
| Username | admin |
| Password | secret |
And I press "Log in"
Then I should be on the administrative page
And I should see "Log out"
Scenario: Logging out
...

[http://cukes.info/]
The link provides a detail decription, definition, and examples of Cucumber implementation best practices and supported

frameworks.

''Another Cucumber Example:''
Scenario: See all vendors
Given I am logged in as a user in the administrator role
And There are 3 vendors
When I go to the manage vendors page
Then I should see the first 3 vendor names

'''Shoulda'''
An extension to Test::Unit with additional helpers, macros, and assertions.

[http://www.thoughtbot.com/projects/shoulda]
The link provides a more conclusive definition of Shoulda along with installation facts and working examples of the Shoulda

testing framework within Ruby's built in Test::Unit

''Shoulda Example with Test::Unit''

class UserTest < ActiveRecord::TestCase
should_belong_to :account
should_have_many :posts
should_validate_presence_of :email
should_allow_values_for :email, "test@example.com"
should_not_allow_values_for :email, "test"
end

== BDD: Behavior Driven Development ==
[http://eggsonbread.com/2009/07/22/behavior-driven-development-in-a-nutshell/]
Behavior driven development was born from the concepts behind the implementation of TDD. It brings together strands from

TestDrivenDevelopment and DomainDrivenDesign into an integrated whole, making the relationship between these two powerful

approaches to software development more evident. Most test driven development testing frameworks such as RSpec and Cucumber also support behavior driven development testing.

[http://behaviour-driven.org/]
The link supports BDDs definition with additional links to more viable behavior driven development resources.

----

'''Other Test Tool Resources'''

''Watir:'' is an open-source library for automating web browsers. It allows you to write tests that are easy to read and maintain. It

is simple and flexible.
[http://wtr.rubyforge.org/]
The link provides an overview of Watir with installation specifications, examples, and supported platforms

''NullDB:'' [http://avdi.org/projects/nulldb/]
a way to speed up testing by avoiding database use.

''Bleakhouse:'' memory leak detection
[http://www.rubyinside.com/bleakhouse-tool-to-find-memory-leaks-in-your-rails-applications-470.html]
The link gives additional information on Bleakhouse profiling for memory leaks

''ruby-debug:''
Other than the extensive use of breakpoints Rails provides little to streamline the debugging process. Ruby-debug provides Rails with a plug-in extending the functionality of Rails built in debugger.

[http://rubyforge.org/softwaremap/trove_list.php?form_cat=47]
The link provides twenty additional debug resources available for RoR

== '''Conclusion''' ==

Rails is a very comprehensive development environment for Ruby with numerous extensions, plugins, and other resources outside of IDEs to strengthen the functionality of the open source web application framework.

== References ==

''All sources used to create this wiki are linked in the above text.''

CSC/ECE 517 Fall 2009/wiki1b team1

2009-09-28T20:09:03Z

Los Bravo: /* TDD: Test Driven Development */

CSC/ECE 517 Fall 2009

'''
== Resources for Rails (other than IDEs) ==
'''

IDEs are a valuable resource for Rails development, however there are many other resources and tools
that can either replace or supplement IDEs.

'''Resources for Rails other than IDEs
'''

'''''Rails API''''' - http://api.rubyonrails.org/

This site documents Rails files, classes and methods that can be used to build a Rails application.

'''''Rails Forum''''' - http://railsforum.com/

A discussion forum covering all aspects of Rails for beginners and experts including planning,
programming, extensions and production.

'''''Introducing Ruby on Rails'''''

Part 1 http://www.softwaredeveloper.com/features/intro-to-ruby-on-rails-042507/

Part 2 http://www.softwaredeveloper.com/features/intro-to-ruby-on-rails-part-two-043007/

An excellent introduction to Rails for novices

'''''Installers'''
''

Windows: InstantRails - http://instantrails.rubyforge.org/wiki/wiki.pl

An all in one, single click installer for Windows that includes a Rails server.

Mac: Locomotive - http://locomotive.raaum.org/

'''''Rails Projects''''' - http://www.workingwithrails.com/

A Database of Rails projects, programmers and websites

'''''Rails plugins''''' - http://agilewebdevelopment.com/

A collection of Rails open source plugins, searchable by category or keyword.

'''''Sample Rails''''' - http://snippets.dzone.com/tag/rails

A collection of Rails code snippets.

'''''Agile Rails book''''' - http://www.amazon.com/gp/product/097669400X/002-0481267-8083260?v=glance&n=283155

An excellent resource for learning how to apply Agile programming concepts to Rails.

'''''Rails cheatsheet''''' - http://www.blainekendall.com/uploads/RubyOnRails-Cheatsheet-BlaineKendall.pdf

One user's list of best practices, gotchas and quirks of developing with Rails.

'''''Rails best practices''''' - http://www.therailsway.com/

An official best practices list for programming in Rails.

'''''Advanced Rails''''' - http://webonrails.com/

A resource for the advanced Rails programmer.

'''''Rails Blog''''' - http://weblog.rubyonrails.org/

An online community of updates about current happenings with the Rails platform.

'''''Rails Guides''''' - http://guides.rubyonrails.org/

An all in one resource for learning Rails including Howtos, security and contributing to the Rails community.

'''''Authoring Rails plugins''''' - http://nubyonrails.com/articles/2006/05/04/the-complete-guide-to-rails-plugins-part-i

A complete guide to authoring your own Rails plugins.

'''

== '''Tools for Rails (other than IDEs)''' ==
'''

'''Test Unit'''
The Rails stack uses Test::Unit, known as the default Ruby unit testing framework shipping with Ruby. There are various plugins and extension that could be used with Rails built-in Test::Unit to extend its functionality for support of TDD and BDD testing practices.

[http://wiki.rubyonrails.org/addons/testing]
The link provides additional information in the form of supporting resources, whitepapers, examples, and plug-in documentation

'''Example'''
[http://wiki.rubyonrails.org/testing/test-unitrequire]

Image:class CalculatorTest < Test::Unit::TestCase
def test_add_two_numbers_for_the_sum
calculator = Calculator.new
assert_equal 4, calculator.sum(2, 2)
end
end

== TDD: Test Driven Development ==

Test Driven Development is a combination of refactoring and test first development, a form of development where the test is

written prior to completed production code. The goal of TDD is the specification of requirements and not the validation of

requirements. There are a few testing frameworks that are used to implement the TDD programming technique.

[http://ruby.about.com/b/2009/01/28/test-driven-development-with-rails.htm]
This link provides a comprehensive overview of test driven development practices and available resources for implementation.

'''RSpec'''
RSpec is a testing framework for Behavior Driven Development, complete with its own expectations, matchers and mocking and

stubbing facilities. It goes along hand in hand with Cucumber, though it plays nicely with many other testing frameworks as well.

''Example:''

The following code will fail during execution. ''Expresses some basic desired behavior''[http://rspec.info/]

<nowiki>#</nowiki> bowling_spec.rb
require ‘bowling’
describe Bowling do
it "should score 0 for gutter game" do
bowling = Bowling.new
20.times { bowling.hit(0) }
bowling.score.should == 0
end
end

The following code pass execution. ''Just enough code to make it pass.''[http://rspec.info/]

<nowiki>#</nowiki> bowling.rb
class Bowling
def hit(pins)
end
def score
0
end
end

[http://www.ibm.com/developerworks/web/library/wa-rspec/]
The link provides a brief overview of RSpec with a comprehensive series of examples and a conceptual view of Rpecs step by step

implementation process

'''Cucumber'''
Cucumber is used with TDD and BDD within other testing frameworks such as RSpec by letting software development teams describe how

software should behave in plain text. The text is written in a business-readable domain-specific language and serves as

documentation, automated tests and development-aid - all rolled into one format.

''Cucumber Example:''
Feature: Log in and out
As an administrator
I want to restrict access to certain portions of my site
In order to prevent users from changing the content
Scenario: Logging in
Given I am not logged in as an administrator
When I go to the administrative page
And I fill in the fields
| Username | admin |
| Password | secret |
And I press "Log in"
Then I should be on the administrative page
And I should see "Log out"
Scenario: Logging out
...

[http://cukes.info/]
The link provides a detail decription, definition, and examples of Cucumber implementation best practices and supported

frameworks.

''Another Cucumber Example:''
Scenario: See all vendors
Given I am logged in as a user in the administrator role
And There are 3 vendors
When I go to the manage vendors page
Then I should see the first 3 vendor names

'''Shoulda'''
An extension to Test::Unit with additional helpers, macros, and assertions.

[http://www.thoughtbot.com/projects/shoulda]
The link provides a more conclusive definition of Shoulda along with installation facts and working examples of the Shoulda

testing framework within Ruby's built in Test::Unit

== BDD: Behavior Driven Development ==
[http://eggsonbread.com/2009/07/22/behavior-driven-development-in-a-nutshell/]
Behavior driven development was born from the concepts behind the implementation of TDD. It brings together strands from

TestDrivenDevelopment and DomainDrivenDesign into an integrated whole, making the relationship between these two powerful

approaches to software development more evident. Most test driven development testing frameworks such as RSpec and Cucumber also support behavior driven development testing.

[http://behaviour-driven.org/]
The link supports BDDs definition with additional links to more viable behavior driven development resources.

----

'''Other Test Tool Resources'''

''Watir:'' is an open-source library for automating web browsers. It allows you to write tests that are easy to read and maintain. It

is simple and flexible.
[http://wtr.rubyforge.org/]
The link provides an overview of Watir with installation specifications, examples, and supported platforms

''NullDB:'' [http://avdi.org/projects/nulldb/]
a way to speed up testing by avoiding database use.

''Bleakhouse:'' memory leak detection
[http://www.rubyinside.com/bleakhouse-tool-to-find-memory-leaks-in-your-rails-applications-470.html]
The link gives additional information on Bleakhouse profiling for memory leaks

''ruby-debug:''
Other than the extensive use of breakpoints Rails provides little to streamline the debugging process. Ruby-debug provides Rails with a plug-in extending the functionality of Rails built in debugger.

[http://rubyforge.org/softwaremap/trove_list.php?form_cat=47]
The link provides twenty additional debug resources available for RoR

== '''Conclusion''' ==

Rails is a very comprehensive development environment for Ruby with numerous extensions, plugins, and other resources outside of IDEs to strengthen the functionality of the open source web application framework.

== References ==

''All sources used to create this wiki are linked in the above text.''

CSC/ECE 517 Fall 2009/wiki1b team1

2009-09-28T20:08:29Z

Los Bravo: /* TDD: Test Driven Development */

CSC/ECE 517 Fall 2009

'''
== Resources for Rails (other than IDEs) ==
'''

IDEs are a valuable resource for Rails development, however there are many other resources and tools
that can either replace or supplement IDEs.

'''Resources for Rails other than IDEs
'''

'''''Rails API''''' - http://api.rubyonrails.org/

This site documents Rails files, classes and methods that can be used to build a Rails application.

'''''Rails Forum''''' - http://railsforum.com/

A discussion forum covering all aspects of Rails for beginners and experts including planning,
programming, extensions and production.

'''''Introducing Ruby on Rails'''''

Part 1 http://www.softwaredeveloper.com/features/intro-to-ruby-on-rails-042507/

Part 2 http://www.softwaredeveloper.com/features/intro-to-ruby-on-rails-part-two-043007/

An excellent introduction to Rails for novices

'''''Installers'''
''

Windows: InstantRails - http://instantrails.rubyforge.org/wiki/wiki.pl

An all in one, single click installer for Windows that includes a Rails server.

Mac: Locomotive - http://locomotive.raaum.org/

'''''Rails Projects''''' - http://www.workingwithrails.com/

A Database of Rails projects, programmers and websites

'''''Rails plugins''''' - http://agilewebdevelopment.com/

A collection of Rails open source plugins, searchable by category or keyword.

'''''Sample Rails''''' - http://snippets.dzone.com/tag/rails

A collection of Rails code snippets.

'''''Agile Rails book''''' - http://www.amazon.com/gp/product/097669400X/002-0481267-8083260?v=glance&n=283155

An excellent resource for learning how to apply Agile programming concepts to Rails.

'''''Rails cheatsheet''''' - http://www.blainekendall.com/uploads/RubyOnRails-Cheatsheet-BlaineKendall.pdf

One user's list of best practices, gotchas and quirks of developing with Rails.

'''''Rails best practices''''' - http://www.therailsway.com/

An official best practices list for programming in Rails.

'''''Advanced Rails''''' - http://webonrails.com/

A resource for the advanced Rails programmer.

'''''Rails Blog''''' - http://weblog.rubyonrails.org/

An online community of updates about current happenings with the Rails platform.

'''''Rails Guides''''' - http://guides.rubyonrails.org/

An all in one resource for learning Rails including Howtos, security and contributing to the Rails community.

'''''Authoring Rails plugins''''' - http://nubyonrails.com/articles/2006/05/04/the-complete-guide-to-rails-plugins-part-i

A complete guide to authoring your own Rails plugins.

'''

== '''Tools for Rails (other than IDEs)''' ==
'''

'''Test Unit'''
The Rails stack uses Test::Unit, known as the default Ruby unit testing framework shipping with Ruby. There are various plugins and extension that could be used with Rails built-in Test::Unit to extend its functionality for support of TDD and BDD testing practices.

[http://wiki.rubyonrails.org/addons/testing]
The link provides additional information in the form of supporting resources, whitepapers, examples, and plug-in documentation

'''Example'''
[http://wiki.rubyonrails.org/testing/test-unitrequire]

Image:class CalculatorTest < Test::Unit::TestCase
def test_add_two_numbers_for_the_sum
calculator = Calculator.new
assert_equal 4, calculator.sum(2, 2)
end
end

== TDD: Test Driven Development ==

Test Driven Development is a combination of refactoring and test first development, a form of development where the test is

written prior to completed production code. The goal of TDD is the specification of requirements and not the validation of

requirements. There are a few testing frameworks that are used to implement the TDD programming technique.

[http://ruby.about.com/b/2009/01/28/test-driven-development-with-rails.htm]
This link provides a comprehensive overview of test driven development practices and available resources for implementation.

'''RSpec'''
RSpec is a testing framework for Behavior Driven Development, complete with its own expectations, matchers and mocking and

stubbing facilities. It goes along hand in hand with Cucumber, though it plays nicely with many other testing frameworks as well.

''Example''

The following code will fail during execution. ''Expresses some basic desired behavior''[http://rspec.info/]

<nowiki>#</nowiki> bowling_spec.rb
require ‘bowling’
describe Bowling do
it "should score 0 for gutter game" do
bowling = Bowling.new
20.times { bowling.hit(0) }
bowling.score.should == 0
end
end

The following code pass execution. ''Just enough code to make it pass.''[http://rspec.info/]

<nowiki>#</nowiki> bowling.rb
class Bowling
def hit(pins)
end
def score
0
end
end

[http://www.ibm.com/developerworks/web/library/wa-rspec/]
The link provides a brief overview of RSpec with a comprehensive series of examples and a conceptual view of Rpecs step by step

implementation process

'''Cucumber'''
Cucumber is used with TDD and BDD within other testing frameworks such as RSpec by letting software development teams describe how

software should behave in plain text. The text is written in a business-readable domain-specific language and serves as

documentation, automated tests and development-aid - all rolled into one format.

'''Another Cucumber Example:'''
Feature: Log in and out
As an administrator
I want to restrict access to certain portions of my site
In order to prevent users from changing the content
Scenario: Logging in
Given I am not logged in as an administrator
When I go to the administrative page
And I fill in the fields
| Username | admin |
| Password | secret |
And I press "Log in"
Then I should be on the administrative page
And I should see "Log out"
Scenario: Logging out
...

[http://cukes.info/]
The link provides a detail decription, definition, and examples of Cucumber implementation best practices and supported

frameworks.

'''Another Cucumber Example:'''
Scenario: See all vendors
Given I am logged in as a user in the administrator role
And There are 3 vendors
When I go to the manage vendors page
Then I should see the first 3 vendor names

'''Shoulda'''
An extension to Test::Unit with additional helpers, macros, and assertions.

[http://www.thoughtbot.com/projects/shoulda]
The link provides a more conclusive definition of Shoulda along with installation facts and working examples of the Shoulda

testing framework within Ruby's built in Test::Unit

== BDD: Behavior Driven Development ==
[http://eggsonbread.com/2009/07/22/behavior-driven-development-in-a-nutshell/]
Behavior driven development was born from the concepts behind the implementation of TDD. It brings together strands from

TestDrivenDevelopment and DomainDrivenDesign into an integrated whole, making the relationship between these two powerful

approaches to software development more evident. Most test driven development testing frameworks such as RSpec and Cucumber also support behavior driven development testing.

[http://behaviour-driven.org/]
The link supports BDDs definition with additional links to more viable behavior driven development resources.

----

'''Other Test Tool Resources'''

''Watir:'' is an open-source library for automating web browsers. It allows you to write tests that are easy to read and maintain. It

is simple and flexible.
[http://wtr.rubyforge.org/]
The link provides an overview of Watir with installation specifications, examples, and supported platforms

''NullDB:'' [http://avdi.org/projects/nulldb/]
a way to speed up testing by avoiding database use.

''Bleakhouse:'' memory leak detection
[http://www.rubyinside.com/bleakhouse-tool-to-find-memory-leaks-in-your-rails-applications-470.html]
The link gives additional information on Bleakhouse profiling for memory leaks

''ruby-debug:''
Other than the extensive use of breakpoints Rails provides little to streamline the debugging process. Ruby-debug provides Rails with a plug-in extending the functionality of Rails built in debugger.

[http://rubyforge.org/softwaremap/trove_list.php?form_cat=47]
The link provides twenty additional debug resources available for RoR

== '''Conclusion''' ==

Rails is a very comprehensive development environment for Ruby with numerous extensions, plugins, and other resources outside of IDEs to strengthen the functionality of the open source web application framework.

== References ==

''All sources used to create this wiki are linked in the above text.''

CSC/ECE 517 Fall 2009/wiki1b team1

2009-09-28T20:07:47Z

Los Bravo: /* TDD: Test Driven Development */

CSC/ECE 517 Fall 2009

'''
== Resources for Rails (other than IDEs) ==
'''

IDEs are a valuable resource for Rails development, however there are many other resources and tools
that can either replace or supplement IDEs.

'''Resources for Rails other than IDEs
'''

'''''Rails API''''' - http://api.rubyonrails.org/

This site documents Rails files, classes and methods that can be used to build a Rails application.

'''''Rails Forum''''' - http://railsforum.com/

A discussion forum covering all aspects of Rails for beginners and experts including planning,
programming, extensions and production.

'''''Introducing Ruby on Rails'''''

Part 1 http://www.softwaredeveloper.com/features/intro-to-ruby-on-rails-042507/

Part 2 http://www.softwaredeveloper.com/features/intro-to-ruby-on-rails-part-two-043007/

An excellent introduction to Rails for novices

'''''Installers'''
''

Windows: InstantRails - http://instantrails.rubyforge.org/wiki/wiki.pl

An all in one, single click installer for Windows that includes a Rails server.

Mac: Locomotive - http://locomotive.raaum.org/

'''''Rails Projects''''' - http://www.workingwithrails.com/

A Database of Rails projects, programmers and websites

'''''Rails plugins''''' - http://agilewebdevelopment.com/

A collection of Rails open source plugins, searchable by category or keyword.

'''''Sample Rails''''' - http://snippets.dzone.com/tag/rails

A collection of Rails code snippets.

'''''Agile Rails book''''' - http://www.amazon.com/gp/product/097669400X/002-0481267-8083260?v=glance&n=283155

An excellent resource for learning how to apply Agile programming concepts to Rails.

'''''Rails cheatsheet''''' - http://www.blainekendall.com/uploads/RubyOnRails-Cheatsheet-BlaineKendall.pdf

One user's list of best practices, gotchas and quirks of developing with Rails.

'''''Rails best practices''''' - http://www.therailsway.com/

An official best practices list for programming in Rails.

'''''Advanced Rails''''' - http://webonrails.com/

A resource for the advanced Rails programmer.

'''''Rails Blog''''' - http://weblog.rubyonrails.org/

An online community of updates about current happenings with the Rails platform.

'''''Rails Guides''''' - http://guides.rubyonrails.org/

An all in one resource for learning Rails including Howtos, security and contributing to the Rails community.

'''''Authoring Rails plugins''''' - http://nubyonrails.com/articles/2006/05/04/the-complete-guide-to-rails-plugins-part-i

A complete guide to authoring your own Rails plugins.

'''

== '''Tools for Rails (other than IDEs)''' ==
'''

'''Test Unit'''
The Rails stack uses Test::Unit, known as the default Ruby unit testing framework shipping with Ruby. There are various plugins and extension that could be used with Rails built-in Test::Unit to extend its functionality for support of TDD and BDD testing practices.

[http://wiki.rubyonrails.org/addons/testing]
The link provides additional information in the form of supporting resources, whitepapers, examples, and plug-in documentation

'''Example'''
[http://wiki.rubyonrails.org/testing/test-unitrequire]

Image:class CalculatorTest < Test::Unit::TestCase
def test_add_two_numbers_for_the_sum
calculator = Calculator.new
assert_equal 4, calculator.sum(2, 2)
end
end

== TDD: Test Driven Development ==

Test Driven Development is a combination of refactoring and test first development, a form of development where the test is

written prior to completed production code. The goal of TDD is the specification of requirements and not the validation of

requirements. There are a few testing frameworks that are used to implement the TDD programming technique.

[http://ruby.about.com/b/2009/01/28/test-driven-development-with-rails.htm]
This link provides a comprehensive overview of test driven development practices and available resources for implementation.

'''RSpec'''
RSpec is a testing framework for Behavior Driven Development, complete with its own expectations, matchers and mocking and

stubbing facilities. It goes along hand in hand with Cucumber, though it plays nicely with many other testing frameworks as well.

''Example''

The following code will fail during execution. ''Expresses some basic desired behavior''[http://rspec.info/]

<nowiki>#</nowiki> bowling_spec.rb
require ‘bowling’
describe Bowling do
it "should score 0 for gutter game" do
bowling = Bowling.new
20.times { bowling.hit(0) }
bowling.score.should == 0
end
end

The following code pass execution. ''Just enough code to make it pass.''[http://rspec.info/]

<nowiki>#</nowiki> bowling.rb
class Bowling
def hit(pins)
end
def score
0
end
end

[http://www.ibm.com/developerworks/web/library/wa-rspec/]
The link provides a brief overview of RSpec with a comprehensive series of examples and a conceptual view of Rpecs step by step

implementation process

'''Cucumber'''
Cucumber is used with TDD and BDD within other testing frameworks such as RSpec by letting software development teams describe how

software should behave in plain text. The text is written in a business-readable domain-specific language and serves as

documentation, automated tests and development-aid - all rolled into one format.

Feature: Log in and out
As an administrator
I want to restrict access to certain portions of my site
In order to prevent users from changing the content
Scenario: Logging in
Given I am not logged in as an administrator
When I go to the administrative page
And I fill in the fields
| Username | admin |
| Password | secret |
And I press "Log in"
Then I should be on the administrative page
And I should see "Log out"
Scenario: Logging out
...

[http://cukes.info/]
The link provides a detail decription, definition, and examples of Cucumber implementation best practices and supported

frameworks.

'''Cucumber Example:'''
Scenario: See all vendors
Given I am logged in as a user in the administrator role
And There are 3 vendors
When I go to the manage vendors page
Then I should see the first 3 vendor names

'''Shoulda'''
An extension to Test::Unit with additional helpers, macros, and assertions.

[http://www.thoughtbot.com/projects/shoulda]
The link provides a more conclusive definition of Shoulda along with installation facts and working examples of the Shoulda

testing framework within Ruby's built in Test::Unit

== BDD: Behavior Driven Development ==
[http://eggsonbread.com/2009/07/22/behavior-driven-development-in-a-nutshell/]
Behavior driven development was born from the concepts behind the implementation of TDD. It brings together strands from

TestDrivenDevelopment and DomainDrivenDesign into an integrated whole, making the relationship between these two powerful

approaches to software development more evident. Most test driven development testing frameworks such as RSpec and Cucumber also support behavior driven development testing.

[http://behaviour-driven.org/]
The link supports BDDs definition with additional links to more viable behavior driven development resources.

----

'''Other Test Tool Resources'''

''Watir:'' is an open-source library for automating web browsers. It allows you to write tests that are easy to read and maintain. It

is simple and flexible.
[http://wtr.rubyforge.org/]
The link provides an overview of Watir with installation specifications, examples, and supported platforms

''NullDB:'' [http://avdi.org/projects/nulldb/]
a way to speed up testing by avoiding database use.

''Bleakhouse:'' memory leak detection
[http://www.rubyinside.com/bleakhouse-tool-to-find-memory-leaks-in-your-rails-applications-470.html]
The link gives additional information on Bleakhouse profiling for memory leaks

''ruby-debug:''
Other than the extensive use of breakpoints Rails provides little to streamline the debugging process. Ruby-debug provides Rails with a plug-in extending the functionality of Rails built in debugger.

[http://rubyforge.org/softwaremap/trove_list.php?form_cat=47]
The link provides twenty additional debug resources available for RoR

== '''Conclusion''' ==

Rails is a very comprehensive development environment for Ruby with numerous extensions, plugins, and other resources outside of IDEs to strengthen the functionality of the open source web application framework.

== References ==

''All sources used to create this wiki are linked in the above text.''

CSC/ECE 517 Fall 2009/wiki1b team1

2009-09-28T20:06:16Z

Los Bravo: /* TDD: Test Driven Development */

CSC/ECE 517 Fall 2009

'''
== Resources for Rails (other than IDEs) ==
'''

IDEs are a valuable resource for Rails development, however there are many other resources and tools
that can either replace or supplement IDEs.

'''Resources for Rails other than IDEs
'''

'''''Rails API''''' - http://api.rubyonrails.org/

This site documents Rails files, classes and methods that can be used to build a Rails application.

'''''Rails Forum''''' - http://railsforum.com/

A discussion forum covering all aspects of Rails for beginners and experts including planning,
programming, extensions and production.

'''''Introducing Ruby on Rails'''''

Part 1 http://www.softwaredeveloper.com/features/intro-to-ruby-on-rails-042507/

Part 2 http://www.softwaredeveloper.com/features/intro-to-ruby-on-rails-part-two-043007/

An excellent introduction to Rails for novices

'''''Installers'''
''

Windows: InstantRails - http://instantrails.rubyforge.org/wiki/wiki.pl

An all in one, single click installer for Windows that includes a Rails server.

Mac: Locomotive - http://locomotive.raaum.org/

'''''Rails Projects''''' - http://www.workingwithrails.com/

A Database of Rails projects, programmers and websites

'''''Rails plugins''''' - http://agilewebdevelopment.com/

A collection of Rails open source plugins, searchable by category or keyword.

'''''Sample Rails''''' - http://snippets.dzone.com/tag/rails

A collection of Rails code snippets.

'''''Agile Rails book''''' - http://www.amazon.com/gp/product/097669400X/002-0481267-8083260?v=glance&n=283155

An excellent resource for learning how to apply Agile programming concepts to Rails.

'''''Rails cheatsheet''''' - http://www.blainekendall.com/uploads/RubyOnRails-Cheatsheet-BlaineKendall.pdf

One user's list of best practices, gotchas and quirks of developing with Rails.

'''''Rails best practices''''' - http://www.therailsway.com/

An official best practices list for programming in Rails.

'''''Advanced Rails''''' - http://webonrails.com/

A resource for the advanced Rails programmer.

'''''Rails Blog''''' - http://weblog.rubyonrails.org/

An online community of updates about current happenings with the Rails platform.

'''''Rails Guides''''' - http://guides.rubyonrails.org/

An all in one resource for learning Rails including Howtos, security and contributing to the Rails community.

'''''Authoring Rails plugins''''' - http://nubyonrails.com/articles/2006/05/04/the-complete-guide-to-rails-plugins-part-i

A complete guide to authoring your own Rails plugins.

'''

== '''Tools for Rails (other than IDEs)''' ==
'''

'''Test Unit'''
The Rails stack uses Test::Unit, known as the default Ruby unit testing framework shipping with Ruby. There are various plugins and extension that could be used with Rails built-in Test::Unit to extend its functionality for support of TDD and BDD testing practices.

[http://wiki.rubyonrails.org/addons/testing]
The link provides additional information in the form of supporting resources, whitepapers, examples, and plug-in documentation

'''Example'''
[http://wiki.rubyonrails.org/testing/test-unitrequire]

Image:class CalculatorTest < Test::Unit::TestCase
def test_add_two_numbers_for_the_sum
calculator = Calculator.new
assert_equal 4, calculator.sum(2, 2)
end
end

== TDD: Test Driven Development ==

Test Driven Development is a combination of refactoring and test first development, a form of development where the test is

written prior to completed production code. The goal of TDD is the specification of requirements and not the validation of

requirements. There are a few testing frameworks that are used to implement the TDD programming technique.

[http://ruby.about.com/b/2009/01/28/test-driven-development-with-rails.htm]
This link provides a comprehensive overview of test driven development practices and available resources for implementation.

'''RSpec'''
RSpec is a testing framework for Behavior Driven Development, complete with its own expectations, matchers and mocking and

stubbing facilities. It goes along hand in hand with Cucumber, though it plays nicely with many other testing frameworks as well.

''Example''

The following code will fail during execution. ''Expresses some basic desired behavior''[http://rspec.info/]

<nowiki>#</nowiki> bowling_spec.rb
require ‘bowling’
describe Bowling do
it "should score 0 for gutter game" do
bowling = Bowling.new
20.times { bowling.hit(0) }
bowling.score.should == 0
end
end

The following code pass execution. ''Just enough code to make it pass.''[http://rspec.info/]

<nowiki>#</nowiki> bowling.rb
class Bowling
def hit(pins)
end
def score
0
end
end

[http://www.ibm.com/developerworks/web/library/wa-rspec/]
The link provides a brief overview of RSpec with a comprehensive series of examples and a conceptual view of Rpecs step by step

implementation process

'''Cucumber'''
Cucumber is used with TDD and BDD within other testing frameworks such as RSpec by letting software development teams describe how

software should behave in plain text. The text is written in a business-readable domain-specific language and serves as

documentation, automated tests and development-aid - all rolled into one format.

Feature: Log in and out
As an administrator
I want to restrict access to certain portions of my site
In order to prevent users from changing the content

Scenario: Logging in
Given I am not logged in as an administrator
When I go to the administrative page
And I fill in the fields
| Username | admin |
| Password | secret |
And I press "Log in"
Then I should be on the administrative page
And I should see "Log out"

Scenario: Logging out
...

[http://cukes.info/]
The link provides a detail decription, definition, and examples of Cucumber implementation best practices and supported

frameworks.

'''Cucumber Example:'''
Scenario: See all vendors
Given I am logged in as a user in the administrator role
And There are 3 vendors
When I go to the manage vendors page
Then I should see the first 3 vendor names

'''Shoulda'''
An extension to Test::Unit with additional helpers, macros, and assertions.

[http://www.thoughtbot.com/projects/shoulda]
The link provides a more conclusive definition of Shoulda along with installation facts and working examples of the Shoulda

testing framework within Ruby's built in Test::Unit

== BDD: Behavior Driven Development ==
[http://eggsonbread.com/2009/07/22/behavior-driven-development-in-a-nutshell/]
Behavior driven development was born from the concepts behind the implementation of TDD. It brings together strands from

TestDrivenDevelopment and DomainDrivenDesign into an integrated whole, making the relationship between these two powerful

approaches to software development more evident. Most test driven development testing frameworks such as RSpec and Cucumber also support behavior driven development testing.

[http://behaviour-driven.org/]
The link supports BDDs definition with additional links to more viable behavior driven development resources.

----

'''Other Test Tool Resources'''

''Watir:'' is an open-source library for automating web browsers. It allows you to write tests that are easy to read and maintain. It

is simple and flexible.
[http://wtr.rubyforge.org/]
The link provides an overview of Watir with installation specifications, examples, and supported platforms

''NullDB:'' [http://avdi.org/projects/nulldb/]
a way to speed up testing by avoiding database use.

''Bleakhouse:'' memory leak detection
[http://www.rubyinside.com/bleakhouse-tool-to-find-memory-leaks-in-your-rails-applications-470.html]
The link gives additional information on Bleakhouse profiling for memory leaks

''ruby-debug:''
Other than the extensive use of breakpoints Rails provides little to streamline the debugging process. Ruby-debug provides Rails with a plug-in extending the functionality of Rails built in debugger.

[http://rubyforge.org/softwaremap/trove_list.php?form_cat=47]
The link provides twenty additional debug resources available for RoR

== '''Conclusion''' ==

Rails is a very comprehensive development environment for Ruby with numerous extensions, plugins, and other resources outside of IDEs to strengthen the functionality of the open source web application framework.

== References ==

''All sources used to create this wiki are linked in the above text.''

CSC/ECE 517 Fall 2009/wiki1b team1

2009-09-28T20:02:41Z

Los Bravo: /* TDD: Test Driven Development */

CSC/ECE 517 Fall 2009

'''
== Resources for Rails (other than IDEs) ==
'''

IDEs are a valuable resource for Rails development, however there are many other resources and tools
that can either replace or supplement IDEs.

'''Resources for Rails other than IDEs
'''

'''''Rails API''''' - http://api.rubyonrails.org/

This site documents Rails files, classes and methods that can be used to build a Rails application.

'''''Rails Forum''''' - http://railsforum.com/

A discussion forum covering all aspects of Rails for beginners and experts including planning,
programming, extensions and production.

'''''Introducing Ruby on Rails'''''

Part 1 http://www.softwaredeveloper.com/features/intro-to-ruby-on-rails-042507/

Part 2 http://www.softwaredeveloper.com/features/intro-to-ruby-on-rails-part-two-043007/

An excellent introduction to Rails for novices

'''''Installers'''
''

Windows: InstantRails - http://instantrails.rubyforge.org/wiki/wiki.pl

An all in one, single click installer for Windows that includes a Rails server.

Mac: Locomotive - http://locomotive.raaum.org/

'''''Rails Projects''''' - http://www.workingwithrails.com/

A Database of Rails projects, programmers and websites

'''''Rails plugins''''' - http://agilewebdevelopment.com/

A collection of Rails open source plugins, searchable by category or keyword.

'''''Sample Rails''''' - http://snippets.dzone.com/tag/rails

A collection of Rails code snippets.

'''''Agile Rails book''''' - http://www.amazon.com/gp/product/097669400X/002-0481267-8083260?v=glance&n=283155

An excellent resource for learning how to apply Agile programming concepts to Rails.

'''''Rails cheatsheet''''' - http://www.blainekendall.com/uploads/RubyOnRails-Cheatsheet-BlaineKendall.pdf

One user's list of best practices, gotchas and quirks of developing with Rails.

'''''Rails best practices''''' - http://www.therailsway.com/

An official best practices list for programming in Rails.

'''''Advanced Rails''''' - http://webonrails.com/

A resource for the advanced Rails programmer.

'''''Rails Blog''''' - http://weblog.rubyonrails.org/

An online community of updates about current happenings with the Rails platform.

'''''Rails Guides''''' - http://guides.rubyonrails.org/

An all in one resource for learning Rails including Howtos, security and contributing to the Rails community.

'''''Authoring Rails plugins''''' - http://nubyonrails.com/articles/2006/05/04/the-complete-guide-to-rails-plugins-part-i

A complete guide to authoring your own Rails plugins.

'''

== '''Tools for Rails (other than IDEs)''' ==
'''

'''Test Unit'''
The Rails stack uses Test::Unit, known as the default Ruby unit testing framework shipping with Ruby. There are various plugins and extension that could be used with Rails built-in Test::Unit to extend its functionality for support of TDD and BDD testing practices.

[http://wiki.rubyonrails.org/addons/testing]
The link provides additional information in the form of supporting resources, whitepapers, examples, and plug-in documentation

'''Example'''
[http://wiki.rubyonrails.org/testing/test-unitrequire]

Image:class CalculatorTest < Test::Unit::TestCase
def test_add_two_numbers_for_the_sum
calculator = Calculator.new
assert_equal 4, calculator.sum(2, 2)
end
end

== TDD: Test Driven Development ==

Test Driven Development is a combination of refactoring and test first development, a form of development where the test is

written prior to completed production code. The goal of TDD is the specification of requirements and not the validation of

requirements. There are a few testing frameworks that are used to implement the TDD programming technique.

[http://ruby.about.com/b/2009/01/28/test-driven-development-with-rails.htm]
This link provides a comprehensive overview of test driven development practices and available resources for implementation.

'''RSpec'''
RSpec is a testing framework for Behavior Driven Development, complete with its own expectations, matchers and mocking and

stubbing facilities. It goes along hand in hand with Cucumber, though it plays nicely with many other testing frameworks as well.

''Example''

The following code will fail during execution. ''Expresses some basic desired behavior''[http://rspec.info/]

<nowiki>#</nowiki> bowling_spec.rb
require ‘bowling’
describe Bowling do
it "should score 0 for gutter game" do
bowling = Bowling.new
20.times { bowling.hit(0) }
bowling.score.should == 0
end
end

The following code pass execution. ''Just enough code to make it pass.''[http://rspec.info/]

<nowiki>#</nowiki> bowling.rb
class Bowling
def hit(pins)
end
def score
0
end
end

'''Model Examples'''
These are the equivalent of unit tests in Rails’ built in testing. Ironically
(for the traditional TDD’er) these are the only specs that we feel should actually interact
with the database.

'''Controller Examples'''
These align somewhat with functional tests in rails, except
that they do not actually render views (though you can force rendering of views
if you prefer). Instead of setting expectations about what goes on a page, you
set expectations about what templates get rendered.

'''View Examples'''
This is the other half of Rails’ functional testing. View specs allow
you to set up assigns (thanks to ZenTest).

'''Helper Examples'''
let you specify directly methods that live in your helpers.

[http://www.ibm.com/developerworks/web/library/wa-rspec/]
The link provides a brief overview of RSpec with a comprehensive series of examples and a conceptual view of Rpecs step by step

implementation process

'''Cucumber'''
Cucumber is used with TDD and BDD within other testing frameworks such as RSpec by letting software development teams describe how

software should behave in plain text. The text is written in a business-readable domain-specific language and serves as

documentation, automated tests and development-aid - all rolled into one format.

[http://cukes.info/]
The link provides a detail decription, definition, and examples of Cucumber implementation best practices and supported

frameworks.

'''Cucumber Example:'''
Scenario: See all vendors
Given I am logged in as a user in the administrator role
And There are 3 vendors
When I go to the manage vendors page
Then I should see the first 3 vendor names

'''Shoulda'''
An extension to Test::Unit with additional helpers, macros, and assertions.

[http://www.thoughtbot.com/projects/shoulda]
The link provides a more conclusive definition of Shoulda along with installation facts and working examples of the Shoulda

testing framework within Ruby's built in Test::Unit

== BDD: Behavior Driven Development ==
[http://eggsonbread.com/2009/07/22/behavior-driven-development-in-a-nutshell/]
Behavior driven development was born from the concepts behind the implementation of TDD. It brings together strands from

TestDrivenDevelopment and DomainDrivenDesign into an integrated whole, making the relationship between these two powerful

approaches to software development more evident. Most test driven development testing frameworks such as RSpec and Cucumber also support behavior driven development testing.

[http://behaviour-driven.org/]
The link supports BDDs definition with additional links to more viable behavior driven development resources.

----

'''Other Test Tool Resources'''

''Watir:'' is an open-source library for automating web browsers. It allows you to write tests that are easy to read and maintain. It

is simple and flexible.
[http://wtr.rubyforge.org/]
The link provides an overview of Watir with installation specifications, examples, and supported platforms

''NullDB:'' [http://avdi.org/projects/nulldb/]
a way to speed up testing by avoiding database use.

''Bleakhouse:'' memory leak detection
[http://www.rubyinside.com/bleakhouse-tool-to-find-memory-leaks-in-your-rails-applications-470.html]
The link gives additional information on Bleakhouse profiling for memory leaks

''ruby-debug:''
Other than the extensive use of breakpoints Rails provides little to streamline the debugging process. Ruby-debug provides Rails with a plug-in extending the functionality of Rails built in debugger.

[http://rubyforge.org/softwaremap/trove_list.php?form_cat=47]
The link provides twenty additional debug resources available for RoR

== '''Conclusion''' ==

Rails is a very comprehensive development environment for Ruby with numerous extensions, plugins, and other resources outside of IDEs to strengthen the functionality of the open source web application framework.

== References ==

''All sources used to create this wiki are linked in the above text.''

CSC/ECE 517 Fall 2009/wiki1b team1

2009-09-28T20:02:11Z

Los Bravo: /* TDD: Test Driven Development */

CSC/ECE 517 Fall 2009

'''
== Resources for Rails (other than IDEs) ==
'''

IDEs are a valuable resource for Rails development, however there are many other resources and tools
that can either replace or supplement IDEs.

'''Resources for Rails other than IDEs
'''

'''''Rails API''''' - http://api.rubyonrails.org/

This site documents Rails files, classes and methods that can be used to build a Rails application.

'''''Rails Forum''''' - http://railsforum.com/

A discussion forum covering all aspects of Rails for beginners and experts including planning,
programming, extensions and production.

'''''Introducing Ruby on Rails'''''

Part 1 http://www.softwaredeveloper.com/features/intro-to-ruby-on-rails-042507/

Part 2 http://www.softwaredeveloper.com/features/intro-to-ruby-on-rails-part-two-043007/

An excellent introduction to Rails for novices

'''''Installers'''
''

Windows: InstantRails - http://instantrails.rubyforge.org/wiki/wiki.pl

An all in one, single click installer for Windows that includes a Rails server.

Mac: Locomotive - http://locomotive.raaum.org/

'''''Rails Projects''''' - http://www.workingwithrails.com/

A Database of Rails projects, programmers and websites

'''''Rails plugins''''' - http://agilewebdevelopment.com/

A collection of Rails open source plugins, searchable by category or keyword.

'''''Sample Rails''''' - http://snippets.dzone.com/tag/rails

A collection of Rails code snippets.

'''''Agile Rails book''''' - http://www.amazon.com/gp/product/097669400X/002-0481267-8083260?v=glance&n=283155

An excellent resource for learning how to apply Agile programming concepts to Rails.

'''''Rails cheatsheet''''' - http://www.blainekendall.com/uploads/RubyOnRails-Cheatsheet-BlaineKendall.pdf

One user's list of best practices, gotchas and quirks of developing with Rails.

'''''Rails best practices''''' - http://www.therailsway.com/

An official best practices list for programming in Rails.

'''''Advanced Rails''''' - http://webonrails.com/

A resource for the advanced Rails programmer.

'''''Rails Blog''''' - http://weblog.rubyonrails.org/

An online community of updates about current happenings with the Rails platform.

'''''Rails Guides''''' - http://guides.rubyonrails.org/

An all in one resource for learning Rails including Howtos, security and contributing to the Rails community.

'''''Authoring Rails plugins''''' - http://nubyonrails.com/articles/2006/05/04/the-complete-guide-to-rails-plugins-part-i

A complete guide to authoring your own Rails plugins.

'''

== '''Tools for Rails (other than IDEs)''' ==
'''

'''Test Unit'''
The Rails stack uses Test::Unit, known as the default Ruby unit testing framework shipping with Ruby. There are various plugins and extension that could be used with Rails built-in Test::Unit to extend its functionality for support of TDD and BDD testing practices.

[http://wiki.rubyonrails.org/addons/testing]
The link provides additional information in the form of supporting resources, whitepapers, examples, and plug-in documentation

'''Example'''
[http://wiki.rubyonrails.org/testing/test-unitrequire]

Image:class CalculatorTest < Test::Unit::TestCase
def test_add_two_numbers_for_the_sum
calculator = Calculator.new
assert_equal 4, calculator.sum(2, 2)
end
end

== TDD: Test Driven Development ==

Test Driven Development is a combination of refactoring and test first development, a form of development where the test is

written prior to completed production code. The goal of TDD is the specification of requirements and not the validation of

requirements. There are a few testing frameworks that are used to implement the TDD programming technique.

[http://ruby.about.com/b/2009/01/28/test-driven-development-with-rails.htm]
This link provides a comprehensive overview of test driven development practices and available resources for implementation.

'''RSpec'''
RSpec is a testing framework for Behavior Driven Development, complete with its own expectations, matchers and mocking and

stubbing facilities. It goes along hand in hand with Cucumber, though it plays nicely with many other testing frameworks as well.

''Example''[http://rspec.info/]

The following code will fail during execution. ''Expresses some basic desired behavior''[http://rspec.info/]

<nowiki>#</nowiki> bowling_spec.rb
require ‘bowling’
describe Bowling do
it "should score 0 for gutter game" do
bowling = Bowling.new
20.times { bowling.hit(0) }
bowling.score.should == 0
end
end

The following code pass execution. ''Just enough code to make it pass.''

<nowiki>#</nowiki> bowling.rb
class Bowling
def hit(pins)
end
def score
0
end
end

'''Model Examples'''
These are the equivalent of unit tests in Rails’ built in testing. Ironically
(for the traditional TDD’er) these are the only specs that we feel should actually interact
with the database.

'''Controller Examples'''
These align somewhat with functional tests in rails, except
that they do not actually render views (though you can force rendering of views
if you prefer). Instead of setting expectations about what goes on a page, you
set expectations about what templates get rendered.

'''View Examples'''
This is the other half of Rails’ functional testing. View specs allow
you to set up assigns (thanks to ZenTest).

'''Helper Examples'''
let you specify directly methods that live in your helpers.

[http://www.ibm.com/developerworks/web/library/wa-rspec/]
The link provides a brief overview of RSpec with a comprehensive series of examples and a conceptual view of Rpecs step by step

implementation process

'''Cucumber'''
Cucumber is used with TDD and BDD within other testing frameworks such as RSpec by letting software development teams describe how

software should behave in plain text. The text is written in a business-readable domain-specific language and serves as

documentation, automated tests and development-aid - all rolled into one format.

[http://cukes.info/]
The link provides a detail decription, definition, and examples of Cucumber implementation best practices and supported

frameworks.

'''Cucumber Example:'''
Scenario: See all vendors
Given I am logged in as a user in the administrator role
And There are 3 vendors
When I go to the manage vendors page
Then I should see the first 3 vendor names

'''Shoulda'''
An extension to Test::Unit with additional helpers, macros, and assertions.

[http://www.thoughtbot.com/projects/shoulda]
The link provides a more conclusive definition of Shoulda along with installation facts and working examples of the Shoulda

testing framework within Ruby's built in Test::Unit

== BDD: Behavior Driven Development ==
[http://eggsonbread.com/2009/07/22/behavior-driven-development-in-a-nutshell/]
Behavior driven development was born from the concepts behind the implementation of TDD. It brings together strands from

TestDrivenDevelopment and DomainDrivenDesign into an integrated whole, making the relationship between these two powerful

approaches to software development more evident. Most test driven development testing frameworks such as RSpec and Cucumber also support behavior driven development testing.

[http://behaviour-driven.org/]
The link supports BDDs definition with additional links to more viable behavior driven development resources.

----

'''Other Test Tool Resources'''

''Watir:'' is an open-source library for automating web browsers. It allows you to write tests that are easy to read and maintain. It

is simple and flexible.
[http://wtr.rubyforge.org/]
The link provides an overview of Watir with installation specifications, examples, and supported platforms

''NullDB:'' [http://avdi.org/projects/nulldb/]
a way to speed up testing by avoiding database use.

''Bleakhouse:'' memory leak detection
[http://www.rubyinside.com/bleakhouse-tool-to-find-memory-leaks-in-your-rails-applications-470.html]
The link gives additional information on Bleakhouse profiling for memory leaks

''ruby-debug:''
Other than the extensive use of breakpoints Rails provides little to streamline the debugging process. Ruby-debug provides Rails with a plug-in extending the functionality of Rails built in debugger.

[http://rubyforge.org/softwaremap/trove_list.php?form_cat=47]
The link provides twenty additional debug resources available for RoR

== '''Conclusion''' ==

Rails is a very comprehensive development environment for Ruby with numerous extensions, plugins, and other resources outside of IDEs to strengthen the functionality of the open source web application framework.

== References ==

''All sources used to create this wiki are linked in the above text.''

CSC/ECE 517 Fall 2009/wiki1b team1

2009-09-28T20:00:49Z

Los Bravo: /* TDD: Test Driven Development */

CSC/ECE 517 Fall 2009

'''
== Resources for Rails (other than IDEs) ==
'''

IDEs are a valuable resource for Rails development, however there are many other resources and tools
that can either replace or supplement IDEs.

'''Resources for Rails other than IDEs
'''

'''''Rails API''''' - http://api.rubyonrails.org/

This site documents Rails files, classes and methods that can be used to build a Rails application.

'''''Rails Forum''''' - http://railsforum.com/

A discussion forum covering all aspects of Rails for beginners and experts including planning,
programming, extensions and production.

'''''Introducing Ruby on Rails'''''

Part 1 http://www.softwaredeveloper.com/features/intro-to-ruby-on-rails-042507/

Part 2 http://www.softwaredeveloper.com/features/intro-to-ruby-on-rails-part-two-043007/

An excellent introduction to Rails for novices

'''''Installers'''
''

Windows: InstantRails - http://instantrails.rubyforge.org/wiki/wiki.pl

An all in one, single click installer for Windows that includes a Rails server.

Mac: Locomotive - http://locomotive.raaum.org/

'''''Rails Projects''''' - http://www.workingwithrails.com/

A Database of Rails projects, programmers and websites

'''''Rails plugins''''' - http://agilewebdevelopment.com/

A collection of Rails open source plugins, searchable by category or keyword.

'''''Sample Rails''''' - http://snippets.dzone.com/tag/rails

A collection of Rails code snippets.

'''''Agile Rails book''''' - http://www.amazon.com/gp/product/097669400X/002-0481267-8083260?v=glance&n=283155

An excellent resource for learning how to apply Agile programming concepts to Rails.

'''''Rails cheatsheet''''' - http://www.blainekendall.com/uploads/RubyOnRails-Cheatsheet-BlaineKendall.pdf

One user's list of best practices, gotchas and quirks of developing with Rails.

'''''Rails best practices''''' - http://www.therailsway.com/

An official best practices list for programming in Rails.

'''''Advanced Rails''''' - http://webonrails.com/

A resource for the advanced Rails programmer.

'''''Rails Blog''''' - http://weblog.rubyonrails.org/

An online community of updates about current happenings with the Rails platform.

'''''Rails Guides''''' - http://guides.rubyonrails.org/

An all in one resource for learning Rails including Howtos, security and contributing to the Rails community.

'''''Authoring Rails plugins''''' - http://nubyonrails.com/articles/2006/05/04/the-complete-guide-to-rails-plugins-part-i

A complete guide to authoring your own Rails plugins.

'''

== '''Tools for Rails (other than IDEs)''' ==
'''

'''Test Unit'''
The Rails stack uses Test::Unit, known as the default Ruby unit testing framework shipping with Ruby. There are various plugins and extension that could be used with Rails built-in Test::Unit to extend its functionality for support of TDD and BDD testing practices.

[http://wiki.rubyonrails.org/addons/testing]
The link provides additional information in the form of supporting resources, whitepapers, examples, and plug-in documentation

'''Example'''
[http://wiki.rubyonrails.org/testing/test-unitrequire]

Image:class CalculatorTest < Test::Unit::TestCase
def test_add_two_numbers_for_the_sum
calculator = Calculator.new
assert_equal 4, calculator.sum(2, 2)
end
end

== TDD: Test Driven Development ==

Test Driven Development is a combination of refactoring and test first development, a form of development where the test is

written prior to completed production code. The goal of TDD is the specification of requirements and not the validation of

requirements. There are a few testing frameworks that are used to implement the TDD programming technique.

[http://ruby.about.com/b/2009/01/28/test-driven-development-with-rails.htm]
This link provides a comprehensive overview of test driven development practices and available resources for implementation.

'''RSpec'''
RSpec is a testing framework for Behavior Driven Development, complete with its own expectations, matchers and mocking and

stubbing facilities. It goes along hand in hand with Cucumber, though it plays nicely with many other testing frameworks as well.

''Example expresses some basic desired behavior''[http://rspec.info/]

The following code will fail during execution.

<nowiki>#</nowiki> bowling_spec.rb
require ‘bowling’
describe Bowling do
it "should score 0 for gutter game" do
bowling = Bowling.new
20.times { bowling.hit(0) }
bowling.score.should == 0
end
end

''Just enough code to make it pass.''

The following code pass execution.

<nowiki>#</nowiki> bowling.rb
class Bowling
def hit(pins)
end
def score
0
end
end

'''Model Examples'''
These are the equivalent of unit tests in Rails’ built in testing. Ironically
(for the traditional TDD’er) these are the only specs that we feel should actually interact
with the database.

'''Controller Examples'''
These align somewhat with functional tests in rails, except
that they do not actually render views (though you can force rendering of views
if you prefer). Instead of setting expectations about what goes on a page, you
set expectations about what templates get rendered.

'''View Examples'''
This is the other half of Rails’ functional testing. View specs allow
you to set up assigns (thanks to ZenTest).

'''Helper Examples'''
let you specify directly methods that live in your helpers.

[http://www.ibm.com/developerworks/web/library/wa-rspec/]
The link provides a brief overview of RSpec with a comprehensive series of examples and a conceptual view of Rpecs step by step

implementation process

'''Cucumber'''
Cucumber is used with TDD and BDD within other testing frameworks such as RSpec by letting software development teams describe how

software should behave in plain text. The text is written in a business-readable domain-specific language and serves as

documentation, automated tests and development-aid - all rolled into one format.

[http://cukes.info/]
The link provides a detail decription, definition, and examples of Cucumber implementation best practices and supported

frameworks.

'''Cucumber Example:'''
Scenario: See all vendors
Given I am logged in as a user in the administrator role
And There are 3 vendors
When I go to the manage vendors page
Then I should see the first 3 vendor names

'''Shoulda'''
An extension to Test::Unit with additional helpers, macros, and assertions.

[http://www.thoughtbot.com/projects/shoulda]
The link provides a more conclusive definition of Shoulda along with installation facts and working examples of the Shoulda

testing framework within Ruby's built in Test::Unit

== BDD: Behavior Driven Development ==
[http://eggsonbread.com/2009/07/22/behavior-driven-development-in-a-nutshell/]
Behavior driven development was born from the concepts behind the implementation of TDD. It brings together strands from

TestDrivenDevelopment and DomainDrivenDesign into an integrated whole, making the relationship between these two powerful

approaches to software development more evident. Most test driven development testing frameworks such as RSpec and Cucumber also support behavior driven development testing.

[http://behaviour-driven.org/]
The link supports BDDs definition with additional links to more viable behavior driven development resources.

----

'''Other Test Tool Resources'''

''Watir:'' is an open-source library for automating web browsers. It allows you to write tests that are easy to read and maintain. It

is simple and flexible.
[http://wtr.rubyforge.org/]
The link provides an overview of Watir with installation specifications, examples, and supported platforms

''NullDB:'' [http://avdi.org/projects/nulldb/]
a way to speed up testing by avoiding database use.

''Bleakhouse:'' memory leak detection
[http://www.rubyinside.com/bleakhouse-tool-to-find-memory-leaks-in-your-rails-applications-470.html]
The link gives additional information on Bleakhouse profiling for memory leaks

''ruby-debug:''
Other than the extensive use of breakpoints Rails provides little to streamline the debugging process. Ruby-debug provides Rails with a plug-in extending the functionality of Rails built in debugger.

[http://rubyforge.org/softwaremap/trove_list.php?form_cat=47]
The link provides twenty additional debug resources available for RoR

== '''Conclusion''' ==

Rails is a very comprehensive development environment for Ruby with numerous extensions, plugins, and other resources outside of IDEs to strengthen the functionality of the open source web application framework.

== References ==

''All sources used to create this wiki are linked in the above text.''

CSC/ECE 517 Fall 2009/wiki1b team1

2009-09-28T20:00:18Z

Los Bravo: /* TDD: Test Driven Development */

CSC/ECE 517 Fall 2009

'''
== Resources for Rails (other than IDEs) ==
'''

IDEs are a valuable resource for Rails development, however there are many other resources and tools
that can either replace or supplement IDEs.

'''Resources for Rails other than IDEs
'''

'''''Rails API''''' - http://api.rubyonrails.org/

This site documents Rails files, classes and methods that can be used to build a Rails application.

'''''Rails Forum''''' - http://railsforum.com/

A discussion forum covering all aspects of Rails for beginners and experts including planning,
programming, extensions and production.

'''''Introducing Ruby on Rails'''''

Part 1 http://www.softwaredeveloper.com/features/intro-to-ruby-on-rails-042507/

Part 2 http://www.softwaredeveloper.com/features/intro-to-ruby-on-rails-part-two-043007/

An excellent introduction to Rails for novices

'''''Installers'''
''

Windows: InstantRails - http://instantrails.rubyforge.org/wiki/wiki.pl

An all in one, single click installer for Windows that includes a Rails server.

Mac: Locomotive - http://locomotive.raaum.org/

'''''Rails Projects''''' - http://www.workingwithrails.com/

A Database of Rails projects, programmers and websites

'''''Rails plugins''''' - http://agilewebdevelopment.com/

A collection of Rails open source plugins, searchable by category or keyword.

'''''Sample Rails''''' - http://snippets.dzone.com/tag/rails

A collection of Rails code snippets.

'''''Agile Rails book''''' - http://www.amazon.com/gp/product/097669400X/002-0481267-8083260?v=glance&n=283155

An excellent resource for learning how to apply Agile programming concepts to Rails.

'''''Rails cheatsheet''''' - http://www.blainekendall.com/uploads/RubyOnRails-Cheatsheet-BlaineKendall.pdf

One user's list of best practices, gotchas and quirks of developing with Rails.

'''''Rails best practices''''' - http://www.therailsway.com/

An official best practices list for programming in Rails.

'''''Advanced Rails''''' - http://webonrails.com/

A resource for the advanced Rails programmer.

'''''Rails Blog''''' - http://weblog.rubyonrails.org/

An online community of updates about current happenings with the Rails platform.

'''''Rails Guides''''' - http://guides.rubyonrails.org/

An all in one resource for learning Rails including Howtos, security and contributing to the Rails community.

'''''Authoring Rails plugins''''' - http://nubyonrails.com/articles/2006/05/04/the-complete-guide-to-rails-plugins-part-i

A complete guide to authoring your own Rails plugins.

'''

== '''Tools for Rails (other than IDEs)''' ==
'''

'''Test Unit'''
The Rails stack uses Test::Unit, known as the default Ruby unit testing framework shipping with Ruby. There are various plugins and extension that could be used with Rails built-in Test::Unit to extend its functionality for support of TDD and BDD testing practices.

[http://wiki.rubyonrails.org/addons/testing]
The link provides additional information in the form of supporting resources, whitepapers, examples, and plug-in documentation

'''Example'''
[http://wiki.rubyonrails.org/testing/test-unitrequire]

Image:class CalculatorTest < Test::Unit::TestCase
def test_add_two_numbers_for_the_sum
calculator = Calculator.new
assert_equal 4, calculator.sum(2, 2)
end
end

== TDD: Test Driven Development ==

Test Driven Development is a combination of refactoring and test first development, a form of development where the test is

written prior to completed production code. The goal of TDD is the specification of requirements and not the validation of

requirements. There are a few testing frameworks that are used to implement the TDD programming technique.

[http://ruby.about.com/b/2009/01/28/test-driven-development-with-rails.htm]
This link provides a comprehensive overview of test driven development practices and available resources for implementation.

'''RSpec'''
RSpec is a testing framework for Behavior Driven Development, complete with its own expectations, matchers and mocking and

stubbing facilities. It goes along hand in hand with Cucumber, though it plays nicely with many other testing frameworks as well.

''Example expresses some basic desired behavior''[http://rspec.info/]
The following code will fail during execution.

<nowiki>#</nowiki> bowling_spec.rb
require ‘bowling’
describe Bowling do
it "should score 0 for gutter game" do
bowling = Bowling.new
20.times { bowling.hit(0) }
bowling.score.should == 0
end
end

''Just enough code to make it pass.''
The following code pass execution.

<nowiki>#</nowiki> bowling.rb
class Bowling
def hit(pins)
end
def score
0
end
end

'''Model Examples'''
These are the equivalent of unit tests in Rails’ built in testing. Ironically
(for the traditional TDD’er) these are the only specs that we feel should actually interact
with the database.

'''Controller Examples'''
These align somewhat with functional tests in rails, except
that they do not actually render views (though you can force rendering of views
if you prefer). Instead of setting expectations about what goes on a page, you
set expectations about what templates get rendered.

'''View Examples'''
This is the other half of Rails’ functional testing. View specs allow
you to set up assigns (thanks to ZenTest).

'''Helper Examples'''
let you specify directly methods that live in your helpers.

[http://www.ibm.com/developerworks/web/library/wa-rspec/]
The link provides a brief overview of RSpec with a comprehensive series of examples and a conceptual view of Rpecs step by step

implementation process

'''Cucumber'''
Cucumber is used with TDD and BDD within other testing frameworks such as RSpec by letting software development teams describe how

software should behave in plain text. The text is written in a business-readable domain-specific language and serves as

documentation, automated tests and development-aid - all rolled into one format.

[http://cukes.info/]
The link provides a detail decription, definition, and examples of Cucumber implementation best practices and supported

frameworks.

'''Cucumber Example:'''
Scenario: See all vendors
Given I am logged in as a user in the administrator role
And There are 3 vendors
When I go to the manage vendors page
Then I should see the first 3 vendor names

'''Shoulda'''
An extension to Test::Unit with additional helpers, macros, and assertions.

[http://www.thoughtbot.com/projects/shoulda]
The link provides a more conclusive definition of Shoulda along with installation facts and working examples of the Shoulda

testing framework within Ruby's built in Test::Unit

== BDD: Behavior Driven Development ==
[http://eggsonbread.com/2009/07/22/behavior-driven-development-in-a-nutshell/]
Behavior driven development was born from the concepts behind the implementation of TDD. It brings together strands from

TestDrivenDevelopment and DomainDrivenDesign into an integrated whole, making the relationship between these two powerful

approaches to software development more evident. Most test driven development testing frameworks such as RSpec and Cucumber also support behavior driven development testing.

[http://behaviour-driven.org/]
The link supports BDDs definition with additional links to more viable behavior driven development resources.

----

'''Other Test Tool Resources'''

''Watir:'' is an open-source library for automating web browsers. It allows you to write tests that are easy to read and maintain. It

is simple and flexible.
[http://wtr.rubyforge.org/]
The link provides an overview of Watir with installation specifications, examples, and supported platforms

''NullDB:'' [http://avdi.org/projects/nulldb/]
a way to speed up testing by avoiding database use.

''Bleakhouse:'' memory leak detection
[http://www.rubyinside.com/bleakhouse-tool-to-find-memory-leaks-in-your-rails-applications-470.html]
The link gives additional information on Bleakhouse profiling for memory leaks

''ruby-debug:''
Other than the extensive use of breakpoints Rails provides little to streamline the debugging process. Ruby-debug provides Rails with a plug-in extending the functionality of Rails built in debugger.

[http://rubyforge.org/softwaremap/trove_list.php?form_cat=47]
The link provides twenty additional debug resources available for RoR

== '''Conclusion''' ==

Rails is a very comprehensive development environment for Ruby with numerous extensions, plugins, and other resources outside of IDEs to strengthen the functionality of the open source web application framework.

== References ==

''All sources used to create this wiki are linked in the above text.''

CSC/ECE 517 Fall 2009/wiki1b team1

2009-09-28T19:57:24Z

Los Bravo: /* TDD: Test Driven Development */

CSC/ECE 517 Fall 2009

'''
== Resources for Rails (other than IDEs) ==
'''

IDEs are a valuable resource for Rails development, however there are many other resources and tools
that can either replace or supplement IDEs.

'''Resources for Rails other than IDEs
'''

'''''Rails API''''' - http://api.rubyonrails.org/

This site documents Rails files, classes and methods that can be used to build a Rails application.

'''''Rails Forum''''' - http://railsforum.com/

A discussion forum covering all aspects of Rails for beginners and experts including planning,
programming, extensions and production.

'''''Introducing Ruby on Rails'''''

Part 1 http://www.softwaredeveloper.com/features/intro-to-ruby-on-rails-042507/

Part 2 http://www.softwaredeveloper.com/features/intro-to-ruby-on-rails-part-two-043007/

An excellent introduction to Rails for novices

'''''Installers'''
''

Windows: InstantRails - http://instantrails.rubyforge.org/wiki/wiki.pl

An all in one, single click installer for Windows that includes a Rails server.

Mac: Locomotive - http://locomotive.raaum.org/

'''''Rails Projects''''' - http://www.workingwithrails.com/

A Database of Rails projects, programmers and websites

'''''Rails plugins''''' - http://agilewebdevelopment.com/

A collection of Rails open source plugins, searchable by category or keyword.

'''''Sample Rails''''' - http://snippets.dzone.com/tag/rails

A collection of Rails code snippets.

'''''Agile Rails book''''' - http://www.amazon.com/gp/product/097669400X/002-0481267-8083260?v=glance&n=283155

An excellent resource for learning how to apply Agile programming concepts to Rails.

'''''Rails cheatsheet''''' - http://www.blainekendall.com/uploads/RubyOnRails-Cheatsheet-BlaineKendall.pdf

One user's list of best practices, gotchas and quirks of developing with Rails.

'''''Rails best practices''''' - http://www.therailsway.com/

An official best practices list for programming in Rails.

'''''Advanced Rails''''' - http://webonrails.com/

A resource for the advanced Rails programmer.

'''''Rails Blog''''' - http://weblog.rubyonrails.org/

An online community of updates about current happenings with the Rails platform.

'''''Rails Guides''''' - http://guides.rubyonrails.org/

An all in one resource for learning Rails including Howtos, security and contributing to the Rails community.

'''''Authoring Rails plugins''''' - http://nubyonrails.com/articles/2006/05/04/the-complete-guide-to-rails-plugins-part-i

A complete guide to authoring your own Rails plugins.

'''

== '''Tools for Rails (other than IDEs)''' ==
'''

'''Test Unit'''
The Rails stack uses Test::Unit, known as the default Ruby unit testing framework shipping with Ruby. There are various plugins and extension that could be used with Rails built-in Test::Unit to extend its functionality for support of TDD and BDD testing practices.

[http://wiki.rubyonrails.org/addons/testing]
The link provides additional information in the form of supporting resources, whitepapers, examples, and plug-in documentation

'''Example'''
[http://wiki.rubyonrails.org/testing/test-unitrequire]

Image:class CalculatorTest < Test::Unit::TestCase
def test_add_two_numbers_for_the_sum
calculator = Calculator.new
assert_equal 4, calculator.sum(2, 2)
end
end

== TDD: Test Driven Development ==

Test Driven Development is a combination of refactoring and test first development, a form of development where the test is

written prior to completed production code. The goal of TDD is the specification of requirements and not the validation of

requirements. There are a few testing frameworks that are used to implement the TDD programming technique.

[http://ruby.about.com/b/2009/01/28/test-driven-development-with-rails.htm]
This link provides a comprehensive overview of test driven development practices and available resources for implementation.

'''RSpec'''
RSpec is a testing framework for Behavior Driven Development, complete with its own expectations, matchers and mocking and

stubbing facilities. It goes along hand in hand with Cucumber, though it plays nicely with many other testing frameworks as well.

''Example expresses some basic desired behavior''[http://rspec.info/]

<nowiki>#</nowiki> bowling_spec.rb
require ‘bowling’
describe Bowling do
it "should score 0 for gutter game" do
bowling = Bowling.new
20.times { bowling.hit(0) }
bowling.score.should == 0
end
end

''Just enough code to make it pass.''

<nowiki>#</nowiki> bowling.rb
class Bowling
def hit(pins)
end
def score
0
end
end

'''Model Examples'''
These are the equivalent of unit tests in Rails’ built in testing. Ironically
(for the traditional TDD’er) these are the only specs that we feel should actually interact
with the database.

'''Controller Examples'''
These align somewhat with functional tests in rails, except
that they do not actually render views (though you can force rendering of views
if you prefer). Instead of setting expectations about what goes on a page, you
set expectations about what templates get rendered.

'''View Examples'''
This is the other half of Rails’ functional testing. View specs allow
you to set up assigns (thanks to ZenTest).

'''Helper Examples'''
let you specify directly methods that live in your helpers.

[http://www.ibm.com/developerworks/web/library/wa-rspec/]
The link provides a brief overview of RSpec with a comprehensive series of examples and a conceptual view of Rpecs step by step

implementation process

'''Cucumber'''
Cucumber is used with TDD and BDD within other testing frameworks such as RSpec by letting software development teams describe how

software should behave in plain text. The text is written in a business-readable domain-specific language and serves as

documentation, automated tests and development-aid - all rolled into one format.

[http://cukes.info/]
The link provides a detail decription, definition, and examples of Cucumber implementation best practices and supported

frameworks.

'''Cucumber Example:'''
Scenario: See all vendors
Given I am logged in as a user in the administrator role
And There are 3 vendors
When I go to the manage vendors page
Then I should see the first 3 vendor names

'''Shoulda'''
An extension to Test::Unit with additional helpers, macros, and assertions.

[http://www.thoughtbot.com/projects/shoulda]
The link provides a more conclusive definition of Shoulda along with installation facts and working examples of the Shoulda

testing framework within Ruby's built in Test::Unit

== BDD: Behavior Driven Development ==
[http://eggsonbread.com/2009/07/22/behavior-driven-development-in-a-nutshell/]
Behavior driven development was born from the concepts behind the implementation of TDD. It brings together strands from

TestDrivenDevelopment and DomainDrivenDesign into an integrated whole, making the relationship between these two powerful

approaches to software development more evident. Most test driven development testing frameworks such as RSpec and Cucumber also support behavior driven development testing.

[http://behaviour-driven.org/]
The link supports BDDs definition with additional links to more viable behavior driven development resources.

----

'''Other Test Tool Resources'''

''Watir:'' is an open-source library for automating web browsers. It allows you to write tests that are easy to read and maintain. It

is simple and flexible.
[http://wtr.rubyforge.org/]
The link provides an overview of Watir with installation specifications, examples, and supported platforms

''NullDB:'' [http://avdi.org/projects/nulldb/]
a way to speed up testing by avoiding database use.

''Bleakhouse:'' memory leak detection
[http://www.rubyinside.com/bleakhouse-tool-to-find-memory-leaks-in-your-rails-applications-470.html]
The link gives additional information on Bleakhouse profiling for memory leaks

''ruby-debug:''
Other than the extensive use of breakpoints Rails provides little to streamline the debugging process. Ruby-debug provides Rails with a plug-in extending the functionality of Rails built in debugger.

[http://rubyforge.org/softwaremap/trove_list.php?form_cat=47]
The link provides twenty additional debug resources available for RoR

== '''Conclusion''' ==

Rails is a very comprehensive development environment for Ruby with numerous extensions, plugins, and other resources outside of IDEs to strengthen the functionality of the open source web application framework.

== References ==

''All sources used to create this wiki are linked in the above text.''

CSC/ECE 517 Fall 2009/wiki1b team1

2009-09-28T19:56:32Z

Los Bravo: /* TDD: Test Driven Development */

CSC/ECE 517 Fall 2009

'''
== Resources for Rails (other than IDEs) ==
'''

IDEs are a valuable resource for Rails development, however there are many other resources and tools
that can either replace or supplement IDEs.

'''Resources for Rails other than IDEs
'''

'''''Rails API''''' - http://api.rubyonrails.org/

This site documents Rails files, classes and methods that can be used to build a Rails application.

'''''Rails Forum''''' - http://railsforum.com/

A discussion forum covering all aspects of Rails for beginners and experts including planning,
programming, extensions and production.

'''''Introducing Ruby on Rails'''''

Part 1 http://www.softwaredeveloper.com/features/intro-to-ruby-on-rails-042507/

Part 2 http://www.softwaredeveloper.com/features/intro-to-ruby-on-rails-part-two-043007/

An excellent introduction to Rails for novices

'''''Installers'''
''

Windows: InstantRails - http://instantrails.rubyforge.org/wiki/wiki.pl

An all in one, single click installer for Windows that includes a Rails server.

Mac: Locomotive - http://locomotive.raaum.org/

'''''Rails Projects''''' - http://www.workingwithrails.com/

A Database of Rails projects, programmers and websites

'''''Rails plugins''''' - http://agilewebdevelopment.com/

A collection of Rails open source plugins, searchable by category or keyword.

'''''Sample Rails''''' - http://snippets.dzone.com/tag/rails

A collection of Rails code snippets.

'''''Agile Rails book''''' - http://www.amazon.com/gp/product/097669400X/002-0481267-8083260?v=glance&n=283155

An excellent resource for learning how to apply Agile programming concepts to Rails.

'''''Rails cheatsheet''''' - http://www.blainekendall.com/uploads/RubyOnRails-Cheatsheet-BlaineKendall.pdf

One user's list of best practices, gotchas and quirks of developing with Rails.

'''''Rails best practices''''' - http://www.therailsway.com/

An official best practices list for programming in Rails.

'''''Advanced Rails''''' - http://webonrails.com/

A resource for the advanced Rails programmer.

'''''Rails Blog''''' - http://weblog.rubyonrails.org/

An online community of updates about current happenings with the Rails platform.

'''''Rails Guides''''' - http://guides.rubyonrails.org/

An all in one resource for learning Rails including Howtos, security and contributing to the Rails community.

'''''Authoring Rails plugins''''' - http://nubyonrails.com/articles/2006/05/04/the-complete-guide-to-rails-plugins-part-i

A complete guide to authoring your own Rails plugins.

'''

== '''Tools for Rails (other than IDEs)''' ==
'''

'''Test Unit'''
The Rails stack uses Test::Unit, known as the default Ruby unit testing framework shipping with Ruby. There are various plugins and extension that could be used with Rails built-in Test::Unit to extend its functionality for support of TDD and BDD testing practices.

[http://wiki.rubyonrails.org/addons/testing]
The link provides additional information in the form of supporting resources, whitepapers, examples, and plug-in documentation

'''Example'''
[http://wiki.rubyonrails.org/testing/test-unitrequire]

Image:class CalculatorTest < Test::Unit::TestCase
def test_add_two_numbers_for_the_sum
calculator = Calculator.new
assert_equal 4, calculator.sum(2, 2)
end
end

== TDD: Test Driven Development ==

Test Driven Development is a combination of refactoring and test first development, a form of development where the test is

written prior to completed production code. The goal of TDD is the specification of requirements and not the validation of

requirements. There are a few testing frameworks that are used to implement the TDD programming technique.

[http://ruby.about.com/b/2009/01/28/test-driven-development-with-rails.htm]
This link provides a comprehensive overview of test driven development practices and available resources for implementation.

'''RSpec'''
RSpec is a testing framework for Behavior Driven Development, complete with its own expectations, matchers and mocking and

stubbing facilities. It goes along hand in hand with Cucumber, though it plays nicely with many other testing frameworks as well.

''Example expresses some basic desired behavior''[http://rspec.info/]

<nowiki>#</nowiki> bowling_spec.rb
require ‘bowling’
describe Bowling do
it "should score 0 for gutter game" do
bowling = Bowling.new
20.times { bowling.hit(0) }
bowling.score.should == 0
end
end

<nowiki>#</nowiki> bowling.rb
class Bowling
def hit(pins)
end
def score
0
end
end

'''Model Examples'''
These are the equivalent of unit tests in Rails’ built in testing. Ironically
(for the traditional TDD’er) these are the only specs that we feel should actually interact
with the database.

'''Controller Examples'''
These align somewhat with functional tests in rails, except
that they do not actually render views (though you can force rendering of views
if you prefer). Instead of setting expectations about what goes on a page, you
set expectations about what templates get rendered.

'''View Examples'''
This is the other half of Rails’ functional testing. View specs allow
you to set up assigns (thanks to ZenTest).

'''Helper Examples'''
let you specify directly methods that live in your helpers.

[http://www.ibm.com/developerworks/web/library/wa-rspec/]
The link provides a brief overview of RSpec with a comprehensive series of examples and a conceptual view of Rpecs step by step

implementation process

'''Cucumber'''
Cucumber is used with TDD and BDD within other testing frameworks such as RSpec by letting software development teams describe how

software should behave in plain text. The text is written in a business-readable domain-specific language and serves as

documentation, automated tests and development-aid - all rolled into one format.

[http://cukes.info/]
The link provides a detail decription, definition, and examples of Cucumber implementation best practices and supported

frameworks.

'''Cucumber Example:'''
Scenario: See all vendors
Given I am logged in as a user in the administrator role
And There are 3 vendors
When I go to the manage vendors page
Then I should see the first 3 vendor names

'''Shoulda'''
An extension to Test::Unit with additional helpers, macros, and assertions.

[http://www.thoughtbot.com/projects/shoulda]
The link provides a more conclusive definition of Shoulda along with installation facts and working examples of the Shoulda

testing framework within Ruby's built in Test::Unit

== BDD: Behavior Driven Development ==
[http://eggsonbread.com/2009/07/22/behavior-driven-development-in-a-nutshell/]
Behavior driven development was born from the concepts behind the implementation of TDD. It brings together strands from

TestDrivenDevelopment and DomainDrivenDesign into an integrated whole, making the relationship between these two powerful

approaches to software development more evident. Most test driven development testing frameworks such as RSpec and Cucumber also support behavior driven development testing.

[http://behaviour-driven.org/]
The link supports BDDs definition with additional links to more viable behavior driven development resources.

----

'''Other Test Tool Resources'''

''Watir:'' is an open-source library for automating web browsers. It allows you to write tests that are easy to read and maintain. It

is simple and flexible.
[http://wtr.rubyforge.org/]
The link provides an overview of Watir with installation specifications, examples, and supported platforms

''NullDB:'' [http://avdi.org/projects/nulldb/]
a way to speed up testing by avoiding database use.

''Bleakhouse:'' memory leak detection
[http://www.rubyinside.com/bleakhouse-tool-to-find-memory-leaks-in-your-rails-applications-470.html]
The link gives additional information on Bleakhouse profiling for memory leaks

''ruby-debug:''
Other than the extensive use of breakpoints Rails provides little to streamline the debugging process. Ruby-debug provides Rails with a plug-in extending the functionality of Rails built in debugger.

[http://rubyforge.org/softwaremap/trove_list.php?form_cat=47]
The link provides twenty additional debug resources available for RoR

== '''Conclusion''' ==

Rails is a very comprehensive development environment for Ruby with numerous extensions, plugins, and other resources outside of IDEs to strengthen the functionality of the open source web application framework.

== References ==

''All sources used to create this wiki are linked in the above text.''

CSC/ECE 517 Fall 2009/wiki1b team1

2009-09-28T19:55:19Z

Los Bravo: /* TDD: Test Driven Development */

CSC/ECE 517 Fall 2009

'''
== Resources for Rails (other than IDEs) ==
'''

IDEs are a valuable resource for Rails development, however there are many other resources and tools
that can either replace or supplement IDEs.

'''Resources for Rails other than IDEs
'''

'''''Rails API''''' - http://api.rubyonrails.org/

This site documents Rails files, classes and methods that can be used to build a Rails application.

'''''Rails Forum''''' - http://railsforum.com/

A discussion forum covering all aspects of Rails for beginners and experts including planning,
programming, extensions and production.

'''''Introducing Ruby on Rails'''''

Part 1 http://www.softwaredeveloper.com/features/intro-to-ruby-on-rails-042507/

Part 2 http://www.softwaredeveloper.com/features/intro-to-ruby-on-rails-part-two-043007/

An excellent introduction to Rails for novices

'''''Installers'''
''

Windows: InstantRails - http://instantrails.rubyforge.org/wiki/wiki.pl

An all in one, single click installer for Windows that includes a Rails server.

Mac: Locomotive - http://locomotive.raaum.org/

'''''Rails Projects''''' - http://www.workingwithrails.com/

A Database of Rails projects, programmers and websites

'''''Rails plugins''''' - http://agilewebdevelopment.com/

A collection of Rails open source plugins, searchable by category or keyword.

'''''Sample Rails''''' - http://snippets.dzone.com/tag/rails

A collection of Rails code snippets.

'''''Agile Rails book''''' - http://www.amazon.com/gp/product/097669400X/002-0481267-8083260?v=glance&n=283155

An excellent resource for learning how to apply Agile programming concepts to Rails.

'''''Rails cheatsheet''''' - http://www.blainekendall.com/uploads/RubyOnRails-Cheatsheet-BlaineKendall.pdf

One user's list of best practices, gotchas and quirks of developing with Rails.

'''''Rails best practices''''' - http://www.therailsway.com/

An official best practices list for programming in Rails.

'''''Advanced Rails''''' - http://webonrails.com/

A resource for the advanced Rails programmer.

'''''Rails Blog''''' - http://weblog.rubyonrails.org/

An online community of updates about current happenings with the Rails platform.

'''''Rails Guides''''' - http://guides.rubyonrails.org/

An all in one resource for learning Rails including Howtos, security and contributing to the Rails community.

'''''Authoring Rails plugins''''' - http://nubyonrails.com/articles/2006/05/04/the-complete-guide-to-rails-plugins-part-i

A complete guide to authoring your own Rails plugins.

'''

== '''Tools for Rails (other than IDEs)''' ==
'''

'''Test Unit'''
The Rails stack uses Test::Unit, known as the default Ruby unit testing framework shipping with Ruby. There are various plugins and extension that could be used with Rails built-in Test::Unit to extend its functionality for support of TDD and BDD testing practices.

[http://wiki.rubyonrails.org/addons/testing]
The link provides additional information in the form of supporting resources, whitepapers, examples, and plug-in documentation

'''Example'''
[http://wiki.rubyonrails.org/testing/test-unitrequire]

Image:class CalculatorTest < Test::Unit::TestCase
def test_add_two_numbers_for_the_sum
calculator = Calculator.new
assert_equal 4, calculator.sum(2, 2)
end
end

== TDD: Test Driven Development ==

Test Driven Development is a combination of refactoring and test first development, a form of development where the test is

written prior to completed production code. The goal of TDD is the specification of requirements and not the validation of

requirements. There are a few testing frameworks that are used to implement the TDD programming technique.

[http://ruby.about.com/b/2009/01/28/test-driven-development-with-rails.htm]
This link provides a comprehensive overview of test driven development practices and available resources for implementation.

'''RSpec'''
RSpec is a testing framework for Behavior Driven Development, complete with its own expectations, matchers and mocking and

stubbing facilities. It goes along hand in hand with Cucumber, though it plays nicely with many other testing frameworks as well.

''Example expresses some basic desired behavior''[http://rspec.info/]

'#'bowling_spec.rb
require ‘bowling’
describe Bowling do
it "should score 0 for gutter game" do
bowling = Bowling.new
20.times { bowling.hit(0) }
bowling.score.should == 0
end
end

# bowling.rb
class Bowling
def hit(pins)
end
def score
0
end
end

'''Model Examples'''
These are the equivalent of unit tests in Rails’ built in testing. Ironically
(for the traditional TDD’er) these are the only specs that we feel should actually interact
with the database.

'''Controller Examples'''
These align somewhat with functional tests in rails, except
that they do not actually render views (though you can force rendering of views
if you prefer). Instead of setting expectations about what goes on a page, you
set expectations about what templates get rendered.

'''View Examples'''
This is the other half of Rails’ functional testing. View specs allow
you to set up assigns (thanks to ZenTest).

'''Helper Examples'''
let you specify directly methods that live in your helpers.

[http://www.ibm.com/developerworks/web/library/wa-rspec/]
The link provides a brief overview of RSpec with a comprehensive series of examples and a conceptual view of Rpecs step by step

implementation process

'''Cucumber'''
Cucumber is used with TDD and BDD within other testing frameworks such as RSpec by letting software development teams describe how

software should behave in plain text. The text is written in a business-readable domain-specific language and serves as

documentation, automated tests and development-aid - all rolled into one format.

[http://cukes.info/]
The link provides a detail decription, definition, and examples of Cucumber implementation best practices and supported

frameworks.

'''Cucumber Example:'''
Scenario: See all vendors
Given I am logged in as a user in the administrator role
And There are 3 vendors
When I go to the manage vendors page
Then I should see the first 3 vendor names

'''Shoulda'''
An extension to Test::Unit with additional helpers, macros, and assertions.

[http://www.thoughtbot.com/projects/shoulda]
The link provides a more conclusive definition of Shoulda along with installation facts and working examples of the Shoulda

testing framework within Ruby's built in Test::Unit

== BDD: Behavior Driven Development ==
[http://eggsonbread.com/2009/07/22/behavior-driven-development-in-a-nutshell/]
Behavior driven development was born from the concepts behind the implementation of TDD. It brings together strands from

TestDrivenDevelopment and DomainDrivenDesign into an integrated whole, making the relationship between these two powerful

approaches to software development more evident. Most test driven development testing frameworks such as RSpec and Cucumber also support behavior driven development testing.

[http://behaviour-driven.org/]
The link supports BDDs definition with additional links to more viable behavior driven development resources.

----

'''Other Test Tool Resources'''

''Watir:'' is an open-source library for automating web browsers. It allows you to write tests that are easy to read and maintain. It

is simple and flexible.
[http://wtr.rubyforge.org/]
The link provides an overview of Watir with installation specifications, examples, and supported platforms

''NullDB:'' [http://avdi.org/projects/nulldb/]
a way to speed up testing by avoiding database use.

''Bleakhouse:'' memory leak detection
[http://www.rubyinside.com/bleakhouse-tool-to-find-memory-leaks-in-your-rails-applications-470.html]
The link gives additional information on Bleakhouse profiling for memory leaks

''ruby-debug:''
Other than the extensive use of breakpoints Rails provides little to streamline the debugging process. Ruby-debug provides Rails with a plug-in extending the functionality of Rails built in debugger.

[http://rubyforge.org/softwaremap/trove_list.php?form_cat=47]
The link provides twenty additional debug resources available for RoR

== '''Conclusion''' ==

Rails is a very comprehensive development environment for Ruby with numerous extensions, plugins, and other resources outside of IDEs to strengthen the functionality of the open source web application framework.

== References ==

''All sources used to create this wiki are linked in the above text.''

CSC/ECE 517 Fall 2009/wiki1b team1

2009-09-28T19:53:33Z

Los Bravo: /* TDD: Test Driven Development */

CSC/ECE 517 Fall 2009

'''
== Resources for Rails (other than IDEs) ==
'''

IDEs are a valuable resource for Rails development, however there are many other resources and tools
that can either replace or supplement IDEs.

'''Resources for Rails other than IDEs
'''

'''''Rails API''''' - http://api.rubyonrails.org/

This site documents Rails files, classes and methods that can be used to build a Rails application.

'''''Rails Forum''''' - http://railsforum.com/

A discussion forum covering all aspects of Rails for beginners and experts including planning,
programming, extensions and production.

'''''Introducing Ruby on Rails'''''

Part 1 http://www.softwaredeveloper.com/features/intro-to-ruby-on-rails-042507/

Part 2 http://www.softwaredeveloper.com/features/intro-to-ruby-on-rails-part-two-043007/

An excellent introduction to Rails for novices

'''''Installers'''
''

Windows: InstantRails - http://instantrails.rubyforge.org/wiki/wiki.pl

An all in one, single click installer for Windows that includes a Rails server.

Mac: Locomotive - http://locomotive.raaum.org/

'''''Rails Projects''''' - http://www.workingwithrails.com/

A Database of Rails projects, programmers and websites

'''''Rails plugins''''' - http://agilewebdevelopment.com/

A collection of Rails open source plugins, searchable by category or keyword.

'''''Sample Rails''''' - http://snippets.dzone.com/tag/rails

A collection of Rails code snippets.

'''''Agile Rails book''''' - http://www.amazon.com/gp/product/097669400X/002-0481267-8083260?v=glance&n=283155

An excellent resource for learning how to apply Agile programming concepts to Rails.

'''''Rails cheatsheet''''' - http://www.blainekendall.com/uploads/RubyOnRails-Cheatsheet-BlaineKendall.pdf

One user's list of best practices, gotchas and quirks of developing with Rails.

'''''Rails best practices''''' - http://www.therailsway.com/

An official best practices list for programming in Rails.

'''''Advanced Rails''''' - http://webonrails.com/

A resource for the advanced Rails programmer.

'''''Rails Blog''''' - http://weblog.rubyonrails.org/

An online community of updates about current happenings with the Rails platform.

'''''Rails Guides''''' - http://guides.rubyonrails.org/

An all in one resource for learning Rails including Howtos, security and contributing to the Rails community.

'''''Authoring Rails plugins''''' - http://nubyonrails.com/articles/2006/05/04/the-complete-guide-to-rails-plugins-part-i

A complete guide to authoring your own Rails plugins.

'''

== '''Tools for Rails (other than IDEs)''' ==
'''

'''Test Unit'''
The Rails stack uses Test::Unit, known as the default Ruby unit testing framework shipping with Ruby. There are various plugins and extension that could be used with Rails built-in Test::Unit to extend its functionality for support of TDD and BDD testing practices.

[http://wiki.rubyonrails.org/addons/testing]
The link provides additional information in the form of supporting resources, whitepapers, examples, and plug-in documentation

'''Example'''
[http://wiki.rubyonrails.org/testing/test-unitrequire]

Image:class CalculatorTest < Test::Unit::TestCase
def test_add_two_numbers_for_the_sum
calculator = Calculator.new
assert_equal 4, calculator.sum(2, 2)
end
end

== TDD: Test Driven Development ==

Test Driven Development is a combination of refactoring and test first development, a form of development where the test is

written prior to completed production code. The goal of TDD is the specification of requirements and not the validation of

requirements. There are a few testing frameworks that are used to implement the TDD programming technique.

[http://ruby.about.com/b/2009/01/28/test-driven-development-with-rails.htm]
This link provides a comprehensive overview of test driven development practices and available resources for implementation.

'''RSpec'''
RSpec is a testing framework for Behavior Driven Development, complete with its own expectations, matchers and mocking and

stubbing facilities. It goes along hand in hand with Cucumber, though it plays nicely with many other testing frameworks as well.

''Example expresses some basic desired behavior''[http://rspec.info/]

bowling_spec.rb
require ‘bowling’
describe Bowling do
it "should score 0 for gutter game" do
bowling = Bowling.new
20.times { bowling.hit(0) }
bowling.score.should == 0
end
end

'''Model Examples'''
These are the equivalent of unit tests in Rails’ built in testing. Ironically
(for the traditional TDD’er) these are the only specs that we feel should actually interact
with the database.

'''Controller Examples'''
These align somewhat with functional tests in rails, except
that they do not actually render views (though you can force rendering of views
if you prefer). Instead of setting expectations about what goes on a page, you
set expectations about what templates get rendered.

'''View Examples'''
This is the other half of Rails’ functional testing. View specs allow
you to set up assigns (thanks to ZenTest).

'''Helper Examples'''
let you specify directly methods that live in your helpers.

[http://www.ibm.com/developerworks/web/library/wa-rspec/]
The link provides a brief overview of RSpec with a comprehensive series of examples and a conceptual view of Rpecs step by step

implementation process

'''Cucumber'''
Cucumber is used with TDD and BDD within other testing frameworks such as RSpec by letting software development teams describe how

software should behave in plain text. The text is written in a business-readable domain-specific language and serves as

documentation, automated tests and development-aid - all rolled into one format.

[http://cukes.info/]
The link provides a detail decription, definition, and examples of Cucumber implementation best practices and supported

frameworks.

'''Cucumber Example:'''
Scenario: See all vendors
Given I am logged in as a user in the administrator role
And There are 3 vendors
When I go to the manage vendors page
Then I should see the first 3 vendor names

'''Shoulda'''
An extension to Test::Unit with additional helpers, macros, and assertions.

[http://www.thoughtbot.com/projects/shoulda]
The link provides a more conclusive definition of Shoulda along with installation facts and working examples of the Shoulda

testing framework within Ruby's built in Test::Unit

== BDD: Behavior Driven Development ==
[http://eggsonbread.com/2009/07/22/behavior-driven-development-in-a-nutshell/]
Behavior driven development was born from the concepts behind the implementation of TDD. It brings together strands from

TestDrivenDevelopment and DomainDrivenDesign into an integrated whole, making the relationship between these two powerful

approaches to software development more evident. Most test driven development testing frameworks such as RSpec and Cucumber also support behavior driven development testing.

[http://behaviour-driven.org/]
The link supports BDDs definition with additional links to more viable behavior driven development resources.

----

'''Other Test Tool Resources'''

''Watir:'' is an open-source library for automating web browsers. It allows you to write tests that are easy to read and maintain. It

is simple and flexible.
[http://wtr.rubyforge.org/]
The link provides an overview of Watir with installation specifications, examples, and supported platforms

''NullDB:'' [http://avdi.org/projects/nulldb/]
a way to speed up testing by avoiding database use.

''Bleakhouse:'' memory leak detection
[http://www.rubyinside.com/bleakhouse-tool-to-find-memory-leaks-in-your-rails-applications-470.html]
The link gives additional information on Bleakhouse profiling for memory leaks

''ruby-debug:''
Other than the extensive use of breakpoints Rails provides little to streamline the debugging process. Ruby-debug provides Rails with a plug-in extending the functionality of Rails built in debugger.

[http://rubyforge.org/softwaremap/trove_list.php?form_cat=47]
The link provides twenty additional debug resources available for RoR

== '''Conclusion''' ==

Rails is a very comprehensive development environment for Ruby with numerous extensions, plugins, and other resources outside of IDEs to strengthen the functionality of the open source web application framework.

== References ==

''All sources used to create this wiki are linked in the above text.''

CSC/ECE 517 Fall 2009/wiki1b team1

2009-09-28T19:51:56Z

Los Bravo: /* TDD: Test Driven Development */

CSC/ECE 517 Fall 2009

'''
== Resources for Rails (other than IDEs) ==
'''

IDEs are a valuable resource for Rails development, however there are many other resources and tools
that can either replace or supplement IDEs.

'''Resources for Rails other than IDEs
'''

'''''Rails API''''' - http://api.rubyonrails.org/

This site documents Rails files, classes and methods that can be used to build a Rails application.

'''''Rails Forum''''' - http://railsforum.com/

A discussion forum covering all aspects of Rails for beginners and experts including planning,
programming, extensions and production.

'''''Introducing Ruby on Rails'''''

Part 1 http://www.softwaredeveloper.com/features/intro-to-ruby-on-rails-042507/

Part 2 http://www.softwaredeveloper.com/features/intro-to-ruby-on-rails-part-two-043007/

An excellent introduction to Rails for novices

'''''Installers'''
''

Windows: InstantRails - http://instantrails.rubyforge.org/wiki/wiki.pl

An all in one, single click installer for Windows that includes a Rails server.

Mac: Locomotive - http://locomotive.raaum.org/

'''''Rails Projects''''' - http://www.workingwithrails.com/

A Database of Rails projects, programmers and websites

'''''Rails plugins''''' - http://agilewebdevelopment.com/

A collection of Rails open source plugins, searchable by category or keyword.

'''''Sample Rails''''' - http://snippets.dzone.com/tag/rails

A collection of Rails code snippets.

'''''Agile Rails book''''' - http://www.amazon.com/gp/product/097669400X/002-0481267-8083260?v=glance&n=283155

An excellent resource for learning how to apply Agile programming concepts to Rails.

'''''Rails cheatsheet''''' - http://www.blainekendall.com/uploads/RubyOnRails-Cheatsheet-BlaineKendall.pdf

One user's list of best practices, gotchas and quirks of developing with Rails.

'''''Rails best practices''''' - http://www.therailsway.com/

An official best practices list for programming in Rails.

'''''Advanced Rails''''' - http://webonrails.com/

A resource for the advanced Rails programmer.

'''''Rails Blog''''' - http://weblog.rubyonrails.org/

An online community of updates about current happenings with the Rails platform.

'''''Rails Guides''''' - http://guides.rubyonrails.org/

An all in one resource for learning Rails including Howtos, security and contributing to the Rails community.

'''''Authoring Rails plugins''''' - http://nubyonrails.com/articles/2006/05/04/the-complete-guide-to-rails-plugins-part-i

A complete guide to authoring your own Rails plugins.

'''

== '''Tools for Rails (other than IDEs)''' ==
'''

'''Test Unit'''
The Rails stack uses Test::Unit, known as the default Ruby unit testing framework shipping with Ruby. There are various plugins and extension that could be used with Rails built-in Test::Unit to extend its functionality for support of TDD and BDD testing practices.

[http://wiki.rubyonrails.org/addons/testing]
The link provides additional information in the form of supporting resources, whitepapers, examples, and plug-in documentation

'''Example'''
[http://wiki.rubyonrails.org/testing/test-unitrequire]

Image:class CalculatorTest < Test::Unit::TestCase
def test_add_two_numbers_for_the_sum
calculator = Calculator.new
assert_equal 4, calculator.sum(2, 2)
end
end

== TDD: Test Driven Development ==

Test Driven Development is a combination of refactoring and test first development, a form of development where the test is

written prior to completed production code. The goal of TDD is the specification of requirements and not the validation of

requirements. There are a few testing frameworks that are used to implement the TDD programming technique.

[http://ruby.about.com/b/2009/01/28/test-driven-development-with-rails.htm]
This link provides a comprehensive overview of test driven development practices and available resources for implementation.

'''RSpec'''
RSpec is a testing framework for Behavior Driven Development, complete with its own expectations, matchers and mocking and

stubbing facilities. It goes along hand in hand with Cucumber, though it plays nicely with many other testing frameworks as well.

'''Example expresses some basic desired behavior'''''Italic text''

bowling_spec.rb
require ‘bowling’
describe Bowling do
it "should score 0 for gutter game" do
bowling = Bowling.new
20.times { bowling.hit(0) }
bowling.score.should == 0
end
end

'''Model Examples'''
These are the equivalent of unit tests in Rails’ built in testing. Ironically
(for the traditional TDD’er) these are the only specs that we feel should actually interact
with the database.

'''Controller Examples'''
These align somewhat with functional tests in rails, except
that they do not actually render views (though you can force rendering of views
if you prefer). Instead of setting expectations about what goes on a page, you
set expectations about what templates get rendered.

'''View Examples'''
This is the other half of Rails’ functional testing. View specs allow
you to set up assigns (thanks to ZenTest).

'''Helper Examples'''
let you specify directly methods that live in your helpers.

[http://www.ibm.com/developerworks/web/library/wa-rspec/]
The link provides a brief overview of RSpec with a comprehensive series of examples and a conceptual view of Rpecs step by step

implementation process

'''Cucumber'''
Cucumber is used with TDD and BDD within other testing frameworks such as RSpec by letting software development teams describe how

software should behave in plain text. The text is written in a business-readable domain-specific language and serves as

documentation, automated tests and development-aid - all rolled into one format.

[http://cukes.info/]
The link provides a detail decription, definition, and examples of Cucumber implementation best practices and supported

frameworks.

'''Cucumber Example:'''
Scenario: See all vendors
Given I am logged in as a user in the administrator role
And There are 3 vendors
When I go to the manage vendors page
Then I should see the first 3 vendor names

'''Shoulda'''
An extension to Test::Unit with additional helpers, macros, and assertions.

[http://www.thoughtbot.com/projects/shoulda]
The link provides a more conclusive definition of Shoulda along with installation facts and working examples of the Shoulda

testing framework within Ruby's built in Test::Unit

== BDD: Behavior Driven Development ==
[http://eggsonbread.com/2009/07/22/behavior-driven-development-in-a-nutshell/]
Behavior driven development was born from the concepts behind the implementation of TDD. It brings together strands from

TestDrivenDevelopment and DomainDrivenDesign into an integrated whole, making the relationship between these two powerful

approaches to software development more evident. Most test driven development testing frameworks such as RSpec and Cucumber also support behavior driven development testing.

[http://behaviour-driven.org/]
The link supports BDDs definition with additional links to more viable behavior driven development resources.

----

'''Other Test Tool Resources'''

''Watir:'' is an open-source library for automating web browsers. It allows you to write tests that are easy to read and maintain. It

is simple and flexible.
[http://wtr.rubyforge.org/]
The link provides an overview of Watir with installation specifications, examples, and supported platforms

''NullDB:'' [http://avdi.org/projects/nulldb/]
a way to speed up testing by avoiding database use.

''Bleakhouse:'' memory leak detection
[http://www.rubyinside.com/bleakhouse-tool-to-find-memory-leaks-in-your-rails-applications-470.html]
The link gives additional information on Bleakhouse profiling for memory leaks

''ruby-debug:''
Other than the extensive use of breakpoints Rails provides little to streamline the debugging process. Ruby-debug provides Rails with a plug-in extending the functionality of Rails built in debugger.

[http://rubyforge.org/softwaremap/trove_list.php?form_cat=47]
The link provides twenty additional debug resources available for RoR

== '''Conclusion''' ==

Rails is a very comprehensive development environment for Ruby with numerous extensions, plugins, and other resources outside of IDEs to strengthen the functionality of the open source web application framework.

== References ==

''All sources used to create this wiki are linked in the above text.''

CSC/ECE 517 Fall 2009/wiki1b team1

2009-09-28T19:51:28Z

Los Bravo: /* TDD: Test Driven Development */

CSC/ECE 517 Fall 2009

'''
== Resources for Rails (other than IDEs) ==
'''

IDEs are a valuable resource for Rails development, however there are many other resources and tools
that can either replace or supplement IDEs.

'''Resources for Rails other than IDEs
'''

'''''Rails API''''' - http://api.rubyonrails.org/

This site documents Rails files, classes and methods that can be used to build a Rails application.

'''''Rails Forum''''' - http://railsforum.com/

A discussion forum covering all aspects of Rails for beginners and experts including planning,
programming, extensions and production.

'''''Introducing Ruby on Rails'''''

Part 1 http://www.softwaredeveloper.com/features/intro-to-ruby-on-rails-042507/

Part 2 http://www.softwaredeveloper.com/features/intro-to-ruby-on-rails-part-two-043007/

An excellent introduction to Rails for novices

'''''Installers'''
''

Windows: InstantRails - http://instantrails.rubyforge.org/wiki/wiki.pl

An all in one, single click installer for Windows that includes a Rails server.

Mac: Locomotive - http://locomotive.raaum.org/

'''''Rails Projects''''' - http://www.workingwithrails.com/

A Database of Rails projects, programmers and websites

'''''Rails plugins''''' - http://agilewebdevelopment.com/

A collection of Rails open source plugins, searchable by category or keyword.

'''''Sample Rails''''' - http://snippets.dzone.com/tag/rails

A collection of Rails code snippets.

'''''Agile Rails book''''' - http://www.amazon.com/gp/product/097669400X/002-0481267-8083260?v=glance&n=283155

An excellent resource for learning how to apply Agile programming concepts to Rails.

'''''Rails cheatsheet''''' - http://www.blainekendall.com/uploads/RubyOnRails-Cheatsheet-BlaineKendall.pdf

One user's list of best practices, gotchas and quirks of developing with Rails.

'''''Rails best practices''''' - http://www.therailsway.com/

An official best practices list for programming in Rails.

'''''Advanced Rails''''' - http://webonrails.com/

A resource for the advanced Rails programmer.

'''''Rails Blog''''' - http://weblog.rubyonrails.org/

An online community of updates about current happenings with the Rails platform.

'''''Rails Guides''''' - http://guides.rubyonrails.org/

An all in one resource for learning Rails including Howtos, security and contributing to the Rails community.

'''''Authoring Rails plugins''''' - http://nubyonrails.com/articles/2006/05/04/the-complete-guide-to-rails-plugins-part-i

A complete guide to authoring your own Rails plugins.

'''

== '''Tools for Rails (other than IDEs)''' ==
'''

'''Test Unit'''
The Rails stack uses Test::Unit, known as the default Ruby unit testing framework shipping with Ruby. There are various plugins and extension that could be used with Rails built-in Test::Unit to extend its functionality for support of TDD and BDD testing practices.

[http://wiki.rubyonrails.org/addons/testing]
The link provides additional information in the form of supporting resources, whitepapers, examples, and plug-in documentation

'''Example'''
[http://wiki.rubyonrails.org/testing/test-unitrequire]

Image:class CalculatorTest < Test::Unit::TestCase
def test_add_two_numbers_for_the_sum
calculator = Calculator.new
assert_equal 4, calculator.sum(2, 2)
end
end

== TDD: Test Driven Development ==

Test Driven Development is a combination of refactoring and test first development, a form of development where the test is

written prior to completed production code. The goal of TDD is the specification of requirements and not the validation of

requirements. There are a few testing frameworks that are used to implement the TDD programming technique.

[http://ruby.about.com/b/2009/01/28/test-driven-development-with-rails.htm]
This link provides a comprehensive overview of test driven development practices and available resources for implementation.

'''RSpec'''
RSpec is a testing framework for Behavior Driven Development, complete with its own expectations, matchers and mocking and

stubbing facilities. It goes along hand in hand with Cucumber, though it plays nicely with many other testing frameworks as well.

Example expresses some basic desired behavior

bowling_spec.rb
require ‘bowling’
describe Bowling do
it "should score 0 for gutter game" do
bowling = Bowling.new
20.times { bowling.hit(0) }
bowling.score.should == 0
end
end

'''Model Examples'''
These are the equivalent of unit tests in Rails’ built in testing. Ironically
(for the traditional TDD’er) these are the only specs that we feel should actually interact
with the database.

'''Controller Examples'''
These align somewhat with functional tests in rails, except
that they do not actually render views (though you can force rendering of views
if you prefer). Instead of setting expectations about what goes on a page, you
set expectations about what templates get rendered.

'''View Examples'''
This is the other half of Rails’ functional testing. View specs allow
you to set up assigns (thanks to ZenTest).

'''Helper Examples'''
let you specify directly methods that live in your helpers.

[http://www.ibm.com/developerworks/web/library/wa-rspec/]
The link provides a brief overview of RSpec with a comprehensive series of examples and a conceptual view of Rpecs step by step

implementation process

'''Cucumber'''
Cucumber is used with TDD and BDD within other testing frameworks such as RSpec by letting software development teams describe how

software should behave in plain text. The text is written in a business-readable domain-specific language and serves as

documentation, automated tests and development-aid - all rolled into one format.

[http://cukes.info/]
The link provides a detail decription, definition, and examples of Cucumber implementation best practices and supported

frameworks.

'''Cucumber Example:'''
Scenario: See all vendors
Given I am logged in as a user in the administrator role
And There are 3 vendors
When I go to the manage vendors page
Then I should see the first 3 vendor names

'''Shoulda'''
An extension to Test::Unit with additional helpers, macros, and assertions.

[http://www.thoughtbot.com/projects/shoulda]
The link provides a more conclusive definition of Shoulda along with installation facts and working examples of the Shoulda

testing framework within Ruby's built in Test::Unit

== BDD: Behavior Driven Development ==
[http://eggsonbread.com/2009/07/22/behavior-driven-development-in-a-nutshell/]
Behavior driven development was born from the concepts behind the implementation of TDD. It brings together strands from

TestDrivenDevelopment and DomainDrivenDesign into an integrated whole, making the relationship between these two powerful

approaches to software development more evident. Most test driven development testing frameworks such as RSpec and Cucumber also support behavior driven development testing.

[http://behaviour-driven.org/]
The link supports BDDs definition with additional links to more viable behavior driven development resources.

----

'''Other Test Tool Resources'''

''Watir:'' is an open-source library for automating web browsers. It allows you to write tests that are easy to read and maintain. It

is simple and flexible.
[http://wtr.rubyforge.org/]
The link provides an overview of Watir with installation specifications, examples, and supported platforms

''NullDB:'' [http://avdi.org/projects/nulldb/]
a way to speed up testing by avoiding database use.

''Bleakhouse:'' memory leak detection
[http://www.rubyinside.com/bleakhouse-tool-to-find-memory-leaks-in-your-rails-applications-470.html]
The link gives additional information on Bleakhouse profiling for memory leaks

''ruby-debug:''
Other than the extensive use of breakpoints Rails provides little to streamline the debugging process. Ruby-debug provides Rails with a plug-in extending the functionality of Rails built in debugger.

[http://rubyforge.org/softwaremap/trove_list.php?form_cat=47]
The link provides twenty additional debug resources available for RoR

== '''Conclusion''' ==

Rails is a very comprehensive development environment for Ruby with numerous extensions, plugins, and other resources outside of IDEs to strengthen the functionality of the open source web application framework.

== References ==

''All sources used to create this wiki are linked in the above text.''

CSC/ECE 517 Fall 2009/wiki1b team1

2009-09-28T19:51:05Z

Los Bravo: /* TDD: Test Driven Development */

CSC/ECE 517 Fall 2009

'''
== Resources for Rails (other than IDEs) ==
'''

IDEs are a valuable resource for Rails development, however there are many other resources and tools
that can either replace or supplement IDEs.

'''Resources for Rails other than IDEs
'''

'''''Rails API''''' - http://api.rubyonrails.org/

This site documents Rails files, classes and methods that can be used to build a Rails application.

'''''Rails Forum''''' - http://railsforum.com/

A discussion forum covering all aspects of Rails for beginners and experts including planning,
programming, extensions and production.

'''''Introducing Ruby on Rails'''''

Part 1 http://www.softwaredeveloper.com/features/intro-to-ruby-on-rails-042507/

Part 2 http://www.softwaredeveloper.com/features/intro-to-ruby-on-rails-part-two-043007/

An excellent introduction to Rails for novices

'''''Installers'''
''

Windows: InstantRails - http://instantrails.rubyforge.org/wiki/wiki.pl

An all in one, single click installer for Windows that includes a Rails server.

Mac: Locomotive - http://locomotive.raaum.org/

'''''Rails Projects''''' - http://www.workingwithrails.com/

A Database of Rails projects, programmers and websites

'''''Rails plugins''''' - http://agilewebdevelopment.com/

A collection of Rails open source plugins, searchable by category or keyword.

'''''Sample Rails''''' - http://snippets.dzone.com/tag/rails

A collection of Rails code snippets.

'''''Agile Rails book''''' - http://www.amazon.com/gp/product/097669400X/002-0481267-8083260?v=glance&n=283155

An excellent resource for learning how to apply Agile programming concepts to Rails.

'''''Rails cheatsheet''''' - http://www.blainekendall.com/uploads/RubyOnRails-Cheatsheet-BlaineKendall.pdf

One user's list of best practices, gotchas and quirks of developing with Rails.

'''''Rails best practices''''' - http://www.therailsway.com/

An official best practices list for programming in Rails.

'''''Advanced Rails''''' - http://webonrails.com/

A resource for the advanced Rails programmer.

'''''Rails Blog''''' - http://weblog.rubyonrails.org/

An online community of updates about current happenings with the Rails platform.

'''''Rails Guides''''' - http://guides.rubyonrails.org/

An all in one resource for learning Rails including Howtos, security and contributing to the Rails community.

'''''Authoring Rails plugins''''' - http://nubyonrails.com/articles/2006/05/04/the-complete-guide-to-rails-plugins-part-i

A complete guide to authoring your own Rails plugins.

'''

== '''Tools for Rails (other than IDEs)''' ==
'''

'''Test Unit'''
The Rails stack uses Test::Unit, known as the default Ruby unit testing framework shipping with Ruby. There are various plugins and extension that could be used with Rails built-in Test::Unit to extend its functionality for support of TDD and BDD testing practices.

[http://wiki.rubyonrails.org/addons/testing]
The link provides additional information in the form of supporting resources, whitepapers, examples, and plug-in documentation

'''Example'''
[http://wiki.rubyonrails.org/testing/test-unitrequire]

Image:class CalculatorTest < Test::Unit::TestCase
def test_add_two_numbers_for_the_sum
calculator = Calculator.new
assert_equal 4, calculator.sum(2, 2)
end
end

== TDD: Test Driven Development ==

Test Driven Development is a combination of refactoring and test first development, a form of development where the test is

written prior to completed production code. The goal of TDD is the specification of requirements and not the validation of

requirements. There are a few testing frameworks that are used to implement the TDD programming technique.

[http://ruby.about.com/b/2009/01/28/test-driven-development-with-rails.htm]
This link provides a comprehensive overview of test driven development practices and available resources for implementation.

'''RSpec'''
RSpec is a testing framework for Behavior Driven Development, complete with its own expectations, matchers and mocking and

stubbing facilities. It goes along hand in hand with Cucumber, though it plays nicely with many other testing frameworks as well.

Example expresses some basic desired behavior

bowling_spec.rb
require ‘bowling’
describe Bowling do
it "should score 0 for gutter game" do
bowling = Bowling.new
20.times { bowling.hit(0) }
bowling.score.should == 0
end
end

'''Model Examples'''
These are the equivalent of unit tests in Rails’ built in testing. Ironically
(for the traditional TDD’er) these are the only specs that we feel should actually interact
with the database.

'''Controller Examples'''
These align somewhat with functional tests in rails, except
that they do not actually render views (though you can force rendering of views
if you prefer). Instead of setting expectations about what goes on a page, you
set expectations about what templates get rendered.

'''View Examples'''
This is the other half of Rails’ functional testing. View specs allow
you to set up assigns (thanks to ZenTest).

'''Helper Examples'''
let you specify directly methods that live in your helpers.

[http://www.ibm.com/developerworks/web/library/wa-rspec/]
The link provides a brief overview of RSpec with a comprehensive series of examples and a conceptual view of Rpecs step by step

implementation process

'''Cucumber'''
Cucumber is used with TDD and BDD within other testing frameworks such as RSpec by letting software development teams describe how

software should behave in plain text. The text is written in a business-readable domain-specific language and serves as

documentation, automated tests and development-aid - all rolled into one format.

[http://cukes.info/]
The link provides a detail decription, definition, and examples of Cucumber implementation best practices and supported

frameworks.

'''Cucumber Example:'''
Scenario: See all vendors
Given I am logged in as a user in the administrator role
And There are 3 vendors
When I go to the manage vendors page
Then I should see the first 3 vendor names

'''Shoulda'''
An extension to Test::Unit with additional helpers, macros, and assertions.

[http://www.thoughtbot.com/projects/shoulda]
The link provides a more conclusive definition of Shoulda along with installation facts and working examples of the Shoulda

testing framework within Ruby's built in Test::Unit

== BDD: Behavior Driven Development ==
[http://eggsonbread.com/2009/07/22/behavior-driven-development-in-a-nutshell/]
Behavior driven development was born from the concepts behind the implementation of TDD. It brings together strands from

TestDrivenDevelopment and DomainDrivenDesign into an integrated whole, making the relationship between these two powerful

approaches to software development more evident. Most test driven development testing frameworks such as RSpec and Cucumber also support behavior driven development testing.

[http://behaviour-driven.org/]
The link supports BDDs definition with additional links to more viable behavior driven development resources.

----

'''Other Test Tool Resources'''

''Watir:'' is an open-source library for automating web browsers. It allows you to write tests that are easy to read and maintain. It

is simple and flexible.
[http://wtr.rubyforge.org/]
The link provides an overview of Watir with installation specifications, examples, and supported platforms

''NullDB:'' [http://avdi.org/projects/nulldb/]
a way to speed up testing by avoiding database use.

''Bleakhouse:'' memory leak detection
[http://www.rubyinside.com/bleakhouse-tool-to-find-memory-leaks-in-your-rails-applications-470.html]
The link gives additional information on Bleakhouse profiling for memory leaks

''ruby-debug:''
Other than the extensive use of breakpoints Rails provides little to streamline the debugging process. Ruby-debug provides Rails with a plug-in extending the functionality of Rails built in debugger.

[http://rubyforge.org/softwaremap/trove_list.php?form_cat=47]
The link provides twenty additional debug resources available for RoR

== '''Conclusion''' ==

Rails is a very comprehensive development environment for Ruby with numerous extensions, plugins, and other resources outside of IDEs to strengthen the functionality of the open source web application framework.

== References ==

''All sources used to create this wiki are linked in the above text.''

CSC/ECE 517 Fall 2009/wiki1b team1

2009-09-28T19:50:32Z

Los Bravo: /* TDD: Test Driven Development */

CSC/ECE 517 Fall 2009

'''
== Resources for Rails (other than IDEs) ==
'''

IDEs are a valuable resource for Rails development, however there are many other resources and tools
that can either replace or supplement IDEs.

'''Resources for Rails other than IDEs
'''

'''''Rails API''''' - http://api.rubyonrails.org/

This site documents Rails files, classes and methods that can be used to build a Rails application.

'''''Rails Forum''''' - http://railsforum.com/

A discussion forum covering all aspects of Rails for beginners and experts including planning,
programming, extensions and production.

'''''Introducing Ruby on Rails'''''

Part 1 http://www.softwaredeveloper.com/features/intro-to-ruby-on-rails-042507/

Part 2 http://www.softwaredeveloper.com/features/intro-to-ruby-on-rails-part-two-043007/

An excellent introduction to Rails for novices

'''''Installers'''
''

Windows: InstantRails - http://instantrails.rubyforge.org/wiki/wiki.pl

An all in one, single click installer for Windows that includes a Rails server.

Mac: Locomotive - http://locomotive.raaum.org/

'''''Rails Projects''''' - http://www.workingwithrails.com/

A Database of Rails projects, programmers and websites

'''''Rails plugins''''' - http://agilewebdevelopment.com/

A collection of Rails open source plugins, searchable by category or keyword.

'''''Sample Rails''''' - http://snippets.dzone.com/tag/rails

A collection of Rails code snippets.

'''''Agile Rails book''''' - http://www.amazon.com/gp/product/097669400X/002-0481267-8083260?v=glance&n=283155

An excellent resource for learning how to apply Agile programming concepts to Rails.

'''''Rails cheatsheet''''' - http://www.blainekendall.com/uploads/RubyOnRails-Cheatsheet-BlaineKendall.pdf

One user's list of best practices, gotchas and quirks of developing with Rails.

'''''Rails best practices''''' - http://www.therailsway.com/

An official best practices list for programming in Rails.

'''''Advanced Rails''''' - http://webonrails.com/

A resource for the advanced Rails programmer.

'''''Rails Blog''''' - http://weblog.rubyonrails.org/

An online community of updates about current happenings with the Rails platform.

'''''Rails Guides''''' - http://guides.rubyonrails.org/

An all in one resource for learning Rails including Howtos, security and contributing to the Rails community.

'''''Authoring Rails plugins''''' - http://nubyonrails.com/articles/2006/05/04/the-complete-guide-to-rails-plugins-part-i

A complete guide to authoring your own Rails plugins.

'''

== '''Tools for Rails (other than IDEs)''' ==
'''

'''Test Unit'''
The Rails stack uses Test::Unit, known as the default Ruby unit testing framework shipping with Ruby. There are various plugins and extension that could be used with Rails built-in Test::Unit to extend its functionality for support of TDD and BDD testing practices.

[http://wiki.rubyonrails.org/addons/testing]
The link provides additional information in the form of supporting resources, whitepapers, examples, and plug-in documentation

'''Example'''
[http://wiki.rubyonrails.org/testing/test-unitrequire]

Image:class CalculatorTest < Test::Unit::TestCase
def test_add_two_numbers_for_the_sum
calculator = Calculator.new
assert_equal 4, calculator.sum(2, 2)
end
end

== TDD: Test Driven Development ==

Test Driven Development is a combination of refactoring and test first development, a form of development where the test is

written prior to completed production code. The goal of TDD is the specification of requirements and not the validation of

requirements. There are a few testing frameworks that are used to implement the TDD programming technique.

[http://ruby.about.com/b/2009/01/28/test-driven-development-with-rails.htm]
This link provides a comprehensive overview of test driven development practices and available resources for implementation.

'''RSpec'''
RSpec is a testing framework for Behavior Driven Development, complete with its own expectations, matchers and mocking and

stubbing facilities. It goes along hand in hand with Cucumber, though it plays nicely with many other testing frameworks as well.

Example expresses some basic desired behavior

bowling_spec.rb

require ‘bowling’

describe Bowling do

it "should score 0 for gutter game" do

bowling = Bowling.new

20.times { bowling.hit(0) }

bowling.score.should == 0

end

end
'''Model Examples'''
These are the equivalent of unit tests in Rails’ built in testing. Ironically
(for the traditional TDD’er) these are the only specs that we feel should actually interact
with the database.

'''Controller Examples'''
These align somewhat with functional tests in rails, except
that they do not actually render views (though you can force rendering of views
if you prefer). Instead of setting expectations about what goes on a page, you
set expectations about what templates get rendered.

'''View Examples'''
This is the other half of Rails’ functional testing. View specs allow
you to set up assigns (thanks to ZenTest).

'''Helper Examples'''
let you specify directly methods that live in your helpers.

[http://www.ibm.com/developerworks/web/library/wa-rspec/]
The link provides a brief overview of RSpec with a comprehensive series of examples and a conceptual view of Rpecs step by step

implementation process

'''Cucumber'''
Cucumber is used with TDD and BDD within other testing frameworks such as RSpec by letting software development teams describe how

software should behave in plain text. The text is written in a business-readable domain-specific language and serves as

documentation, automated tests and development-aid - all rolled into one format.

[http://cukes.info/]
The link provides a detail decription, definition, and examples of Cucumber implementation best practices and supported

frameworks.

'''Cucumber Example:'''
Scenario: See all vendors
Given I am logged in as a user in the administrator role
And There are 3 vendors
When I go to the manage vendors page
Then I should see the first 3 vendor names

'''Shoulda'''
An extension to Test::Unit with additional helpers, macros, and assertions.

[http://www.thoughtbot.com/projects/shoulda]
The link provides a more conclusive definition of Shoulda along with installation facts and working examples of the Shoulda

testing framework within Ruby's built in Test::Unit

== BDD: Behavior Driven Development ==
[http://eggsonbread.com/2009/07/22/behavior-driven-development-in-a-nutshell/]
Behavior driven development was born from the concepts behind the implementation of TDD. It brings together strands from

TestDrivenDevelopment and DomainDrivenDesign into an integrated whole, making the relationship between these two powerful

approaches to software development more evident. Most test driven development testing frameworks such as RSpec and Cucumber also support behavior driven development testing.

[http://behaviour-driven.org/]
The link supports BDDs definition with additional links to more viable behavior driven development resources.

----

'''Other Test Tool Resources'''

''Watir:'' is an open-source library for automating web browsers. It allows you to write tests that are easy to read and maintain. It

is simple and flexible.
[http://wtr.rubyforge.org/]
The link provides an overview of Watir with installation specifications, examples, and supported platforms

''NullDB:'' [http://avdi.org/projects/nulldb/]
a way to speed up testing by avoiding database use.

''Bleakhouse:'' memory leak detection
[http://www.rubyinside.com/bleakhouse-tool-to-find-memory-leaks-in-your-rails-applications-470.html]
The link gives additional information on Bleakhouse profiling for memory leaks

''ruby-debug:''
Other than the extensive use of breakpoints Rails provides little to streamline the debugging process. Ruby-debug provides Rails with a plug-in extending the functionality of Rails built in debugger.

[http://rubyforge.org/softwaremap/trove_list.php?form_cat=47]
The link provides twenty additional debug resources available for RoR

== '''Conclusion''' ==

Rails is a very comprehensive development environment for Ruby with numerous extensions, plugins, and other resources outside of IDEs to strengthen the functionality of the open source web application framework.

== References ==

''All sources used to create this wiki are linked in the above text.''

CSC/ECE 517 Fall 2009/wiki1b team1

2009-09-28T19:49:47Z

Los Bravo: /* TDD: Test Driven Development */

CSC/ECE 517 Fall 2009

'''
== Resources for Rails (other than IDEs) ==
'''

IDEs are a valuable resource for Rails development, however there are many other resources and tools
that can either replace or supplement IDEs.

'''Resources for Rails other than IDEs
'''

'''''Rails API''''' - http://api.rubyonrails.org/

This site documents Rails files, classes and methods that can be used to build a Rails application.

'''''Rails Forum''''' - http://railsforum.com/

A discussion forum covering all aspects of Rails for beginners and experts including planning,
programming, extensions and production.

'''''Introducing Ruby on Rails'''''

Part 1 http://www.softwaredeveloper.com/features/intro-to-ruby-on-rails-042507/

Part 2 http://www.softwaredeveloper.com/features/intro-to-ruby-on-rails-part-two-043007/

An excellent introduction to Rails for novices

'''''Installers'''
''

Windows: InstantRails - http://instantrails.rubyforge.org/wiki/wiki.pl

An all in one, single click installer for Windows that includes a Rails server.

Mac: Locomotive - http://locomotive.raaum.org/

'''''Rails Projects''''' - http://www.workingwithrails.com/

A Database of Rails projects, programmers and websites

'''''Rails plugins''''' - http://agilewebdevelopment.com/

A collection of Rails open source plugins, searchable by category or keyword.

'''''Sample Rails''''' - http://snippets.dzone.com/tag/rails

A collection of Rails code snippets.

'''''Agile Rails book''''' - http://www.amazon.com/gp/product/097669400X/002-0481267-8083260?v=glance&n=283155

An excellent resource for learning how to apply Agile programming concepts to Rails.

'''''Rails cheatsheet''''' - http://www.blainekendall.com/uploads/RubyOnRails-Cheatsheet-BlaineKendall.pdf

One user's list of best practices, gotchas and quirks of developing with Rails.

'''''Rails best practices''''' - http://www.therailsway.com/

An official best practices list for programming in Rails.

'''''Advanced Rails''''' - http://webonrails.com/

A resource for the advanced Rails programmer.

'''''Rails Blog''''' - http://weblog.rubyonrails.org/

An online community of updates about current happenings with the Rails platform.

'''''Rails Guides''''' - http://guides.rubyonrails.org/

An all in one resource for learning Rails including Howtos, security and contributing to the Rails community.

'''''Authoring Rails plugins''''' - http://nubyonrails.com/articles/2006/05/04/the-complete-guide-to-rails-plugins-part-i

A complete guide to authoring your own Rails plugins.

'''

== '''Tools for Rails (other than IDEs)''' ==
'''

'''Test Unit'''
The Rails stack uses Test::Unit, known as the default Ruby unit testing framework shipping with Ruby. There are various plugins and extension that could be used with Rails built-in Test::Unit to extend its functionality for support of TDD and BDD testing practices.

[http://wiki.rubyonrails.org/addons/testing]
The link provides additional information in the form of supporting resources, whitepapers, examples, and plug-in documentation

'''Example'''
[http://wiki.rubyonrails.org/testing/test-unitrequire]

Image:class CalculatorTest < Test::Unit::TestCase
def test_add_two_numbers_for_the_sum
calculator = Calculator.new
assert_equal 4, calculator.sum(2, 2)
end
end

== TDD: Test Driven Development ==

Test Driven Development is a combination of refactoring and test first development, a form of development where the test is

written prior to completed production code. The goal of TDD is the specification of requirements and not the validation of

requirements. There are a few testing frameworks that are used to implement the TDD programming technique.

[http://ruby.about.com/b/2009/01/28/test-driven-development-with-rails.htm]
This link provides a comprehensive overview of test driven development practices and available resources for implementation.

'''RSpec'''
RSpec is a testing framework for Behavior Driven Development, complete with its own expectations, matchers and mocking and

stubbing facilities. It goes along hand in hand with Cucumber, though it plays nicely with many other testing frameworks as well.

Example expresses some basic desired behavior

# bowling_spec.rb

require ‘bowling’

describe Bowling do

it "should score 0 for gutter game" do

bowling = Bowling.new

20.times { bowling.hit(0) }

bowling.score.should == 0

end

end
'''Model Examples'''
These are the equivalent of unit tests in Rails’ built in testing. Ironically
(for the traditional TDD’er) these are the only specs that we feel should actually interact
with the database.

'''Controller Examples'''
These align somewhat with functional tests in rails, except
that they do not actually render views (though you can force rendering of views
if you prefer). Instead of setting expectations about what goes on a page, you
set expectations about what templates get rendered.

'''View Examples'''
This is the other half of Rails’ functional testing. View specs allow
you to set up assigns (thanks to ZenTest).

'''Helper Examples'''
let you specify directly methods that live in your helpers.

[http://www.ibm.com/developerworks/web/library/wa-rspec/]
The link provides a brief overview of RSpec with a comprehensive series of examples and a conceptual view of Rpecs step by step

implementation process

'''Cucumber'''
Cucumber is used with TDD and BDD within other testing frameworks such as RSpec by letting software development teams describe how

software should behave in plain text. The text is written in a business-readable domain-specific language and serves as

documentation, automated tests and development-aid - all rolled into one format.

[http://cukes.info/]
The link provides a detail decription, definition, and examples of Cucumber implementation best practices and supported

frameworks.

'''Cucumber Example:'''
Scenario: See all vendors
Given I am logged in as a user in the administrator role
And There are 3 vendors
When I go to the manage vendors page
Then I should see the first 3 vendor names

'''Shoulda'''
An extension to Test::Unit with additional helpers, macros, and assertions.

[http://www.thoughtbot.com/projects/shoulda]
The link provides a more conclusive definition of Shoulda along with installation facts and working examples of the Shoulda

testing framework within Ruby's built in Test::Unit

== BDD: Behavior Driven Development ==
[http://eggsonbread.com/2009/07/22/behavior-driven-development-in-a-nutshell/]
Behavior driven development was born from the concepts behind the implementation of TDD. It brings together strands from

TestDrivenDevelopment and DomainDrivenDesign into an integrated whole, making the relationship between these two powerful

approaches to software development more evident. Most test driven development testing frameworks such as RSpec and Cucumber also support behavior driven development testing.

[http://behaviour-driven.org/]
The link supports BDDs definition with additional links to more viable behavior driven development resources.

----

'''Other Test Tool Resources'''

''Watir:'' is an open-source library for automating web browsers. It allows you to write tests that are easy to read and maintain. It

is simple and flexible.
[http://wtr.rubyforge.org/]
The link provides an overview of Watir with installation specifications, examples, and supported platforms

''NullDB:'' [http://avdi.org/projects/nulldb/]
a way to speed up testing by avoiding database use.

''Bleakhouse:'' memory leak detection
[http://www.rubyinside.com/bleakhouse-tool-to-find-memory-leaks-in-your-rails-applications-470.html]
The link gives additional information on Bleakhouse profiling for memory leaks

''ruby-debug:''
Other than the extensive use of breakpoints Rails provides little to streamline the debugging process. Ruby-debug provides Rails with a plug-in extending the functionality of Rails built in debugger.

[http://rubyforge.org/softwaremap/trove_list.php?form_cat=47]
The link provides twenty additional debug resources available for RoR

== '''Conclusion''' ==

Rails is a very comprehensive development environment for Ruby with numerous extensions, plugins, and other resources outside of IDEs to strengthen the functionality of the open source web application framework.

== References ==

''All sources used to create this wiki are linked in the above text.''

CSC/ECE 517 Fall 2009/wiki1b team1

2009-09-28T19:00:07Z

Los Bravo: /* TDD: Test Driven Development */

CSC/ECE 517 Fall 2009

'''
== Resources for Rails (other than IDEs) ==
'''

IDEs are a valuable resource for Rails development, however there are many other resources and tools
that can either replace or supplement IDEs.

'''Resources for Rails other than IDEs
'''

'''''Rails API''''' - http://api.rubyonrails.org/

This site documents Rails files, classes and methods that can be used to build a Rails application.

'''''Rails Forum''''' - http://railsforum.com/

A discussion forum covering all aspects of Rails for beginners and experts including planning,
programming, extensions and production.

'''''Introducing Ruby on Rails'''''

Part 1 http://www.softwaredeveloper.com/features/intro-to-ruby-on-rails-042507/

Part 2 http://www.softwaredeveloper.com/features/intro-to-ruby-on-rails-part-two-043007/

An excellent introduction to Rails for novices

'''''Installers'''
''

Windows: InstantRails - http://instantrails.rubyforge.org/wiki/wiki.pl

An all in one, single click installer for Windows that includes a Rails server.

Mac: Locomotive - http://locomotive.raaum.org/

'''''Rails Projects''''' - http://www.workingwithrails.com/

A Database of Rails projects, programmers and websites

'''''Rails plugins''''' - http://agilewebdevelopment.com/

A collection of Rails open source plugins, searchable by category or keyword.

'''''Sample Rails''''' - http://snippets.dzone.com/tag/rails

A collection of Rails code snippets.

'''''Agile Rails book''''' - http://www.amazon.com/gp/product/097669400X/002-0481267-8083260?v=glance&n=283155

An excellent resource for learning how to apply Agile programming concepts to Rails.

'''''Rails cheatsheet''''' - http://www.blainekendall.com/uploads/RubyOnRails-Cheatsheet-BlaineKendall.pdf

One user's list of best practices, gotchas and quirks of developing with Rails.

'''''Rails best practices''''' - http://www.therailsway.com/

An official best practices list for programming in Rails.

'''''Advanced Rails''''' - http://webonrails.com/

A resource for the advanced Rails programmer.

'''''Rails Blog''''' - http://weblog.rubyonrails.org/

An online community of updates about current happenings with the Rails platform.

'''''Rails Guides''''' - http://guides.rubyonrails.org/

An all in one resource for learning Rails including Howtos, security and contributing to the Rails community.

'''''Authoring Rails plugins''''' - http://nubyonrails.com/articles/2006/05/04/the-complete-guide-to-rails-plugins-part-i

A complete guide to authoring your own Rails plugins.

'''

== '''Tools for Rails (other than IDEs)''' ==
'''

'''Test Unit'''
The Rails stack uses Test::Unit, known as the default Ruby unit testing framework shipping with Ruby. There are various plugins and extension that could be used with Rails built-in Test::Unit to extend its functionality for support of TDD and BDD testing practices.

[http://wiki.rubyonrails.org/addons/testing]
The link provides additional information in the form of supporting resources, whitepapers, examples, and plug-in documentation

'''Example'''
[http://wiki.rubyonrails.org/testing/test-unitrequire]

Image:class CalculatorTest < Test::Unit::TestCase
def test_add_two_numbers_for_the_sum
calculator = Calculator.new
assert_equal 4, calculator.sum(2, 2)
end
end

== TDD: Test Driven Development ==

Test Driven Development is a combination of refactoring and test first development, a form of development where the test is

written prior to completed production code. The goal of TDD is the specification of requirements and not the validation of

requirements. There are a few testing frameworks that are used to implement the TDD programming technique.

[http://ruby.about.com/b/2009/01/28/test-driven-development-with-rails.htm]
This link provides a comprehensive overview of test driven development practices and available resources for implementation.

'''RSpec'''
RSpec is a testing framework for Behavior Driven Development, complete with its own expectations, matchers and mocking and

stubbing facilities. It goes along hand in hand with Cucumber, though it plays nicely with many other testing frameworks as well.

'''Model Examples'''
These are the equivalent of unit tests in Rails’ built in testing. Ironically
(for the traditional TDD’er) these are the only specs that we feel should actually interact
with the database.

'''Controller Examples'''
These align somewhat with functional tests in rails, except
that they do not actually render views (though you can force rendering of views
if you prefer). Instead of setting expectations about what goes on a page, you
set expectations about what templates get rendered.

'''View Examples'''
This is the other half of Rails’ functional testing. View specs allow
you to set up assigns (thanks to ZenTest).

'''Helper Examples'''
let you specify directly methods that live in your helpers.

[http://www.ibm.com/developerworks/web/library/wa-rspec/]
The link provides a brief overview of RSpec with a comprehensive series of examples and a conceptual view of Rpecs step by step

implementation process

'''Cucumber'''
Cucumber is used with TDD and BDD within other testing frameworks such as RSpec by letting software development teams describe how

software should behave in plain text. The text is written in a business-readable domain-specific language and serves as

documentation, automated tests and development-aid - all rolled into one format.

[http://cukes.info/]
The link provides a detail decription, definition, and examples of Cucumber implementation best practices and supported

frameworks.

'''Cucumber Example:'''
Scenario: See all vendors
Given I am logged in as a user in the administrator role
And There are 3 vendors
When I go to the manage vendors page
Then I should see the first 3 vendor names

'''Shoulda'''
An extension to Test::Unit with additional helpers, macros, and assertions.

[http://www.thoughtbot.com/projects/shoulda]
The link provides a more conclusive definition of Shoulda along with installation facts and working examples of the Shoulda

testing framework within Ruby's built in Test::Unit

== BDD: Behavior Driven Development ==
[http://eggsonbread.com/2009/07/22/behavior-driven-development-in-a-nutshell/]
Behavior driven development was born from the concepts behind the implementation of TDD. It brings together strands from

TestDrivenDevelopment and DomainDrivenDesign into an integrated whole, making the relationship between these two powerful

approaches to software development more evident. Most test driven development testing frameworks such as RSpec and Cucumber also support behavior driven development testing.

[http://behaviour-driven.org/]
The link supports BDDs definition with additional links to more viable behavior driven development resources.

----

'''Other Test Tool Resources'''

''Watir:'' is an open-source library for automating web browsers. It allows you to write tests that are easy to read and maintain. It

is simple and flexible.
[http://wtr.rubyforge.org/]
The link provides an overview of Watir with installation specifications, examples, and supported platforms

''NullDB:'' [http://avdi.org/projects/nulldb/]
a way to speed up testing by avoiding database use.

''Bleakhouse:'' memory leak detection
[http://www.rubyinside.com/bleakhouse-tool-to-find-memory-leaks-in-your-rails-applications-470.html]
The link gives additional information on Bleakhouse profiling for memory leaks

''ruby-debug:''
Other than the extensive use of breakpoints Rails provides little to streamline the debugging process. Ruby-debug provides Rails with a plug-in extending the functionality of Rails built in debugger.

[http://rubyforge.org/softwaremap/trove_list.php?form_cat=47]
The link provides twenty additional debug resources available for RoR

== '''Conclusion''' ==

Rails is a very comprehensive development environment for Ruby with numerous extensions, plugins, and other resources outside of IDEs to strengthen the functionality of the open source web application framework.

== References ==

''All sources used to create this wiki are linked in the above text.''

CSC/ECE 517 Fall 2009/wiki1b team1

2009-09-28T18:59:32Z

Los Bravo: /* TDD: Test Driven Development */

CSC/ECE 517 Fall 2009

'''
== Resources for Rails (other than IDEs) ==
'''

IDEs are a valuable resource for Rails development, however there are many other resources and tools
that can either replace or supplement IDEs.

'''Resources for Rails other than IDEs
'''

'''''Rails API''''' - http://api.rubyonrails.org/

This site documents Rails files, classes and methods that can be used to build a Rails application.

'''''Rails Forum''''' - http://railsforum.com/

A discussion forum covering all aspects of Rails for beginners and experts including planning,
programming, extensions and production.

'''''Introducing Ruby on Rails'''''

Part 1 http://www.softwaredeveloper.com/features/intro-to-ruby-on-rails-042507/

Part 2 http://www.softwaredeveloper.com/features/intro-to-ruby-on-rails-part-two-043007/

An excellent introduction to Rails for novices

'''''Installers'''
''

Windows: InstantRails - http://instantrails.rubyforge.org/wiki/wiki.pl

An all in one, single click installer for Windows that includes a Rails server.

Mac: Locomotive - http://locomotive.raaum.org/

'''''Rails Projects''''' - http://www.workingwithrails.com/

A Database of Rails projects, programmers and websites

'''''Rails plugins''''' - http://agilewebdevelopment.com/

A collection of Rails open source plugins, searchable by category or keyword.

'''''Sample Rails''''' - http://snippets.dzone.com/tag/rails

A collection of Rails code snippets.

'''''Agile Rails book''''' - http://www.amazon.com/gp/product/097669400X/002-0481267-8083260?v=glance&n=283155

An excellent resource for learning how to apply Agile programming concepts to Rails.

'''''Rails cheatsheet''''' - http://www.blainekendall.com/uploads/RubyOnRails-Cheatsheet-BlaineKendall.pdf

One user's list of best practices, gotchas and quirks of developing with Rails.

'''''Rails best practices''''' - http://www.therailsway.com/

An official best practices list for programming in Rails.

'''''Advanced Rails''''' - http://webonrails.com/

A resource for the advanced Rails programmer.

'''''Rails Blog''''' - http://weblog.rubyonrails.org/

An online community of updates about current happenings with the Rails platform.

'''''Rails Guides''''' - http://guides.rubyonrails.org/

An all in one resource for learning Rails including Howtos, security and contributing to the Rails community.

'''''Authoring Rails plugins''''' - http://nubyonrails.com/articles/2006/05/04/the-complete-guide-to-rails-plugins-part-i

A complete guide to authoring your own Rails plugins.

'''

== '''Tools for Rails (other than IDEs)''' ==
'''

'''Test Unit'''
The Rails stack uses Test::Unit, known as the default Ruby unit testing framework shipping with Ruby. There are various plugins and extension that could be used with Rails built-in Test::Unit to extend its functionality for support of TDD and BDD testing practices.

[http://wiki.rubyonrails.org/addons/testing]
The link provides additional information in the form of supporting resources, whitepapers, examples, and plug-in documentation

'''Example'''
[http://wiki.rubyonrails.org/testing/test-unitrequire]

Image:class CalculatorTest < Test::Unit::TestCase
def test_add_two_numbers_for_the_sum
calculator = Calculator.new
assert_equal 4, calculator.sum(2, 2)
end
end

== TDD: Test Driven Development ==

Test Driven Development is a combination of refactoring and test first development, a form of development where the test is

written prior to completed production code. The goal of TDD is the specification of requirements and not the validation of

requirements. There are a few testing frameworks that are used to implement the TDD programming technique.

[http://ruby.about.com/b/2009/01/28/test-driven-development-with-rails.htm]
This link provides a comprehensive overview of test driven development practices and available resources for implementation.

'''RSpec'''
RSpec is a testing framework for Behavior Driven Development, complete with its own expectations, matchers and mocking and

stubbing facilities. It goes along hand in hand with Cucumber, though it plays nicely with many other testing frameworks as well.

'''Model Examples'''
These are the equivalent of unit tests in Rails’ built in testing. Ironically
(for the traditional TDD’er) these are the only specs that we feel should actually interact
with the database. Learn more ….

'''Controller Examples'''
These align somewhat with functional tests in rails, except
that they do not actually render views (though you can force rendering of views
if you prefer). Instead of setting expectations about what goes on a page, you
set expectations about what templates get rendered. Learn more….

'''View Examples'''
This is the other half of Rails’ functional testing. View specs allow
you to set up assigns (thanks to ZenTest).

'''Helper Examples'''
let you specify directly methods that live in your helpers.

[http://www.ibm.com/developerworks/web/library/wa-rspec/]
The link provides a brief overview of RSpec with a comprehensive series of examples and a conceptual view of Rpecs step by step

implementation process

'''Cucumber'''
Cucumber is used with TDD and BDD within other testing frameworks such as RSpec by letting software development teams describe how

software should behave in plain text. The text is written in a business-readable domain-specific language and serves as

documentation, automated tests and development-aid - all rolled into one format.

[http://cukes.info/]
The link provides a detail decription, definition, and examples of Cucumber implementation best practices and supported

frameworks.

'''Cucumber Example:'''
Scenario: See all vendors
Given I am logged in as a user in the administrator role
And There are 3 vendors
When I go to the manage vendors page
Then I should see the first 3 vendor names

'''Shoulda'''
An extension to Test::Unit with additional helpers, macros, and assertions.

[http://www.thoughtbot.com/projects/shoulda]
The link provides a more conclusive definition of Shoulda along with installation facts and working examples of the Shoulda

testing framework within Ruby's built in Test::Unit

== BDD: Behavior Driven Development ==
[http://eggsonbread.com/2009/07/22/behavior-driven-development-in-a-nutshell/]
Behavior driven development was born from the concepts behind the implementation of TDD. It brings together strands from

TestDrivenDevelopment and DomainDrivenDesign into an integrated whole, making the relationship between these two powerful

approaches to software development more evident. Most test driven development testing frameworks such as RSpec and Cucumber also support behavior driven development testing.

[http://behaviour-driven.org/]
The link supports BDDs definition with additional links to more viable behavior driven development resources.

----

'''Other Test Tool Resources'''

''Watir:'' is an open-source library for automating web browsers. It allows you to write tests that are easy to read and maintain. It

is simple and flexible.
[http://wtr.rubyforge.org/]
The link provides an overview of Watir with installation specifications, examples, and supported platforms

''NullDB:'' [http://avdi.org/projects/nulldb/]
a way to speed up testing by avoiding database use.

''Bleakhouse:'' memory leak detection
[http://www.rubyinside.com/bleakhouse-tool-to-find-memory-leaks-in-your-rails-applications-470.html]
The link gives additional information on Bleakhouse profiling for memory leaks

''ruby-debug:''
Other than the extensive use of breakpoints Rails provides little to streamline the debugging process. Ruby-debug provides Rails with a plug-in extending the functionality of Rails built in debugger.

[http://rubyforge.org/softwaremap/trove_list.php?form_cat=47]
The link provides twenty additional debug resources available for RoR

== '''Conclusion''' ==

Rails is a very comprehensive development environment for Ruby with numerous extensions, plugins, and other resources outside of IDEs to strengthen the functionality of the open source web application framework.

== References ==

''All sources used to create this wiki are linked in the above text.''

CSC/ECE 517 Fall 2009/wiki1b team1

2009-09-22T01:28:42Z

Los Bravo: /* Reference */

CSC/ECE 517 Fall 2009

'''
== Resources for Rails (other than IDEs) ==
'''

IDEs are a valuable resource for Rails development, however there are many other resources and tools
that can either replace or supplement IDEs.

'''Resources for Rails other than IDEs
'''

'''''Rails API''''' - http://api.rubyonrails.org/

This site documents Rails files, classes and methods that can be used to build a Rails application.

'''''Rails Forum''''' - http://railsforum.com/

A discussion forum covering all aspects of Rails for beginners and experts including planning,
programming, extensions and production.

'''''Introducing Ruby on Rails'''''

Part 1 http://www.softwaredeveloper.com/features/intro-to-ruby-on-rails-042507/

Part 2 http://www.softwaredeveloper.com/features/intro-to-ruby-on-rails-part-two-043007/

An excellent introduction to Rails for novices

'''''Installers'''
''

Windows: InstantRails - http://instantrails.rubyforge.org/wiki/wiki.pl

An all in one, single click installer for Windows that includes a Rails server.

Mac: Locomotive - http://locomotive.raaum.org/

'''''Rails Projects''''' - http://www.workingwithrails.com/

A Database of Rails projects, programmers and websites

'''''Rails plugins''''' - http://agilewebdevelopment.com/

A collection of Rails open source plugins, searchable by category or keyword.

'''''Sample Rails''''' - http://snippets.dzone.com/tag/rails

A collection of Rails code snippets.

'''''Agile Rails book''''' - http://www.amazon.com/gp/product/097669400X/002-0481267-8083260?v=glance&n=283155

An excellent resource for learning how to apply Agile programming concepts to Rails.

'''''Rails cheatsheet''''' - http://www.blainekendall.com/uploads/RubyOnRails-Cheatsheet-BlaineKendall.pdf

One user's list of best practices, gotchas and quirks of developing with Rails.

'''''Rails best practices''''' - http://www.therailsway.com/

An official best practices list for programming in Rails.

'''''Advanced Rails''''' - http://webonrails.com/

A resource for the advanced Rails programmer.

'''''Rails Blog''''' - http://weblog.rubyonrails.org/

An online community of updates about current happenings with the Rails platform.

'''''Rails Guides''''' - http://guides.rubyonrails.org/

An all in one resource for learning Rails including Howtos, security and contributing to the Rails community.

'''''Authoring Rails plugins''''' - http://nubyonrails.com/articles/2006/05/04/the-complete-guide-to-rails-plugins-part-i

A complete guide to authoring your own Rails plugins.

'''

== '''Tools for Rails (other than IDEs)''' ==
'''

'''Test Unit'''
The Rails stack uses Test::Unit, known as the default Ruby unit testing framework shipping with Ruby. There are various plugins and extension that could be used with Rails built-in Test::Unit to extend its functionality for support of TDD and BDD testing practices.

[http://wiki.rubyonrails.org/addons/testing]
The link provides additional information in the form of supporting resources, whitepapers, examples, and plug-in documentation

'''Example'''
[http://wiki.rubyonrails.org/testing/test-unitrequire]

Image:class CalculatorTest < Test::Unit::TestCase
def test_add_two_numbers_for_the_sum
calculator = Calculator.new
assert_equal 4, calculator.sum(2, 2)
end
end

== TDD: Test Driven Development ==

Test Driven Development is a combination of refactoring and test first development, a form of development where the test is

written prior to completed production code. The goal of TDD is the specification of requirements and not the validation of

requirements. There are a few testing frameworks that are used to implement the TDD programming technique.

[http://ruby.about.com/b/2009/01/28/test-driven-development-with-rails.htm]
This link provides a comprehensive overview of test driven development practices and available resources for implementation.

'''RSpec'''
RSpec is a testing framework for Behavior Driven Development, complete with its own expectations, matchers and mocking and

stubbing facilities. It goes along hand in hand with Cucumber, though it plays nicely with many other testing frameworks as well.

'''Model Examples'''
These are the equivalent of unit tests in Rails’ built in testing. Ironically
(for the traditional TDD’er) these are the only specs that we feel should actually interact
with the database. Learn more ….

'''Controller Examples'''
These align somewhat with functional tests in rails, except
that they do not actually render views (though you can force rendering of views
if you prefer). Instead of setting expectations about what goes on a page, you
set expectations about what templates get rendered. Learn more….

'''View Examples'''
This is the other half of Rails’ functional testing. View specs allow
you to set up assigns (thanks to ZenTest). Learn more ….

'''Helper Examples'''
let you specify directly methods that live in your helpers. Learn more ….

[http://www.ibm.com/developerworks/web/library/wa-rspec/]
The link provides a brief overview of RSpec with a comprehensive series of examples and a conceptual view of Rpecs step by step

implementation process

'''Cucumber'''
Cucumber is used with TDD and BDD within other testing frameworks such as RSpec by letting software development teams describe how

software should behave in plain text. The text is written in a business-readable domain-specific language and serves as

documentation, automated tests and development-aid - all rolled into one format.

[http://cukes.info/]
The link provides a detail decription, definition, and examples of Cucumber implementation best practices and supported

frameworks.

'''Cucumber Example:'''
Scenario: See all vendors
Given I am logged in as a user in the administrator role
And There are 3 vendors
When I go to the manage vendors page
Then I should see the first 3 vendor names

'''Shoulda'''
An extension to Test::Unit with additional helpers, macros, and assertions.

[http://www.thoughtbot.com/projects/shoulda]
The link provides a more conclusive definition of Shoulda along with installation facts and working examples of the Shoulda

testing framework within Ruby's built in Test::Unit

== BDD: Behavior Driven Development ==
[http://eggsonbread.com/2009/07/22/behavior-driven-development-in-a-nutshell/]
Behavior driven development was born from the concepts behind the implementation of TDD. It brings together strands from

TestDrivenDevelopment and DomainDrivenDesign into an integrated whole, making the relationship between these two powerful

approaches to software development more evident. Most test driven development testing frameworks such as RSpec and Cucumber also support behavior driven development testing.

[http://behaviour-driven.org/]
The link supports BDDs definition with additional links to more viable behavior driven development resources.

----

'''Other Test Tool Resources'''

''Watir:'' is an open-source library for automating web browsers. It allows you to write tests that are easy to read and maintain. It

is simple and flexible.
[http://wtr.rubyforge.org/]
The link provides an overview of Watir with installation specifications, examples, and supported platforms

''NullDB:'' [http://avdi.org/projects/nulldb/]
a way to speed up testing by avoiding database use.

''Bleakhouse:'' memory leak detection
[http://www.rubyinside.com/bleakhouse-tool-to-find-memory-leaks-in-your-rails-applications-470.html]
The link gives additional information on Bleakhouse profiling for memory leaks

''ruby-debug:''
Other than the extensive use of breakpoints Rails provides little to streamline the debugging process. Ruby-debug provides Rails with a plug-in extending the functionality of Rails built in debugger.

[http://rubyforge.org/softwaremap/trove_list.php?form_cat=47]
The link provides twenty additional debug resources available for RoR

== '''Conclusion''' ==

Rails is a very comprehensive development environment for Ruby with numerous extensions, plugins, and other resources outside of IDEs to strengthen the functionality of the open source web application framework.

== References ==

''All sources used to create this wiki are linked in the above text.''

CSC/ECE 517 Fall 2009/wiki1b team1

2009-09-21T02:55:36Z

Los Bravo: /* BDD: Behavior Driven Development */

CSC/ECE 517 Fall 2009

'''
== Resources for Rails (other than IDEs) ==
'''

IDEs are a valuable resource for Rails development, however there are many other resources and tools
that can either replace or supplement IDEs.

'''Resources for Rails other than IDEs
'''

'''''Rails API''''' - http://api.rubyonrails.org/

This site documents Rails files, classes and methods that can be used to build a Rails application.

'''''Rails Forum''''' - http://railsforum.com/

A discussion forum covering all aspects of Rails for beginners and experts including planning,
programming, extensions and production.

'''''Introducing Ruby on Rails'''''

Part 1 http://www.softwaredeveloper.com/features/intro-to-ruby-on-rails-042507/

Part 2 http://www.softwaredeveloper.com/features/intro-to-ruby-on-rails-part-two-043007/

An excellent introduction to Rails for novices

'''''Installers'''
''

Windows: InstantRails - http://instantrails.rubyforge.org/wiki/wiki.pl

An all in one, single click installer for Windows that includes a Rails server.

Mac: Locomotive - http://locomotive.raaum.org/

'''''Rails Projects''''' - http://www.workingwithrails.com/

A Database of Rails projects, programmers and websites

'''''Rails plugins''''' - http://agilewebdevelopment.com/

A collection of Rails open source plugins, searchable by category or keyword.

'''''Sample Rails''''' - http://snippets.dzone.com/tag/rails

A collection of Rails code snippets.

'''''Agile Rails book''''' - http://www.amazon.com/gp/product/097669400X/002-0481267-8083260?v=glance&n=283155

An excellent resource for learning how to apply Agile programming concepts to Rails.

'''''Rails cheatsheet''''' - http://www.blainekendall.com/uploads/RubyOnRails-Cheatsheet-BlaineKendall.pdf

One user's list of best practices, gotchas and quirks of developing with Rails.

'''''Rails best practices''''' - http://www.therailsway.com/

An official best practices list for programming in Rails.

'''''Advanced Rails''''' - http://webonrails.com/

A resource for the advanced Rails programmer.

'''''Rails Blog''''' - http://weblog.rubyonrails.org/

An online community of updates about current happenings with the Rails platform.

'''''Rails Guides''''' - http://guides.rubyonrails.org/

An all in one resource for learning Rails including Howtos, security and contributing to the Rails community.

'''''Authoring Rails plugins''''' - http://nubyonrails.com/articles/2006/05/04/the-complete-guide-to-rails-plugins-part-i

A complete guide to authoring your own Rails plugins.

'''

== '''Tools for Rails (other than IDEs)''' ==
'''

'''Test Unit'''
The Rails stack uses Test::Unit, known as the default Ruby unit testing framework shipping with Ruby. There are various plugins and extension that could be used with Rails built-in Test::Unit to extend its functionality for support of TDD and BDD testing practices.

[http://wiki.rubyonrails.org/addons/testing]
The link provides additional information in the form of supporting resources, whitepapers, examples, and plug-in documentation

'''Example'''
[http://wiki.rubyonrails.org/testing/test-unitrequire]

Image:class CalculatorTest < Test::Unit::TestCase
def test_add_two_numbers_for_the_sum
calculator = Calculator.new
assert_equal 4, calculator.sum(2, 2)
end
end

== TDD: Test Driven Development ==

Test Driven Development is a combination of refactoring and test first development, a form of development where the test is

written prior to completed production code. The goal of TDD is the specification of requirements and not the validation of

requirements. There are a few testing frameworks that are used to implement the TDD programming technique.

[http://ruby.about.com/b/2009/01/28/test-driven-development-with-rails.htm]
This link provides a comprehensive overview of test driven development practices and available resources for implementation.

'''RSpec'''
RSpec is a testing framework for Behavior Driven Development, complete with its own expectations, matchers and mocking and

stubbing facilities. It goes along hand in hand with Cucumber, though it plays nicely with many other testing frameworks as well.

'''Model Examples'''
These are the equivalent of unit tests in Rails’ built in testing. Ironically
(for the traditional TDD’er) these are the only specs that we feel should actually interact
with the database. Learn more ….

'''Controller Examples'''
These align somewhat with functional tests in rails, except
that they do not actually render views (though you can force rendering of views
if you prefer). Instead of setting expectations about what goes on a page, you
set expectations about what templates get rendered. Learn more….

'''View Examples'''
This is the other half of Rails’ functional testing. View specs allow
you to set up assigns (thanks to ZenTest). Learn more ….

'''Helper Examples'''
let you specify directly methods that live in your helpers. Learn more ….

[http://www.ibm.com/developerworks/web/library/wa-rspec/]
The link provides a brief overview of RSpec with a comprehensive series of examples and a conceptual view of Rpecs step by step

implementation process

'''Cucumber'''
Cucumber is used with TDD and BDD within other testing frameworks such as RSpec by letting software development teams describe how

software should behave in plain text. The text is written in a business-readable domain-specific language and serves as

documentation, automated tests and development-aid - all rolled into one format.

[http://cukes.info/]
The link provides a detail decription, definition, and examples of Cucumber implementation best practices and supported

frameworks.

'''Cucumber Example:'''
Scenario: See all vendors
Given I am logged in as a user in the administrator role
And There are 3 vendors
When I go to the manage vendors page
Then I should see the first 3 vendor names

'''Shoulda'''
An extension to Test::Unit with additional helpers, macros, and assertions.

[http://www.thoughtbot.com/projects/shoulda]
The link provides a more conclusive definition of Shoulda along with installation facts and working examples of the Shoulda

testing framework within Ruby's built in Test::Unit

== BDD: Behavior Driven Development ==
[http://eggsonbread.com/2009/07/22/behavior-driven-development-in-a-nutshell/]
Behavior driven development was born from the concepts behind the implementation of TDD. It brings together strands from

TestDrivenDevelopment and DomainDrivenDesign into an integrated whole, making the relationship between these two powerful

approaches to software development more evident. Most test driven development testing frameworks such as RSpec and Cucumber also support behavior driven development testing.

[http://behaviour-driven.org/]
The link supports BDDs definition with additional links to more viable behavior driven development resources.

----

'''Other Test Tool Resources'''

''Watir:'' is an open-source library for automating web browsers. It allows you to write tests that are easy to read and maintain. It

is simple and flexible.
[http://wtr.rubyforge.org/]
The link provides an overview of Watir with installation specifications, examples, and supported platforms

''NullDB:'' [http://avdi.org/projects/nulldb/]
a way to speed up testing by avoiding database use.

''Bleakhouse:'' memory leak detection
[http://www.rubyinside.com/bleakhouse-tool-to-find-memory-leaks-in-your-rails-applications-470.html]
The link gives additional information on Bleakhouse profiling for memory leaks

''ruby-debug:''
Other than the extensive use of breakpoints Rails provides little to streamline the debugging process. Ruby-debug provides Rails with a plug-in extending the functionality of Rails built in debugger.

[http://rubyforge.org/softwaremap/trove_list.php?form_cat=47]
The link provides twenty additional debug resources available for RoR

== '''Conclusion''' ==

Rails is a very comprehensive development environment for Ruby with numerous extensions, plugins, and other resources outside of IDEs to strengthen the functionality of the open source web application framework.

== Reference ==

''All sources used to create this wiki are linked in the above text.''

CSC/ECE 517 Fall 2009/wiki1b team1

2009-09-21T02:55:02Z

Los Bravo: /* BDD: Behavior Driven Development */

CSC/ECE 517 Fall 2009

'''
== Resources for Rails (other than IDEs) ==
'''

IDEs are a valuable resource for Rails development, however there are many other resources and tools
that can either replace or supplement IDEs.

'''Resources for Rails other than IDEs
'''

'''''Rails API''''' - http://api.rubyonrails.org/

This site documents Rails files, classes and methods that can be used to build a Rails application.

'''''Rails Forum''''' - http://railsforum.com/

A discussion forum covering all aspects of Rails for beginners and experts including planning,
programming, extensions and production.

'''''Introducing Ruby on Rails'''''

Part 1 http://www.softwaredeveloper.com/features/intro-to-ruby-on-rails-042507/

Part 2 http://www.softwaredeveloper.com/features/intro-to-ruby-on-rails-part-two-043007/

An excellent introduction to Rails for novices

'''''Installers'''
''

Windows: InstantRails - http://instantrails.rubyforge.org/wiki/wiki.pl

An all in one, single click installer for Windows that includes a Rails server.

Mac: Locomotive - http://locomotive.raaum.org/

'''''Rails Projects''''' - http://www.workingwithrails.com/

A Database of Rails projects, programmers and websites

'''''Rails plugins''''' - http://agilewebdevelopment.com/

A collection of Rails open source plugins, searchable by category or keyword.

'''''Sample Rails''''' - http://snippets.dzone.com/tag/rails

A collection of Rails code snippets.

'''''Agile Rails book''''' - http://www.amazon.com/gp/product/097669400X/002-0481267-8083260?v=glance&n=283155

An excellent resource for learning how to apply Agile programming concepts to Rails.

'''''Rails cheatsheet''''' - http://www.blainekendall.com/uploads/RubyOnRails-Cheatsheet-BlaineKendall.pdf

One user's list of best practices, gotchas and quirks of developing with Rails.

'''''Rails best practices''''' - http://www.therailsway.com/

An official best practices list for programming in Rails.

'''''Advanced Rails''''' - http://webonrails.com/

A resource for the advanced Rails programmer.

'''''Rails Blog''''' - http://weblog.rubyonrails.org/

An online community of updates about current happenings with the Rails platform.

'''''Rails Guides''''' - http://guides.rubyonrails.org/

An all in one resource for learning Rails including Howtos, security and contributing to the Rails community.

'''''Authoring Rails plugins''''' - http://nubyonrails.com/articles/2006/05/04/the-complete-guide-to-rails-plugins-part-i

A complete guide to authoring your own Rails plugins.

'''

== '''Tools for Rails (other than IDEs)''' ==
'''

'''Test Unit'''
The Rails stack uses Test::Unit, known as the default Ruby unit testing framework shipping with Ruby. There are various plugins and extension that could be used with Rails built-in Test::Unit to extend its functionality for support of TDD and BDD testing practices.

[http://wiki.rubyonrails.org/addons/testing]
The link provides additional information in the form of supporting resources, whitepapers, examples, and plug-in documentation

'''Example'''
[http://wiki.rubyonrails.org/testing/test-unitrequire]

Image:class CalculatorTest < Test::Unit::TestCase
def test_add_two_numbers_for_the_sum
calculator = Calculator.new
assert_equal 4, calculator.sum(2, 2)
end
end

== TDD: Test Driven Development ==

Test Driven Development is a combination of refactoring and test first development, a form of development where the test is

written prior to completed production code. The goal of TDD is the specification of requirements and not the validation of

requirements. There are a few testing frameworks that are used to implement the TDD programming technique.

[http://ruby.about.com/b/2009/01/28/test-driven-development-with-rails.htm]
This link provides a comprehensive overview of test driven development practices and available resources for implementation.

'''RSpec'''
RSpec is a testing framework for Behavior Driven Development, complete with its own expectations, matchers and mocking and

stubbing facilities. It goes along hand in hand with Cucumber, though it plays nicely with many other testing frameworks as well.

'''Model Examples'''
These are the equivalent of unit tests in Rails’ built in testing. Ironically
(for the traditional TDD’er) these are the only specs that we feel should actually interact
with the database. Learn more ….

'''Controller Examples'''
These align somewhat with functional tests in rails, except
that they do not actually render views (though you can force rendering of views
if you prefer). Instead of setting expectations about what goes on a page, you
set expectations about what templates get rendered. Learn more….

'''View Examples'''
This is the other half of Rails’ functional testing. View specs allow
you to set up assigns (thanks to ZenTest). Learn more ….

'''Helper Examples'''
let you specify directly methods that live in your helpers. Learn more ….

[http://www.ibm.com/developerworks/web/library/wa-rspec/]
The link provides a brief overview of RSpec with a comprehensive series of examples and a conceptual view of Rpecs step by step

implementation process

'''Cucumber'''
Cucumber is used with TDD and BDD within other testing frameworks such as RSpec by letting software development teams describe how

software should behave in plain text. The text is written in a business-readable domain-specific language and serves as

documentation, automated tests and development-aid - all rolled into one format.

[http://cukes.info/]
The link provides a detail decription, definition, and examples of Cucumber implementation best practices and supported

frameworks.

'''Cucumber Example:'''
Scenario: See all vendors
Given I am logged in as a user in the administrator role
And There are 3 vendors
When I go to the manage vendors page
Then I should see the first 3 vendor names

'''Shoulda'''
An extension to Test::Unit with additional helpers, macros, and assertions.

[http://www.thoughtbot.com/projects/shoulda]
The link provides a more conclusive definition of Shoulda along with installation facts and working examples of the Shoulda

testing framework within Ruby's built in Test::Unit

== BDD: Behavior Driven Development ==
[http://eggsonbread.com/2009/07/22/behavior-driven-development-in-a-nutshell/]
Behavior driven development was born from the concepts behind the implementation of TDD. It brings together strands from

TestDrivenDevelopment and DomainDrivenDesign into an integrated whole, making the relationship between these two powerful

approaches to software development more evident. Most test driven development testing frameworks such as RSpec and Cucumber also support behavior driven development testing.

[http://behaviour-driven.org/]
The link supports BDDs definition with additional links to more viable behavior driven development resources.

----

'''Other Test Tool Resources'''

''Watir:'' is an open-source library for automating web browsers. It allows you to write tests that are easy to read and maintain. It

is simple and flexible.

[http://wtr.rubyforge.org/]
The link provides an overview of Watir with installation specifications, examples, and supported platforms

''NullDB:'' [http://avdi.org/projects/nulldb/]
a way to speed up testing by avoiding database use.

''Bleakhouse:'' memory leak detection
[http://www.rubyinside.com/bleakhouse-tool-to-find-memory-leaks-in-your-rails-applications-470.html]
The link gives additional information on Bleakhouse profiling for memory leaks

''ruby-debug:''
Other than the extensive use of breakpoints Rails provides little to streamline the debugging process. Ruby-debug provides Rails with a plug-in extending the functionality of Rails built in debugger.

[http://rubyforge.org/softwaremap/trove_list.php?form_cat=47]
The link provides twenty additional debug resources available for RoR

== '''Conclusion''' ==

Rails is a very comprehensive development environment for Ruby with numerous extensions, plugins, and other resources outside of IDEs to strengthen the functionality of the open source web application framework.

== Reference ==

''All sources used to create this wiki are linked in the above text.''

CSC/ECE 517 Fall 2009/wiki1b team1

2009-09-21T02:52:32Z

Los Bravo: /* BDD: Behavior Driven Development */

CSC/ECE 517 Fall 2009

'''
== Resources for Rails (other than IDEs) ==
'''

IDEs are a valuable resource for Rails development, however there are many other resources and tools
that can either replace or supplement IDEs.

'''Resources for Rails other than IDEs
'''

'''''Rails API''''' - http://api.rubyonrails.org/

This site documents Rails files, classes and methods that can be used to build a Rails application.

'''''Rails Forum''''' - http://railsforum.com/

A discussion forum covering all aspects of Rails for beginners and experts including planning,
programming, extensions and production.

'''''Introducing Ruby on Rails'''''

Part 1 http://www.softwaredeveloper.com/features/intro-to-ruby-on-rails-042507/

Part 2 http://www.softwaredeveloper.com/features/intro-to-ruby-on-rails-part-two-043007/

An excellent introduction to Rails for novices

'''''Installers'''
''

Windows: InstantRails - http://instantrails.rubyforge.org/wiki/wiki.pl

An all in one, single click installer for Windows that includes a Rails server.

Mac: Locomotive - http://locomotive.raaum.org/

'''''Rails Projects''''' - http://www.workingwithrails.com/

A Database of Rails projects, programmers and websites

'''''Rails plugins''''' - http://agilewebdevelopment.com/

A collection of Rails open source plugins, searchable by category or keyword.

'''''Sample Rails''''' - http://snippets.dzone.com/tag/rails

A collection of Rails code snippets.

'''''Agile Rails book''''' - http://www.amazon.com/gp/product/097669400X/002-0481267-8083260?v=glance&n=283155

An excellent resource for learning how to apply Agile programming concepts to Rails.

'''''Rails cheatsheet''''' - http://www.blainekendall.com/uploads/RubyOnRails-Cheatsheet-BlaineKendall.pdf

One user's list of best practices, gotchas and quirks of developing with Rails.

'''''Rails best practices''''' - http://www.therailsway.com/

An official best practices list for programming in Rails.

'''''Advanced Rails''''' - http://webonrails.com/

A resource for the advanced Rails programmer.

'''''Rails Blog''''' - http://weblog.rubyonrails.org/

An online community of updates about current happenings with the Rails platform.

'''''Rails Guides''''' - http://guides.rubyonrails.org/

An all in one resource for learning Rails including Howtos, security and contributing to the Rails community.

'''''Authoring Rails plugins''''' - http://nubyonrails.com/articles/2006/05/04/the-complete-guide-to-rails-plugins-part-i

A complete guide to authoring your own Rails plugins.

'''

== '''Tools for Rails (other than IDEs)''' ==
'''

'''Test Unit'''
The Rails stack uses Test::Unit, known as the default Ruby unit testing framework shipping with Ruby. There are various plugins and extension that could be used with Rails built-in Test::Unit to extend its functionality for support of TDD and BDD testing practices.

[http://wiki.rubyonrails.org/addons/testing]
The link provides additional information in the form of supporting resources, whitepapers, examples, and plug-in documentation

'''Example'''
[http://wiki.rubyonrails.org/testing/test-unitrequire]

Image:class CalculatorTest < Test::Unit::TestCase
def test_add_two_numbers_for_the_sum
calculator = Calculator.new
assert_equal 4, calculator.sum(2, 2)
end
end

== TDD: Test Driven Development ==

Test Driven Development is a combination of refactoring and test first development, a form of development where the test is

written prior to completed production code. The goal of TDD is the specification of requirements and not the validation of

requirements. There are a few testing frameworks that are used to implement the TDD programming technique.

[http://ruby.about.com/b/2009/01/28/test-driven-development-with-rails.htm]
This link provides a comprehensive overview of test driven development practices and available resources for implementation.

'''RSpec'''
RSpec is a testing framework for Behavior Driven Development, complete with its own expectations, matchers and mocking and

stubbing facilities. It goes along hand in hand with Cucumber, though it plays nicely with many other testing frameworks as well.

'''Model Examples'''
These are the equivalent of unit tests in Rails’ built in testing. Ironically
(for the traditional TDD’er) these are the only specs that we feel should actually interact
with the database. Learn more ….

'''Controller Examples'''
These align somewhat with functional tests in rails, except
that they do not actually render views (though you can force rendering of views
if you prefer). Instead of setting expectations about what goes on a page, you
set expectations about what templates get rendered. Learn more….

'''View Examples'''
This is the other half of Rails’ functional testing. View specs allow
you to set up assigns (thanks to ZenTest). Learn more ….

'''Helper Examples'''
let you specify directly methods that live in your helpers. Learn more ….

[http://www.ibm.com/developerworks/web/library/wa-rspec/]
The link provides a brief overview of RSpec with a comprehensive series of examples and a conceptual view of Rpecs step by step

implementation process

'''Cucumber'''
Cucumber is used with TDD and BDD within other testing frameworks such as RSpec by letting software development teams describe how

software should behave in plain text. The text is written in a business-readable domain-specific language and serves as

documentation, automated tests and development-aid - all rolled into one format.

[http://cukes.info/]
The link provides a detail decription, definition, and examples of Cucumber implementation best practices and supported

frameworks.

'''Cucumber Example:'''
Scenario: See all vendors
Given I am logged in as a user in the administrator role
And There are 3 vendors
When I go to the manage vendors page
Then I should see the first 3 vendor names

'''Shoulda'''
An extension to Test::Unit with additional helpers, macros, and assertions.

[http://www.thoughtbot.com/projects/shoulda]
The link provides a more conclusive definition of Shoulda along with installation facts and working examples of the Shoulda

testing framework within Ruby's built in Test::Unit

== BDD: Behavior Driven Development ==
[http://eggsonbread.com/2009/07/22/behavior-driven-development-in-a-nutshell/]
Behavior driven development was born from the concepts behind the implementation of TDD. It brings together strands from

TestDrivenDevelopment and DomainDrivenDesign into an integrated whole, making the relationship between these two powerful

approaches to software development more evident. Most test driven development testing frameworks such as RSpec and Cucumber also support behavior driven development testing.

[http://behaviour-driven.org/]
The link supports BDDs definition with additional links to more viable behavior driven development resources.

----

'''Other Test Tool Resources'''

''Watir''
Watir is an open-source library for automating web browsers. It allows you to write tests that are easy to read and maintain. It

is simple and flexible.

[http://wtr.rubyforge.org/]
The link provides an overview of Watir with installation specifications, examples, and supported platforms

''NullDB'' - [http://avdi.org/projects/nulldb/]
a way to speed up testing by avoiding database use.

''Bleakhouse:'' memory leak detection
[http://www.rubyinside.com/bleakhouse-tool-to-find-memory-leaks-in-your-rails-applications-470.html]
The link gives additional information on Bleakhouse profiling for memory leaks

''ruby-debug''
Other than the extensive use of breakpoints, ruby-debug provides Rails with a plug-in extending the functionality of Rails built in debugger.

[http://rubyforge.org/softwaremap/trove_list.php?form_cat=47]
The link provides twenty debug resources available for RoR

== '''Conclusion''' ==

Rails is a very comprehensive development environment for Ruby with numerous extensions, plugins, and other resources outside of IDEs to strengthen the functionality of the open source web application framework.

== Reference ==

''All sources used to create this wiki are linked in the above text.''

CSC/ECE 517 Fall 2009/wiki1b team1

2009-09-21T02:51:17Z

Los Bravo: /* BDD: Behavior Driven Development */

CSC/ECE 517 Fall 2009

'''
== Resources for Rails (other than IDEs) ==
'''

IDEs are a valuable resource for Rails development, however there are many other resources and tools
that can either replace or supplement IDEs.

'''Resources for Rails other than IDEs
'''

'''''Rails API''''' - http://api.rubyonrails.org/

This site documents Rails files, classes and methods that can be used to build a Rails application.

'''''Rails Forum''''' - http://railsforum.com/

A discussion forum covering all aspects of Rails for beginners and experts including planning,
programming, extensions and production.

'''''Introducing Ruby on Rails'''''

Part 1 http://www.softwaredeveloper.com/features/intro-to-ruby-on-rails-042507/

Part 2 http://www.softwaredeveloper.com/features/intro-to-ruby-on-rails-part-two-043007/

An excellent introduction to Rails for novices

'''''Installers'''
''

Windows: InstantRails - http://instantrails.rubyforge.org/wiki/wiki.pl

An all in one, single click installer for Windows that includes a Rails server.

Mac: Locomotive - http://locomotive.raaum.org/

'''''Rails Projects''''' - http://www.workingwithrails.com/

A Database of Rails projects, programmers and websites

'''''Rails plugins''''' - http://agilewebdevelopment.com/

A collection of Rails open source plugins, searchable by category or keyword.

'''''Sample Rails''''' - http://snippets.dzone.com/tag/rails

A collection of Rails code snippets.

'''''Agile Rails book''''' - http://www.amazon.com/gp/product/097669400X/002-0481267-8083260?v=glance&n=283155

An excellent resource for learning how to apply Agile programming concepts to Rails.

'''''Rails cheatsheet''''' - http://www.blainekendall.com/uploads/RubyOnRails-Cheatsheet-BlaineKendall.pdf

One user's list of best practices, gotchas and quirks of developing with Rails.

'''''Rails best practices''''' - http://www.therailsway.com/

An official best practices list for programming in Rails.

'''''Advanced Rails''''' - http://webonrails.com/

A resource for the advanced Rails programmer.

'''''Rails Blog''''' - http://weblog.rubyonrails.org/

An online community of updates about current happenings with the Rails platform.

'''''Rails Guides''''' - http://guides.rubyonrails.org/

An all in one resource for learning Rails including Howtos, security and contributing to the Rails community.

'''''Authoring Rails plugins''''' - http://nubyonrails.com/articles/2006/05/04/the-complete-guide-to-rails-plugins-part-i

A complete guide to authoring your own Rails plugins.

'''

== '''Tools for Rails (other than IDEs)''' ==
'''

'''Test Unit'''
The Rails stack uses Test::Unit, known as the default Ruby unit testing framework shipping with Ruby. There are various plugins and extension that could be used with Rails built-in Test::Unit to extend its functionality for support of TDD and BDD testing practices.

[http://wiki.rubyonrails.org/addons/testing]
The link provides additional information in the form of supporting resources, whitepapers, examples, and plug-in documentation

'''Example'''
[http://wiki.rubyonrails.org/testing/test-unitrequire]

Image:class CalculatorTest < Test::Unit::TestCase
def test_add_two_numbers_for_the_sum
calculator = Calculator.new
assert_equal 4, calculator.sum(2, 2)
end
end

== TDD: Test Driven Development ==

Test Driven Development is a combination of refactoring and test first development, a form of development where the test is

written prior to completed production code. The goal of TDD is the specification of requirements and not the validation of

requirements. There are a few testing frameworks that are used to implement the TDD programming technique.

[http://ruby.about.com/b/2009/01/28/test-driven-development-with-rails.htm]
This link provides a comprehensive overview of test driven development practices and available resources for implementation.

'''RSpec'''
RSpec is a testing framework for Behavior Driven Development, complete with its own expectations, matchers and mocking and

stubbing facilities. It goes along hand in hand with Cucumber, though it plays nicely with many other testing frameworks as well.

'''Model Examples'''
These are the equivalent of unit tests in Rails’ built in testing. Ironically
(for the traditional TDD’er) these are the only specs that we feel should actually interact
with the database. Learn more ….

'''Controller Examples'''
These align somewhat with functional tests in rails, except
that they do not actually render views (though you can force rendering of views
if you prefer). Instead of setting expectations about what goes on a page, you
set expectations about what templates get rendered. Learn more….

'''View Examples'''
This is the other half of Rails’ functional testing. View specs allow
you to set up assigns (thanks to ZenTest). Learn more ….

'''Helper Examples'''
let you specify directly methods that live in your helpers. Learn more ….

[http://www.ibm.com/developerworks/web/library/wa-rspec/]
The link provides a brief overview of RSpec with a comprehensive series of examples and a conceptual view of Rpecs step by step

implementation process

'''Cucumber'''
Cucumber is used with TDD and BDD within other testing frameworks such as RSpec by letting software development teams describe how

software should behave in plain text. The text is written in a business-readable domain-specific language and serves as

documentation, automated tests and development-aid - all rolled into one format.

[http://cukes.info/]
The link provides a detail decription, definition, and examples of Cucumber implementation best practices and supported

frameworks.

'''Cucumber Example:'''
Scenario: See all vendors
Given I am logged in as a user in the administrator role
And There are 3 vendors
When I go to the manage vendors page
Then I should see the first 3 vendor names

'''Shoulda'''
An extension to Test::Unit with additional helpers, macros, and assertions.

[http://www.thoughtbot.com/projects/shoulda]
The link provides a more conclusive definition of Shoulda along with installation facts and working examples of the Shoulda

testing framework within Ruby's built in Test::Unit

== BDD: Behavior Driven Development ==
[http://eggsonbread.com/2009/07/22/behavior-driven-development-in-a-nutshell/]
Behavior driven development was born from the concepts behind the implementation of TDD. It brings together strands from

TestDrivenDevelopment and DomainDrivenDesign into an integrated whole, making the relationship between these two powerful

approaches to software development more evident. Most test driven development testing frameworks such as RSpec and Cucumber also support behavior driven development testing.

[http://behaviour-driven.org/]
The link supports BDDs definition with additional links to more viable behavior driven development resources.

----

'''Other Test Tool Resources'''

''Watir''
Watir is an open-source library for automating web browsers. It allows you to write tests that are easy to read and maintain. It

is simple and flexible.

[http://wtr.rubyforge.org/]
The link provides an overview of Watir with installation specifications, examples, and supported platforms

''NullDB'' - [http://avdi.org/projects/nulldb/]
a way to speed up testing by avoiding database use.

''Bleakhouse:'' memory leak detection
[http://www.rubyinside.com/bleakhouse-tool-to-find-memory-leaks-in-your-rails-applications-470.html]
The links gives additional information on Bleakhouse profiling for memory leaks

''ruby-debug''
Other than the extensive use of breakpoints, ruby-debug provides Rails with a plug-in extending the functionality of Rails built in debugger.

[http://rubyforge.org/softwaremap/trove_list.php?form_cat=47]
The link provides twenty debug resources available for RoR

== '''Conclusion''' ==

Rails is a very comprehensive development environment for Ruby with numerous extensions, plugins, and other resources outside of IDEs to strengthen the functionality of the open source web application framework.

== Reference ==

''All sources used to create this wiki are linked in the above text.''

CSC/ECE 517 Fall 2009/wiki1b team1

2009-09-21T02:49:09Z

Los Bravo: /* '''Conclusion''' */

CSC/ECE 517 Fall 2009

'''
== Resources for Rails (other than IDEs) ==
'''

IDEs are a valuable resource for Rails development, however there are many other resources and tools
that can either replace or supplement IDEs.

'''Resources for Rails other than IDEs
'''

'''''Rails API''''' - http://api.rubyonrails.org/

This site documents Rails files, classes and methods that can be used to build a Rails application.

'''''Rails Forum''''' - http://railsforum.com/

A discussion forum covering all aspects of Rails for beginners and experts including planning,
programming, extensions and production.

'''''Introducing Ruby on Rails'''''

Part 1 http://www.softwaredeveloper.com/features/intro-to-ruby-on-rails-042507/

Part 2 http://www.softwaredeveloper.com/features/intro-to-ruby-on-rails-part-two-043007/

An excellent introduction to Rails for novices

'''''Installers'''
''

Windows: InstantRails - http://instantrails.rubyforge.org/wiki/wiki.pl

An all in one, single click installer for Windows that includes a Rails server.

Mac: Locomotive - http://locomotive.raaum.org/

'''''Rails Projects''''' - http://www.workingwithrails.com/

A Database of Rails projects, programmers and websites

'''''Rails plugins''''' - http://agilewebdevelopment.com/

A collection of Rails open source plugins, searchable by category or keyword.

'''''Sample Rails''''' - http://snippets.dzone.com/tag/rails

A collection of Rails code snippets.

'''''Agile Rails book''''' - http://www.amazon.com/gp/product/097669400X/002-0481267-8083260?v=glance&n=283155

An excellent resource for learning how to apply Agile programming concepts to Rails.

'''''Rails cheatsheet''''' - http://www.blainekendall.com/uploads/RubyOnRails-Cheatsheet-BlaineKendall.pdf

One user's list of best practices, gotchas and quirks of developing with Rails.

'''''Rails best practices''''' - http://www.therailsway.com/

An official best practices list for programming in Rails.

'''''Advanced Rails''''' - http://webonrails.com/

A resource for the advanced Rails programmer.

'''''Rails Blog''''' - http://weblog.rubyonrails.org/

An online community of updates about current happenings with the Rails platform.

'''''Rails Guides''''' - http://guides.rubyonrails.org/

An all in one resource for learning Rails including Howtos, security and contributing to the Rails community.

'''''Authoring Rails plugins''''' - http://nubyonrails.com/articles/2006/05/04/the-complete-guide-to-rails-plugins-part-i

A complete guide to authoring your own Rails plugins.

'''

== '''Tools for Rails (other than IDEs)''' ==
'''

'''Test Unit'''
The Rails stack uses Test::Unit, known as the default Ruby unit testing framework shipping with Ruby. There are various plugins and extension that could be used with Rails built-in Test::Unit to extend its functionality for support of TDD and BDD testing practices.

[http://wiki.rubyonrails.org/addons/testing]
The link provides additional information in the form of supporting resources, whitepapers, examples, and plug-in documentation

'''Example'''
[http://wiki.rubyonrails.org/testing/test-unitrequire]

Image:class CalculatorTest < Test::Unit::TestCase
def test_add_two_numbers_for_the_sum
calculator = Calculator.new
assert_equal 4, calculator.sum(2, 2)
end
end

== TDD: Test Driven Development ==

Test Driven Development is a combination of refactoring and test first development, a form of development where the test is

written prior to completed production code. The goal of TDD is the specification of requirements and not the validation of

requirements. There are a few testing frameworks that are used to implement the TDD programming technique.

[http://ruby.about.com/b/2009/01/28/test-driven-development-with-rails.htm]
This link provides a comprehensive overview of test driven development practices and available resources for implementation.

'''RSpec'''
RSpec is a testing framework for Behavior Driven Development, complete with its own expectations, matchers and mocking and

stubbing facilities. It goes along hand in hand with Cucumber, though it plays nicely with many other testing frameworks as well.

'''Model Examples'''
These are the equivalent of unit tests in Rails’ built in testing. Ironically
(for the traditional TDD’er) these are the only specs that we feel should actually interact
with the database. Learn more ….

'''Controller Examples'''
These align somewhat with functional tests in rails, except
that they do not actually render views (though you can force rendering of views
if you prefer). Instead of setting expectations about what goes on a page, you
set expectations about what templates get rendered. Learn more….

'''View Examples'''
This is the other half of Rails’ functional testing. View specs allow
you to set up assigns (thanks to ZenTest). Learn more ….

'''Helper Examples'''
let you specify directly methods that live in your helpers. Learn more ….

[http://www.ibm.com/developerworks/web/library/wa-rspec/]
The link provides a brief overview of RSpec with a comprehensive series of examples and a conceptual view of Rpecs step by step

implementation process

'''Cucumber'''
Cucumber is used with TDD and BDD within other testing frameworks such as RSpec by letting software development teams describe how

software should behave in plain text. The text is written in a business-readable domain-specific language and serves as

documentation, automated tests and development-aid - all rolled into one format.

[http://cukes.info/]
The link provides a detail decription, definition, and examples of Cucumber implementation best practices and supported

frameworks.

'''Cucumber Example:'''
Scenario: See all vendors
Given I am logged in as a user in the administrator role
And There are 3 vendors
When I go to the manage vendors page
Then I should see the first 3 vendor names

'''Shoulda'''
An extension to Test::Unit with additional helpers, macros, and assertions.

[http://www.thoughtbot.com/projects/shoulda]
The link provides a more conclusive definition of Shoulda along with installation facts and working examples of the Shoulda

testing framework within Ruby's built in Test::Unit

== BDD: Behavior Driven Development ==
[http://eggsonbread.com/2009/07/22/behavior-driven-development-in-a-nutshell/]
Behavior driven development was born from the concepts behind the implementation of TDD. It brings together strands from

TestDrivenDevelopment and DomainDrivenDesign into an integrated whole, making the relationship between these two powerful

approaches to software development more evident. Most test driven development testing frameworks such as RSpec and Cucumber also support behavior driven development testing.

[http://behaviour-driven.org/]
The link supports BDDs definition with additional links to more viable behavior driven development resources.

----

'''Other Test Tool Resources'''

''Watir''
Watir is an open-source library for automating web browsers. It allows you to write tests that are easy to read and maintain. It

is simple and flexible.

[http://wtr.rubyforge.org/]
The link provides an overview of Watir with installation specifications, examples, and supported platforms

''NullDB'' - [http://avdi.org/projects/nulldb/]
a way to speed up testing by avoiding database use.

''Bleakhouse:'' memory leak detection
http://www.rubyinside.com/bleakhouse-tool-to-find-memory-leaks-in-your-rails-applications-470.html
The links gives additional information on Bleakhouse profiling for memory leaks

''ruby-debug''
Other than the extensive use of breakpoints, ruby-debug provides Rails with a plug-in extending the functionality of Rails built in debugger.

[http://rubyforge.org/softwaremap/trove_list.php?form_cat=47]
The link provides twenty debug resources available for RoR

== '''Conclusion''' ==

Rails is a very comprehensive development environment for Ruby with numerous extensions, plugins, and other resources outside of IDEs to strengthen the functionality of the open source web application framework.

== Reference ==

''All sources used to create this wiki are linked in the above text.''

CSC/ECE 517 Fall 2009/wiki1b team1

2009-09-21T02:44:50Z

Los Bravo: /* BDD: Behavior Driven Development */

CSC/ECE 517 Fall 2009

'''
== Resources for Rails (other than IDEs) ==
'''

IDEs are a valuable resource for Rails development, however there are many other resources and tools
that can either replace or supplement IDEs.

'''Resources for Rails other than IDEs
'''

'''''Rails API''''' - http://api.rubyonrails.org/

This site documents Rails files, classes and methods that can be used to build a Rails application.

'''''Rails Forum''''' - http://railsforum.com/

A discussion forum covering all aspects of Rails for beginners and experts including planning,
programming, extensions and production.

'''''Introducing Ruby on Rails'''''

Part 1 http://www.softwaredeveloper.com/features/intro-to-ruby-on-rails-042507/

Part 2 http://www.softwaredeveloper.com/features/intro-to-ruby-on-rails-part-two-043007/

An excellent introduction to Rails for novices

'''''Installers'''
''

Windows: InstantRails - http://instantrails.rubyforge.org/wiki/wiki.pl

An all in one, single click installer for Windows that includes a Rails server.

Mac: Locomotive - http://locomotive.raaum.org/

'''''Rails Projects''''' - http://www.workingwithrails.com/

A Database of Rails projects, programmers and websites

'''''Rails plugins''''' - http://agilewebdevelopment.com/

A collection of Rails open source plugins, searchable by category or keyword.

'''''Sample Rails''''' - http://snippets.dzone.com/tag/rails

A collection of Rails code snippets.

'''''Agile Rails book''''' - http://www.amazon.com/gp/product/097669400X/002-0481267-8083260?v=glance&n=283155

An excellent resource for learning how to apply Agile programming concepts to Rails.

'''''Rails cheatsheet''''' - http://www.blainekendall.com/uploads/RubyOnRails-Cheatsheet-BlaineKendall.pdf

One user's list of best practices, gotchas and quirks of developing with Rails.

'''''Rails best practices''''' - http://www.therailsway.com/

An official best practices list for programming in Rails.

'''''Advanced Rails''''' - http://webonrails.com/

A resource for the advanced Rails programmer.

'''''Rails Blog''''' - http://weblog.rubyonrails.org/

An online community of updates about current happenings with the Rails platform.

'''''Rails Guides''''' - http://guides.rubyonrails.org/

An all in one resource for learning Rails including Howtos, security and contributing to the Rails community.

'''''Authoring Rails plugins''''' - http://nubyonrails.com/articles/2006/05/04/the-complete-guide-to-rails-plugins-part-i

A complete guide to authoring your own Rails plugins.

'''

== '''Tools for Rails (other than IDEs)''' ==
'''

'''Test Unit'''
The Rails stack uses Test::Unit, known as the default Ruby unit testing framework shipping with Ruby. There are various plugins and extension that could be used with Rails built-in Test::Unit to extend its functionality for support of TDD and BDD testing practices.

[http://wiki.rubyonrails.org/addons/testing]
The link provides additional information in the form of supporting resources, whitepapers, examples, and plug-in documentation

'''Example'''
[http://wiki.rubyonrails.org/testing/test-unitrequire]

Image:class CalculatorTest < Test::Unit::TestCase
def test_add_two_numbers_for_the_sum
calculator = Calculator.new
assert_equal 4, calculator.sum(2, 2)
end
end

== TDD: Test Driven Development ==

Test Driven Development is a combination of refactoring and test first development, a form of development where the test is

written prior to completed production code. The goal of TDD is the specification of requirements and not the validation of

requirements. There are a few testing frameworks that are used to implement the TDD programming technique.

[http://ruby.about.com/b/2009/01/28/test-driven-development-with-rails.htm]
This link provides a comprehensive overview of test driven development practices and available resources for implementation.

'''RSpec'''
RSpec is a testing framework for Behavior Driven Development, complete with its own expectations, matchers and mocking and

stubbing facilities. It goes along hand in hand with Cucumber, though it plays nicely with many other testing frameworks as well.

'''Model Examples'''
These are the equivalent of unit tests in Rails’ built in testing. Ironically
(for the traditional TDD’er) these are the only specs that we feel should actually interact
with the database. Learn more ….

'''Controller Examples'''
These align somewhat with functional tests in rails, except
that they do not actually render views (though you can force rendering of views
if you prefer). Instead of setting expectations about what goes on a page, you
set expectations about what templates get rendered. Learn more….

'''View Examples'''
This is the other half of Rails’ functional testing. View specs allow
you to set up assigns (thanks to ZenTest). Learn more ….

'''Helper Examples'''
let you specify directly methods that live in your helpers. Learn more ….

[http://www.ibm.com/developerworks/web/library/wa-rspec/]
The link provides a brief overview of RSpec with a comprehensive series of examples and a conceptual view of Rpecs step by step

implementation process

'''Cucumber'''
Cucumber is used with TDD and BDD within other testing frameworks such as RSpec by letting software development teams describe how

software should behave in plain text. The text is written in a business-readable domain-specific language and serves as

documentation, automated tests and development-aid - all rolled into one format.

[http://cukes.info/]
The link provides a detail decription, definition, and examples of Cucumber implementation best practices and supported

frameworks.

'''Cucumber Example:'''
Scenario: See all vendors
Given I am logged in as a user in the administrator role
And There are 3 vendors
When I go to the manage vendors page
Then I should see the first 3 vendor names

'''Shoulda'''
An extension to Test::Unit with additional helpers, macros, and assertions.

[http://www.thoughtbot.com/projects/shoulda]
The link provides a more conclusive definition of Shoulda along with installation facts and working examples of the Shoulda

testing framework within Ruby's built in Test::Unit

== BDD: Behavior Driven Development ==
[http://eggsonbread.com/2009/07/22/behavior-driven-development-in-a-nutshell/]
Behavior driven development was born from the concepts behind the implementation of TDD. It brings together strands from

TestDrivenDevelopment and DomainDrivenDesign into an integrated whole, making the relationship between these two powerful

approaches to software development more evident. Most test driven development testing frameworks such as RSpec and Cucumber also support behavior driven development testing.

[http://behaviour-driven.org/]
The link supports BDDs definition with additional links to more viable behavior driven development resources.

----

'''Other Test Tool Resources'''

''Watir''
Watir is an open-source library for automating web browsers. It allows you to write tests that are easy to read and maintain. It

is simple and flexible.

[http://wtr.rubyforge.org/]
The link provides an overview of Watir with installation specifications, examples, and supported platforms

''NullDB'' - [http://avdi.org/projects/nulldb/]
a way to speed up testing by avoiding database use.

''Bleakhouse:'' memory leak detection
http://www.rubyinside.com/bleakhouse-tool-to-find-memory-leaks-in-your-rails-applications-470.html
The links gives additional information on Bleakhouse profiling for memory leaks

''ruby-debug''
Other than the extensive use of breakpoints, ruby-debug provides Rails with a plug-in extending the functionality of Rails built in debugger.

[http://rubyforge.org/softwaremap/trove_list.php?form_cat=47]
The link provides twenty debug resources available for RoR

== '''Conclusion''' ==

== Reference ==

''All sources used to create this wiki are linked in the above text.''

CSC/ECE 517 Fall 2009/wiki1b team1

2009-09-21T02:37:34Z

Los Bravo: /* BDD: Behavior Driven Development */

CSC/ECE 517 Fall 2009

'''
== Resources for Rails (other than IDEs) ==
'''

IDEs are a valuable resource for Rails development, however there are many other resources and tools
that can either replace or supplement IDEs.

'''Resources for Rails other than IDEs
'''

'''''Rails API''''' - http://api.rubyonrails.org/

This site documents Rails files, classes and methods that can be used to build a Rails application.

'''''Rails Forum''''' - http://railsforum.com/

A discussion forum covering all aspects of Rails for beginners and experts including planning,
programming, extensions and production.

'''''Introducing Ruby on Rails'''''

Part 1 http://www.softwaredeveloper.com/features/intro-to-ruby-on-rails-042507/

Part 2 http://www.softwaredeveloper.com/features/intro-to-ruby-on-rails-part-two-043007/

An excellent introduction to Rails for novices

'''''Installers'''
''

Windows: InstantRails - http://instantrails.rubyforge.org/wiki/wiki.pl

An all in one, single click installer for Windows that includes a Rails server.

Mac: Locomotive - http://locomotive.raaum.org/

'''''Rails Projects''''' - http://www.workingwithrails.com/

A Database of Rails projects, programmers and websites

'''''Rails plugins''''' - http://agilewebdevelopment.com/

A collection of Rails open source plugins, searchable by category or keyword.

'''''Sample Rails''''' - http://snippets.dzone.com/tag/rails

A collection of Rails code snippets.

'''''Agile Rails book''''' - http://www.amazon.com/gp/product/097669400X/002-0481267-8083260?v=glance&n=283155

An excellent resource for learning how to apply Agile programming concepts to Rails.

'''''Rails cheatsheet''''' - http://www.blainekendall.com/uploads/RubyOnRails-Cheatsheet-BlaineKendall.pdf

One user's list of best practices, gotchas and quirks of developing with Rails.

'''''Rails best practices''''' - http://www.therailsway.com/

An official best practices list for programming in Rails.

'''''Advanced Rails''''' - http://webonrails.com/

A resource for the advanced Rails programmer.

'''''Rails Blog''''' - http://weblog.rubyonrails.org/

An online community of updates about current happenings with the Rails platform.

'''''Rails Guides''''' - http://guides.rubyonrails.org/

An all in one resource for learning Rails including Howtos, security and contributing to the Rails community.

'''''Authoring Rails plugins''''' - http://nubyonrails.com/articles/2006/05/04/the-complete-guide-to-rails-plugins-part-i

A complete guide to authoring your own Rails plugins.

'''

== '''Tools for Rails (other than IDEs)''' ==
'''

'''Test Unit'''
The Rails stack uses Test::Unit, known as the default Ruby unit testing framework shipping with Ruby. There are various plugins and extension that could be used with Rails built-in Test::Unit to extend its functionality for support of TDD and BDD testing practices.

[http://wiki.rubyonrails.org/addons/testing]
The link provides additional information in the form of supporting resources, whitepapers, examples, and plug-in documentation

'''Example'''
[http://wiki.rubyonrails.org/testing/test-unitrequire]

Image:class CalculatorTest < Test::Unit::TestCase
def test_add_two_numbers_for_the_sum
calculator = Calculator.new
assert_equal 4, calculator.sum(2, 2)
end
end

== TDD: Test Driven Development ==

Test Driven Development is a combination of refactoring and test first development, a form of development where the test is

written prior to completed production code. The goal of TDD is the specification of requirements and not the validation of

requirements. There are a few testing frameworks that are used to implement the TDD programming technique.

[http://ruby.about.com/b/2009/01/28/test-driven-development-with-rails.htm]
This link provides a comprehensive overview of test driven development practices and available resources for implementation.

'''RSpec'''
RSpec is a testing framework for Behavior Driven Development, complete with its own expectations, matchers and mocking and

stubbing facilities. It goes along hand in hand with Cucumber, though it plays nicely with many other testing frameworks as well.

'''Model Examples'''
These are the equivalent of unit tests in Rails’ built in testing. Ironically
(for the traditional TDD’er) these are the only specs that we feel should actually interact
with the database. Learn more ….

'''Controller Examples'''
These align somewhat with functional tests in rails, except
that they do not actually render views (though you can force rendering of views
if you prefer). Instead of setting expectations about what goes on a page, you
set expectations about what templates get rendered. Learn more….

'''View Examples'''
This is the other half of Rails’ functional testing. View specs allow
you to set up assigns (thanks to ZenTest). Learn more ….

'''Helper Examples'''
let you specify directly methods that live in your helpers. Learn more ….

[http://www.ibm.com/developerworks/web/library/wa-rspec/]
The link provides a brief overview of RSpec with a comprehensive series of examples and a conceptual view of Rpecs step by step

implementation process

'''Cucumber'''
Cucumber is used with TDD and BDD within other testing frameworks such as RSpec by letting software development teams describe how

software should behave in plain text. The text is written in a business-readable domain-specific language and serves as

documentation, automated tests and development-aid - all rolled into one format.

[http://cukes.info/]
The link provides a detail decription, definition, and examples of Cucumber implementation best practices and supported

frameworks.

'''Cucumber Example:'''
Scenario: See all vendors
Given I am logged in as a user in the administrator role
And There are 3 vendors
When I go to the manage vendors page
Then I should see the first 3 vendor names

'''Shoulda'''
An extension to Test::Unit with additional helpers, macros, and assertions.

[http://www.thoughtbot.com/projects/shoulda]
The link provides a more conclusive definition of Shoulda along with installation facts and working examples of the Shoulda

testing framework within Ruby's built in Test::Unit

== BDD: Behavior Driven Development ==
[http://eggsonbread.com/2009/07/22/behavior-driven-development-in-a-nutshell/]
Behavior driven development was born from the concepts behind the implementation of TDD. It brings together strands from

TestDrivenDevelopment and DomainDrivenDesign into an integrated whole, making the relationship between these two powerful

approaches to software development more evident. Most test driven development testing frameworks such as RSpec and Cucumber also support behavior driven development testing.

[http://behaviour-driven.org/]
The link supports BDDs definition with additional links to more viable behavior driven development resources.

----

'''Other Test Tool Resources'''

''Watir''
Watir is an open-source library for automating web browsers. It allows you to write tests that are easy to read and maintain. It

is simple and flexible.

[http://wtr.rubyforge.org/]

''NullDB'' - [http://avdi.org/projects/nulldb/]
a way to speed up testing by avoiding database use.

''Bleakhouse:'' memory leak detection

''ruby-debug''
Other than the extensive use of breakpoints, ruby-debug provides Rails with a plug-in extending the functionality of Rails built in debugger.

[http://rubyforge.org/softwaremap/trove_list.php?form_cat=47]
The link provides twenty debug resources available for RoR

== '''Conclusion''' ==

== Reference ==

''All sources used to create this wiki are linked in the above text.''

CSC/ECE 517 Fall 2009/wiki1b team1

2009-09-21T02:36:21Z

Los Bravo: /* Reference */

CSC/ECE 517 Fall 2009

'''
== Resources for Rails (other than IDEs) ==
'''

IDEs are a valuable resource for Rails development, however there are many other resources and tools
that can either replace or supplement IDEs.

'''Resources for Rails other than IDEs
'''

'''''Rails API''''' - http://api.rubyonrails.org/

This site documents Rails files, classes and methods that can be used to build a Rails application.

'''''Rails Forum''''' - http://railsforum.com/

A discussion forum covering all aspects of Rails for beginners and experts including planning,
programming, extensions and production.

'''''Introducing Ruby on Rails'''''

Part 1 http://www.softwaredeveloper.com/features/intro-to-ruby-on-rails-042507/

Part 2 http://www.softwaredeveloper.com/features/intro-to-ruby-on-rails-part-two-043007/

An excellent introduction to Rails for novices

'''''Installers'''
''

Windows: InstantRails - http://instantrails.rubyforge.org/wiki/wiki.pl

An all in one, single click installer for Windows that includes a Rails server.

Mac: Locomotive - http://locomotive.raaum.org/

'''''Rails Projects''''' - http://www.workingwithrails.com/

A Database of Rails projects, programmers and websites

'''''Rails plugins''''' - http://agilewebdevelopment.com/

A collection of Rails open source plugins, searchable by category or keyword.

'''''Sample Rails''''' - http://snippets.dzone.com/tag/rails

A collection of Rails code snippets.

'''''Agile Rails book''''' - http://www.amazon.com/gp/product/097669400X/002-0481267-8083260?v=glance&n=283155

An excellent resource for learning how to apply Agile programming concepts to Rails.

'''''Rails cheatsheet''''' - http://www.blainekendall.com/uploads/RubyOnRails-Cheatsheet-BlaineKendall.pdf

One user's list of best practices, gotchas and quirks of developing with Rails.

'''''Rails best practices''''' - http://www.therailsway.com/

An official best practices list for programming in Rails.

'''''Advanced Rails''''' - http://webonrails.com/

A resource for the advanced Rails programmer.

'''''Rails Blog''''' - http://weblog.rubyonrails.org/

An online community of updates about current happenings with the Rails platform.

'''''Rails Guides''''' - http://guides.rubyonrails.org/

An all in one resource for learning Rails including Howtos, security and contributing to the Rails community.

'''''Authoring Rails plugins''''' - http://nubyonrails.com/articles/2006/05/04/the-complete-guide-to-rails-plugins-part-i

A complete guide to authoring your own Rails plugins.

'''

== '''Tools for Rails (other than IDEs)''' ==
'''

'''Test Unit'''
The Rails stack uses Test::Unit, known as the default Ruby unit testing framework shipping with Ruby. There are various plugins and extension that could be used with Rails built-in Test::Unit to extend its functionality for support of TDD and BDD testing practices.

[http://wiki.rubyonrails.org/addons/testing]
The link provides additional information in the form of supporting resources, whitepapers, examples, and plug-in documentation

'''Example'''
[http://wiki.rubyonrails.org/testing/test-unitrequire]

Image:class CalculatorTest < Test::Unit::TestCase
def test_add_two_numbers_for_the_sum
calculator = Calculator.new
assert_equal 4, calculator.sum(2, 2)
end
end

== TDD: Test Driven Development ==

Test Driven Development is a combination of refactoring and test first development, a form of development where the test is

written prior to completed production code. The goal of TDD is the specification of requirements and not the validation of

requirements. There are a few testing frameworks that are used to implement the TDD programming technique.

[http://ruby.about.com/b/2009/01/28/test-driven-development-with-rails.htm]
This link provides a comprehensive overview of test driven development practices and available resources for implementation.

'''RSpec'''
RSpec is a testing framework for Behavior Driven Development, complete with its own expectations, matchers and mocking and

stubbing facilities. It goes along hand in hand with Cucumber, though it plays nicely with many other testing frameworks as well.

'''Model Examples'''
These are the equivalent of unit tests in Rails’ built in testing. Ironically
(for the traditional TDD’er) these are the only specs that we feel should actually interact
with the database. Learn more ….

'''Controller Examples'''
These align somewhat with functional tests in rails, except
that they do not actually render views (though you can force rendering of views
if you prefer). Instead of setting expectations about what goes on a page, you
set expectations about what templates get rendered. Learn more….

'''View Examples'''
This is the other half of Rails’ functional testing. View specs allow
you to set up assigns (thanks to ZenTest). Learn more ….

'''Helper Examples'''
let you specify directly methods that live in your helpers. Learn more ….

[http://www.ibm.com/developerworks/web/library/wa-rspec/]
The link provides a brief overview of RSpec with a comprehensive series of examples and a conceptual view of Rpecs step by step

implementation process

'''Cucumber'''
Cucumber is used with TDD and BDD within other testing frameworks such as RSpec by letting software development teams describe how

software should behave in plain text. The text is written in a business-readable domain-specific language and serves as

documentation, automated tests and development-aid - all rolled into one format.

[http://cukes.info/]
The link provides a detail decription, definition, and examples of Cucumber implementation best practices and supported

frameworks.

'''Cucumber Example:'''
Scenario: See all vendors
Given I am logged in as a user in the administrator role
And There are 3 vendors
When I go to the manage vendors page
Then I should see the first 3 vendor names

'''Shoulda'''
An extension to Test::Unit with additional helpers, macros, and assertions.

[http://www.thoughtbot.com/projects/shoulda]
The link provides a more conclusive definition of Shoulda along with installation facts and working examples of the Shoulda

testing framework within Ruby's built in Test::Unit

== BDD: Behavior Driven Development ==
[http://eggsonbread.com/2009/07/22/behavior-driven-development-in-a-nutshell/]
Behavior driven development was born from the concepts behind the implementation of TDD. It brings together strands from

TestDrivenDevelopment and DomainDrivenDesign into an integrated whole, making the relationship between these two powerful

approaches to software development more evident. Most test driven development testing frameworks such as RSpec and Cucumber also support behavior driven development testing.

[http://behaviour-driven.org/]
The link supports BDDs definition with additional links to more viable behavior driven development resources.

----

'''Other Test Tool Resources'''
Watir
Watir is an open-source library for automating web browsers. It allows you to write tests that are easy to read and maintain. It

is simple and flexible.

[http://wtr.rubyforge.org/]

'''NullDB''' - [http://avdi.org/projects/nulldb/]
a way to speed up testing by avoiding database use.

'''Bleakhouse:''' memory leak detection

'''ruby-debug'''
Other than the extensive use of breakpoints, ruby-debug provides Rails with a plug-in extending the functionality of Rails built in debugger.

[http://rubyforge.org/softwaremap/trove_list.php?form_cat=47]
The link provides twenty debug resources available for RoR

== '''Conclusion''' ==

== Reference ==

''All sources used to create this wiki are linked in the above text.''

CSC/ECE 517 Fall 2009/wiki1b team1

2009-09-21T02:35:54Z

Los Bravo: /* BDD: Behavior Driven Development */

CSC/ECE 517 Fall 2009

'''
== Resources for Rails (other than IDEs) ==
'''

IDEs are a valuable resource for Rails development, however there are many other resources and tools
that can either replace or supplement IDEs.

'''Resources for Rails other than IDEs
'''

'''''Rails API''''' - http://api.rubyonrails.org/

This site documents Rails files, classes and methods that can be used to build a Rails application.

'''''Rails Forum''''' - http://railsforum.com/

A discussion forum covering all aspects of Rails for beginners and experts including planning,
programming, extensions and production.

'''''Introducing Ruby on Rails'''''

Part 1 http://www.softwaredeveloper.com/features/intro-to-ruby-on-rails-042507/

Part 2 http://www.softwaredeveloper.com/features/intro-to-ruby-on-rails-part-two-043007/

An excellent introduction to Rails for novices

'''''Installers'''
''

Windows: InstantRails - http://instantrails.rubyforge.org/wiki/wiki.pl

An all in one, single click installer for Windows that includes a Rails server.

Mac: Locomotive - http://locomotive.raaum.org/

'''''Rails Projects''''' - http://www.workingwithrails.com/

A Database of Rails projects, programmers and websites

'''''Rails plugins''''' - http://agilewebdevelopment.com/

A collection of Rails open source plugins, searchable by category or keyword.

'''''Sample Rails''''' - http://snippets.dzone.com/tag/rails

A collection of Rails code snippets.

'''''Agile Rails book''''' - http://www.amazon.com/gp/product/097669400X/002-0481267-8083260?v=glance&n=283155

An excellent resource for learning how to apply Agile programming concepts to Rails.

'''''Rails cheatsheet''''' - http://www.blainekendall.com/uploads/RubyOnRails-Cheatsheet-BlaineKendall.pdf

One user's list of best practices, gotchas and quirks of developing with Rails.

'''''Rails best practices''''' - http://www.therailsway.com/

An official best practices list for programming in Rails.

'''''Advanced Rails''''' - http://webonrails.com/

A resource for the advanced Rails programmer.

'''''Rails Blog''''' - http://weblog.rubyonrails.org/

An online community of updates about current happenings with the Rails platform.

'''''Rails Guides''''' - http://guides.rubyonrails.org/

An all in one resource for learning Rails including Howtos, security and contributing to the Rails community.

'''''Authoring Rails plugins''''' - http://nubyonrails.com/articles/2006/05/04/the-complete-guide-to-rails-plugins-part-i

A complete guide to authoring your own Rails plugins.

'''

== '''Tools for Rails (other than IDEs)''' ==
'''

'''Test Unit'''
The Rails stack uses Test::Unit, known as the default Ruby unit testing framework shipping with Ruby. There are various plugins and extension that could be used with Rails built-in Test::Unit to extend its functionality for support of TDD and BDD testing practices.

[http://wiki.rubyonrails.org/addons/testing]
The link provides additional information in the form of supporting resources, whitepapers, examples, and plug-in documentation

'''Example'''
[http://wiki.rubyonrails.org/testing/test-unitrequire]

Image:class CalculatorTest < Test::Unit::TestCase
def test_add_two_numbers_for_the_sum
calculator = Calculator.new
assert_equal 4, calculator.sum(2, 2)
end
end

== TDD: Test Driven Development ==

Test Driven Development is a combination of refactoring and test first development, a form of development where the test is

written prior to completed production code. The goal of TDD is the specification of requirements and not the validation of

requirements. There are a few testing frameworks that are used to implement the TDD programming technique.

[http://ruby.about.com/b/2009/01/28/test-driven-development-with-rails.htm]
This link provides a comprehensive overview of test driven development practices and available resources for implementation.

'''RSpec'''
RSpec is a testing framework for Behavior Driven Development, complete with its own expectations, matchers and mocking and

stubbing facilities. It goes along hand in hand with Cucumber, though it plays nicely with many other testing frameworks as well.

'''Model Examples'''
These are the equivalent of unit tests in Rails’ built in testing. Ironically
(for the traditional TDD’er) these are the only specs that we feel should actually interact
with the database. Learn more ….

'''Controller Examples'''
These align somewhat with functional tests in rails, except
that they do not actually render views (though you can force rendering of views
if you prefer). Instead of setting expectations about what goes on a page, you
set expectations about what templates get rendered. Learn more….

'''View Examples'''
This is the other half of Rails’ functional testing. View specs allow
you to set up assigns (thanks to ZenTest). Learn more ….

'''Helper Examples'''
let you specify directly methods that live in your helpers. Learn more ….

[http://www.ibm.com/developerworks/web/library/wa-rspec/]
The link provides a brief overview of RSpec with a comprehensive series of examples and a conceptual view of Rpecs step by step

implementation process

'''Cucumber'''
Cucumber is used with TDD and BDD within other testing frameworks such as RSpec by letting software development teams describe how

software should behave in plain text. The text is written in a business-readable domain-specific language and serves as

documentation, automated tests and development-aid - all rolled into one format.

[http://cukes.info/]
The link provides a detail decription, definition, and examples of Cucumber implementation best practices and supported

frameworks.

'''Cucumber Example:'''
Scenario: See all vendors
Given I am logged in as a user in the administrator role
And There are 3 vendors
When I go to the manage vendors page
Then I should see the first 3 vendor names

'''Shoulda'''
An extension to Test::Unit with additional helpers, macros, and assertions.

[http://www.thoughtbot.com/projects/shoulda]
The link provides a more conclusive definition of Shoulda along with installation facts and working examples of the Shoulda

testing framework within Ruby's built in Test::Unit

== BDD: Behavior Driven Development ==
[http://eggsonbread.com/2009/07/22/behavior-driven-development-in-a-nutshell/]
Behavior driven development was born from the concepts behind the implementation of TDD. It brings together strands from

TestDrivenDevelopment and DomainDrivenDesign into an integrated whole, making the relationship between these two powerful

approaches to software development more evident. Most test driven development testing frameworks such as RSpec and Cucumber also support behavior driven development testing.

[http://behaviour-driven.org/]
The link supports BDDs definition with additional links to more viable behavior driven development resources.

----

'''Other Test Tool Resources'''
Watir
Watir is an open-source library for automating web browsers. It allows you to write tests that are easy to read and maintain. It

is simple and flexible.

[http://wtr.rubyforge.org/]

'''NullDB''' - [http://avdi.org/projects/nulldb/]
a way to speed up testing by avoiding database use.

'''Bleakhouse:''' memory leak detection

'''ruby-debug'''
Other than the extensive use of breakpoints, ruby-debug provides Rails with a plug-in extending the functionality of Rails built in debugger.

[http://rubyforge.org/softwaremap/trove_list.php?form_cat=47]
The link provides twenty debug resources available for RoR

== '''Conclusion''' ==

== Reference ==

All sources used to create this wiki are linked in the above text.

CSC/ECE 517 Fall 2009/wiki1b team1

2009-09-21T02:34:19Z

Los Bravo: /* '''Reference''' */

CSC/ECE 517 Fall 2009

'''
== Resources for Rails (other than IDEs) ==
'''

IDEs are a valuable resource for Rails development, however there are many other resources and tools
that can either replace or supplement IDEs.

'''Resources for Rails other than IDEs
'''

'''''Rails API''''' - http://api.rubyonrails.org/

This site documents Rails files, classes and methods that can be used to build a Rails application.

'''''Rails Forum''''' - http://railsforum.com/

A discussion forum covering all aspects of Rails for beginners and experts including planning,
programming, extensions and production.

'''''Introducing Ruby on Rails'''''

Part 1 http://www.softwaredeveloper.com/features/intro-to-ruby-on-rails-042507/

Part 2 http://www.softwaredeveloper.com/features/intro-to-ruby-on-rails-part-two-043007/

An excellent introduction to Rails for novices

'''''Installers'''
''

Windows: InstantRails - http://instantrails.rubyforge.org/wiki/wiki.pl

An all in one, single click installer for Windows that includes a Rails server.

Mac: Locomotive - http://locomotive.raaum.org/

'''''Rails Projects''''' - http://www.workingwithrails.com/

A Database of Rails projects, programmers and websites

'''''Rails plugins''''' - http://agilewebdevelopment.com/

A collection of Rails open source plugins, searchable by category or keyword.

'''''Sample Rails''''' - http://snippets.dzone.com/tag/rails

A collection of Rails code snippets.

'''''Agile Rails book''''' - http://www.amazon.com/gp/product/097669400X/002-0481267-8083260?v=glance&n=283155

An excellent resource for learning how to apply Agile programming concepts to Rails.

'''''Rails cheatsheet''''' - http://www.blainekendall.com/uploads/RubyOnRails-Cheatsheet-BlaineKendall.pdf

One user's list of best practices, gotchas and quirks of developing with Rails.

'''''Rails best practices''''' - http://www.therailsway.com/

An official best practices list for programming in Rails.

'''''Advanced Rails''''' - http://webonrails.com/

A resource for the advanced Rails programmer.

'''''Rails Blog''''' - http://weblog.rubyonrails.org/

An online community of updates about current happenings with the Rails platform.

'''''Rails Guides''''' - http://guides.rubyonrails.org/

An all in one resource for learning Rails including Howtos, security and contributing to the Rails community.

'''''Authoring Rails plugins''''' - http://nubyonrails.com/articles/2006/05/04/the-complete-guide-to-rails-plugins-part-i

A complete guide to authoring your own Rails plugins.

'''

== '''Tools for Rails (other than IDEs)''' ==
'''

'''Test Unit'''
The Rails stack uses Test::Unit, known as the default Ruby unit testing framework shipping with Ruby. There are various plugins and extension that could be used with Rails built-in Test::Unit to extend its functionality for support of TDD and BDD testing practices.

[http://wiki.rubyonrails.org/addons/testing]
The link provides additional information in the form of supporting resources, whitepapers, examples, and plug-in documentation

'''Example'''
[http://wiki.rubyonrails.org/testing/test-unitrequire]

Image:class CalculatorTest < Test::Unit::TestCase
def test_add_two_numbers_for_the_sum
calculator = Calculator.new
assert_equal 4, calculator.sum(2, 2)
end
end

== TDD: Test Driven Development ==

Test Driven Development is a combination of refactoring and test first development, a form of development where the test is

written prior to completed production code. The goal of TDD is the specification of requirements and not the validation of

requirements. There are a few testing frameworks that are used to implement the TDD programming technique.

[http://ruby.about.com/b/2009/01/28/test-driven-development-with-rails.htm]
This link provides a comprehensive overview of test driven development practices and available resources for implementation.

'''RSpec'''
RSpec is a testing framework for Behavior Driven Development, complete with its own expectations, matchers and mocking and

stubbing facilities. It goes along hand in hand with Cucumber, though it plays nicely with many other testing frameworks as well.

'''Model Examples'''
These are the equivalent of unit tests in Rails’ built in testing. Ironically
(for the traditional TDD’er) these are the only specs that we feel should actually interact
with the database. Learn more ….

'''Controller Examples'''
These align somewhat with functional tests in rails, except
that they do not actually render views (though you can force rendering of views
if you prefer). Instead of setting expectations about what goes on a page, you
set expectations about what templates get rendered. Learn more….

'''View Examples'''
This is the other half of Rails’ functional testing. View specs allow
you to set up assigns (thanks to ZenTest). Learn more ….

'''Helper Examples'''
let you specify directly methods that live in your helpers. Learn more ….

[http://www.ibm.com/developerworks/web/library/wa-rspec/]
The link provides a brief overview of RSpec with a comprehensive series of examples and a conceptual view of Rpecs step by step

implementation process

'''Cucumber'''
Cucumber is used with TDD and BDD within other testing frameworks such as RSpec by letting software development teams describe how

software should behave in plain text. The text is written in a business-readable domain-specific language and serves as

documentation, automated tests and development-aid - all rolled into one format.

[http://cukes.info/]
The link provides a detail decription, definition, and examples of Cucumber implementation best practices and supported

frameworks.

'''Cucumber Example:'''
Scenario: See all vendors
Given I am logged in as a user in the administrator role
And There are 3 vendors
When I go to the manage vendors page
Then I should see the first 3 vendor names

'''Shoulda'''
An extension to Test::Unit with additional helpers, macros, and assertions.

[http://www.thoughtbot.com/projects/shoulda]
The link provides a more conclusive definition of Shoulda along with installation facts and working examples of the Shoulda

testing framework within Ruby's built in Test::Unit

== BDD: Behavior Driven Development ==
[http://eggsonbread.com/2009/07/22/behavior-driven-development-in-a-nutshell/]
Behavior driven development was born from the concepts behind the implementation of TDD. It brings together strands from

TestDrivenDevelopment and DomainDrivenDesign into an integrated whole, making the relationship between these two powerful

approaches to software development more evident. Most test driven development testing frameworks such as RSpec and Cucumber also support behavior driven development testing.

[http://behaviour-driven.org/]
The link supports BDDs definition with additional links to more viable behavior driven development resources.

----

'''Other Test Tool Resources'''
Watir
Watir is an open-source library for automating web browsers. It allows you to write tests that are easy to read and maintain. It

is simple and flexible.

[http://wtr.rubyforge.org/]

'''NullDB''' - http://avdi.org/projects/nulldb/
a way to speed up testing by avoiding database use.

'''Bleakhouse:''' memory leak detection

'''ruby-debug'''
Other than the extensive use of breakpoints, ruby-debug provides Rails with a plug-in extending the functionality of Rails built in debugger.

'''http://rubyforge.org/softwaremap/trove_list.php?form_cat=47'''
The link provides twenty debug resources available for RoR

== '''Conclusion''' ==

== Reference ==

All sources used to create this wiki are linked in the above text.

CSC/ECE 517 Fall 2009/wiki1b team1

2009-09-21T02:33:44Z

Los Bravo: /* '''Conclusion''' */

CSC/ECE 517 Fall 2009

'''
== Resources for Rails (other than IDEs) ==
'''

IDEs are a valuable resource for Rails development, however there are many other resources and tools
that can either replace or supplement IDEs.

'''Resources for Rails other than IDEs
'''

'''''Rails API''''' - http://api.rubyonrails.org/

This site documents Rails files, classes and methods that can be used to build a Rails application.

'''''Rails Forum''''' - http://railsforum.com/

A discussion forum covering all aspects of Rails for beginners and experts including planning,
programming, extensions and production.

'''''Introducing Ruby on Rails'''''

Part 1 http://www.softwaredeveloper.com/features/intro-to-ruby-on-rails-042507/

Part 2 http://www.softwaredeveloper.com/features/intro-to-ruby-on-rails-part-two-043007/

An excellent introduction to Rails for novices

'''''Installers'''
''

Windows: InstantRails - http://instantrails.rubyforge.org/wiki/wiki.pl

An all in one, single click installer for Windows that includes a Rails server.

Mac: Locomotive - http://locomotive.raaum.org/

'''''Rails Projects''''' - http://www.workingwithrails.com/

A Database of Rails projects, programmers and websites

'''''Rails plugins''''' - http://agilewebdevelopment.com/

A collection of Rails open source plugins, searchable by category or keyword.

'''''Sample Rails''''' - http://snippets.dzone.com/tag/rails

A collection of Rails code snippets.

'''''Agile Rails book''''' - http://www.amazon.com/gp/product/097669400X/002-0481267-8083260?v=glance&n=283155

An excellent resource for learning how to apply Agile programming concepts to Rails.

'''''Rails cheatsheet''''' - http://www.blainekendall.com/uploads/RubyOnRails-Cheatsheet-BlaineKendall.pdf

One user's list of best practices, gotchas and quirks of developing with Rails.

'''''Rails best practices''''' - http://www.therailsway.com/

An official best practices list for programming in Rails.

'''''Advanced Rails''''' - http://webonrails.com/

A resource for the advanced Rails programmer.

'''''Rails Blog''''' - http://weblog.rubyonrails.org/

An online community of updates about current happenings with the Rails platform.

'''''Rails Guides''''' - http://guides.rubyonrails.org/

An all in one resource for learning Rails including Howtos, security and contributing to the Rails community.

'''''Authoring Rails plugins''''' - http://nubyonrails.com/articles/2006/05/04/the-complete-guide-to-rails-plugins-part-i

A complete guide to authoring your own Rails plugins.

'''

== '''Tools for Rails (other than IDEs)''' ==
'''

'''Test Unit'''
The Rails stack uses Test::Unit, known as the default Ruby unit testing framework shipping with Ruby. There are various plugins and extension that could be used with Rails built-in Test::Unit to extend its functionality for support of TDD and BDD testing practices.

[http://wiki.rubyonrails.org/addons/testing]
The link provides additional information in the form of supporting resources, whitepapers, examples, and plug-in documentation

'''Example'''
[http://wiki.rubyonrails.org/testing/test-unitrequire]

Image:class CalculatorTest < Test::Unit::TestCase
def test_add_two_numbers_for_the_sum
calculator = Calculator.new
assert_equal 4, calculator.sum(2, 2)
end
end

== TDD: Test Driven Development ==

Test Driven Development is a combination of refactoring and test first development, a form of development where the test is

written prior to completed production code. The goal of TDD is the specification of requirements and not the validation of

requirements. There are a few testing frameworks that are used to implement the TDD programming technique.

[http://ruby.about.com/b/2009/01/28/test-driven-development-with-rails.htm]
This link provides a comprehensive overview of test driven development practices and available resources for implementation.

'''RSpec'''
RSpec is a testing framework for Behavior Driven Development, complete with its own expectations, matchers and mocking and

stubbing facilities. It goes along hand in hand with Cucumber, though it plays nicely with many other testing frameworks as well.

'''Model Examples'''
These are the equivalent of unit tests in Rails’ built in testing. Ironically
(for the traditional TDD’er) these are the only specs that we feel should actually interact
with the database. Learn more ….

'''Controller Examples'''
These align somewhat with functional tests in rails, except
that they do not actually render views (though you can force rendering of views
if you prefer). Instead of setting expectations about what goes on a page, you
set expectations about what templates get rendered. Learn more….

'''View Examples'''
This is the other half of Rails’ functional testing. View specs allow
you to set up assigns (thanks to ZenTest). Learn more ….

'''Helper Examples'''
let you specify directly methods that live in your helpers. Learn more ….

[http://www.ibm.com/developerworks/web/library/wa-rspec/]
The link provides a brief overview of RSpec with a comprehensive series of examples and a conceptual view of Rpecs step by step

implementation process

'''Cucumber'''
Cucumber is used with TDD and BDD within other testing frameworks such as RSpec by letting software development teams describe how

software should behave in plain text. The text is written in a business-readable domain-specific language and serves as

documentation, automated tests and development-aid - all rolled into one format.

[http://cukes.info/]
The link provides a detail decription, definition, and examples of Cucumber implementation best practices and supported

frameworks.

'''Cucumber Example:'''
Scenario: See all vendors
Given I am logged in as a user in the administrator role
And There are 3 vendors
When I go to the manage vendors page
Then I should see the first 3 vendor names

'''Shoulda'''
An extension to Test::Unit with additional helpers, macros, and assertions.

[http://www.thoughtbot.com/projects/shoulda]
The link provides a more conclusive definition of Shoulda along with installation facts and working examples of the Shoulda

testing framework within Ruby's built in Test::Unit

== BDD: Behavior Driven Development ==
[http://eggsonbread.com/2009/07/22/behavior-driven-development-in-a-nutshell/]
Behavior driven development was born from the concepts behind the implementation of TDD. It brings together strands from

TestDrivenDevelopment and DomainDrivenDesign into an integrated whole, making the relationship between these two powerful

approaches to software development more evident. Most test driven development testing frameworks such as RSpec and Cucumber also support behavior driven development testing.

[http://behaviour-driven.org/]
The link supports BDDs definition with additional links to more viable behavior driven development resources.

----

'''Other Test Tool Resources'''
Watir
Watir is an open-source library for automating web browsers. It allows you to write tests that are easy to read and maintain. It

is simple and flexible.

[http://wtr.rubyforge.org/]

'''NullDB''' - http://avdi.org/projects/nulldb/
a way to speed up testing by avoiding database use.

'''Bleakhouse:''' memory leak detection

'''ruby-debug'''
Other than the extensive use of breakpoints, ruby-debug provides Rails with a plug-in extending the functionality of Rails built in debugger.

'''http://rubyforge.org/softwaremap/trove_list.php?form_cat=47'''
The link provides twenty debug resources available for RoR

== '''Conclusion''' ==

== '''Reference''' ==

All sources used to create this wiki are linked in the above text.

CSC/ECE 517 Fall 2009/wiki1b team1

2009-09-21T02:30:28Z

Los Bravo: /* Conclusion */

CSC/ECE 517 Fall 2009

'''
== Resources for Rails (other than IDEs) ==
'''

IDEs are a valuable resource for Rails development, however there are many other resources and tools
that can either replace or supplement IDEs.

'''Resources for Rails other than IDEs
'''

'''''Rails API''''' - http://api.rubyonrails.org/

This site documents Rails files, classes and methods that can be used to build a Rails application.

'''''Rails Forum''''' - http://railsforum.com/

A discussion forum covering all aspects of Rails for beginners and experts including planning,
programming, extensions and production.

'''''Introducing Ruby on Rails'''''

Part 1 http://www.softwaredeveloper.com/features/intro-to-ruby-on-rails-042507/

Part 2 http://www.softwaredeveloper.com/features/intro-to-ruby-on-rails-part-two-043007/

An excellent introduction to Rails for novices

'''''Installers'''
''

Windows: InstantRails - http://instantrails.rubyforge.org/wiki/wiki.pl

An all in one, single click installer for Windows that includes a Rails server.

Mac: Locomotive - http://locomotive.raaum.org/

'''''Rails Projects''''' - http://www.workingwithrails.com/

A Database of Rails projects, programmers and websites

'''''Rails plugins''''' - http://agilewebdevelopment.com/

A collection of Rails open source plugins, searchable by category or keyword.

'''''Sample Rails''''' - http://snippets.dzone.com/tag/rails

A collection of Rails code snippets.

'''''Agile Rails book''''' - http://www.amazon.com/gp/product/097669400X/002-0481267-8083260?v=glance&n=283155

An excellent resource for learning how to apply Agile programming concepts to Rails.

'''''Rails cheatsheet''''' - http://www.blainekendall.com/uploads/RubyOnRails-Cheatsheet-BlaineKendall.pdf

One user's list of best practices, gotchas and quirks of developing with Rails.

'''''Rails best practices''''' - http://www.therailsway.com/

An official best practices list for programming in Rails.

'''''Advanced Rails''''' - http://webonrails.com/

A resource for the advanced Rails programmer.

'''''Rails Blog''''' - http://weblog.rubyonrails.org/

An online community of updates about current happenings with the Rails platform.

'''''Rails Guides''''' - http://guides.rubyonrails.org/

An all in one resource for learning Rails including Howtos, security and contributing to the Rails community.

'''''Authoring Rails plugins''''' - http://nubyonrails.com/articles/2006/05/04/the-complete-guide-to-rails-plugins-part-i

A complete guide to authoring your own Rails plugins.

'''

== '''Tools for Rails (other than IDEs)''' ==
'''

'''Test Unit'''
The Rails stack uses Test::Unit, known as the default Ruby unit testing framework shipping with Ruby. There are various plugins and extension that could be used with Rails built-in Test::Unit to extend its functionality for support of TDD and BDD testing practices.

[http://wiki.rubyonrails.org/addons/testing]
The link provides additional information in the form of supporting resources, whitepapers, examples, and plug-in documentation

'''Example'''
[http://wiki.rubyonrails.org/testing/test-unitrequire]

Image:class CalculatorTest < Test::Unit::TestCase
def test_add_two_numbers_for_the_sum
calculator = Calculator.new
assert_equal 4, calculator.sum(2, 2)
end
end

== TDD: Test Driven Development ==

Test Driven Development is a combination of refactoring and test first development, a form of development where the test is

written prior to completed production code. The goal of TDD is the specification of requirements and not the validation of

requirements. There are a few testing frameworks that are used to implement the TDD programming technique.

[http://ruby.about.com/b/2009/01/28/test-driven-development-with-rails.htm]
This link provides a comprehensive overview of test driven development practices and available resources for implementation.

'''RSpec'''
RSpec is a testing framework for Behavior Driven Development, complete with its own expectations, matchers and mocking and

stubbing facilities. It goes along hand in hand with Cucumber, though it plays nicely with many other testing frameworks as well.

'''Model Examples'''
These are the equivalent of unit tests in Rails’ built in testing. Ironically
(for the traditional TDD’er) these are the only specs that we feel should actually interact
with the database. Learn more ….

'''Controller Examples'''
These align somewhat with functional tests in rails, except
that they do not actually render views (though you can force rendering of views
if you prefer). Instead of setting expectations about what goes on a page, you
set expectations about what templates get rendered. Learn more….

'''View Examples'''
This is the other half of Rails’ functional testing. View specs allow
you to set up assigns (thanks to ZenTest). Learn more ….

'''Helper Examples'''
let you specify directly methods that live in your helpers. Learn more ….

[http://www.ibm.com/developerworks/web/library/wa-rspec/]
The link provides a brief overview of RSpec with a comprehensive series of examples and a conceptual view of Rpecs step by step

implementation process

'''Cucumber'''
Cucumber is used with TDD and BDD within other testing frameworks such as RSpec by letting software development teams describe how

software should behave in plain text. The text is written in a business-readable domain-specific language and serves as

documentation, automated tests and development-aid - all rolled into one format.

[http://cukes.info/]
The link provides a detail decription, definition, and examples of Cucumber implementation best practices and supported

frameworks.

'''Cucumber Example:'''
Scenario: See all vendors
Given I am logged in as a user in the administrator role
And There are 3 vendors
When I go to the manage vendors page
Then I should see the first 3 vendor names

'''Shoulda'''
An extension to Test::Unit with additional helpers, macros, and assertions.

[http://www.thoughtbot.com/projects/shoulda]
The link provides a more conclusive definition of Shoulda along with installation facts and working examples of the Shoulda

testing framework within Ruby's built in Test::Unit

== BDD: Behavior Driven Development ==
[http://eggsonbread.com/2009/07/22/behavior-driven-development-in-a-nutshell/]
Behavior driven development was born from the concepts behind the implementation of TDD. It brings together strands from

TestDrivenDevelopment and DomainDrivenDesign into an integrated whole, making the relationship between these two powerful

approaches to software development more evident. Most test driven development testing frameworks such as RSpec and Cucumber also support behavior driven development testing.

[http://behaviour-driven.org/]
The link supports BDDs definition with additional links to more viable behavior driven development resources.

----

'''Other Test Tool Resources'''
Watir
Watir is an open-source library for automating web browsers. It allows you to write tests that are easy to read and maintain. It

is simple and flexible.

[http://wtr.rubyforge.org/]

'''NullDB''' - http://avdi.org/projects/nulldb/
a way to speed up testing by avoiding database use.

'''Bleakhouse:''' memory leak detection

'''ruby-debug'''
Other than the extensive use of breakpoints, ruby-debug provides Rails with a plug-in extending the functionality of Rails built in debugger.

'''http://rubyforge.org/softwaremap/trove_list.php?form_cat=47'''
The link provides twenty debug resources available for RoR

== '''Conclusion''' ==

CSC/ECE 517 Fall 2009/wiki1b team1

2009-09-21T02:29:37Z

Los Bravo: /* Tools for Rails (other than IDEs) */

CSC/ECE 517 Fall 2009

'''
== Resources for Rails (other than IDEs) ==
'''

IDEs are a valuable resource for Rails development, however there are many other resources and tools
that can either replace or supplement IDEs.

'''Resources for Rails other than IDEs
'''

'''''Rails API''''' - http://api.rubyonrails.org/

This site documents Rails files, classes and methods that can be used to build a Rails application.

'''''Rails Forum''''' - http://railsforum.com/

A discussion forum covering all aspects of Rails for beginners and experts including planning,
programming, extensions and production.

'''''Introducing Ruby on Rails'''''

Part 1 http://www.softwaredeveloper.com/features/intro-to-ruby-on-rails-042507/

Part 2 http://www.softwaredeveloper.com/features/intro-to-ruby-on-rails-part-two-043007/

An excellent introduction to Rails for novices

'''''Installers'''
''

Windows: InstantRails - http://instantrails.rubyforge.org/wiki/wiki.pl

An all in one, single click installer for Windows that includes a Rails server.

Mac: Locomotive - http://locomotive.raaum.org/

'''''Rails Projects''''' - http://www.workingwithrails.com/

A Database of Rails projects, programmers and websites

'''''Rails plugins''''' - http://agilewebdevelopment.com/

A collection of Rails open source plugins, searchable by category or keyword.

'''''Sample Rails''''' - http://snippets.dzone.com/tag/rails

A collection of Rails code snippets.

'''''Agile Rails book''''' - http://www.amazon.com/gp/product/097669400X/002-0481267-8083260?v=glance&n=283155

An excellent resource for learning how to apply Agile programming concepts to Rails.

'''''Rails cheatsheet''''' - http://www.blainekendall.com/uploads/RubyOnRails-Cheatsheet-BlaineKendall.pdf

One user's list of best practices, gotchas and quirks of developing with Rails.

'''''Rails best practices''''' - http://www.therailsway.com/

An official best practices list for programming in Rails.

'''''Advanced Rails''''' - http://webonrails.com/

A resource for the advanced Rails programmer.

'''''Rails Blog''''' - http://weblog.rubyonrails.org/

An online community of updates about current happenings with the Rails platform.

'''''Rails Guides''''' - http://guides.rubyonrails.org/

An all in one resource for learning Rails including Howtos, security and contributing to the Rails community.

'''''Authoring Rails plugins''''' - http://nubyonrails.com/articles/2006/05/04/the-complete-guide-to-rails-plugins-part-i

A complete guide to authoring your own Rails plugins.

'''

== '''Tools for Rails (other than IDEs)''' ==
'''

'''Test Unit'''
The Rails stack uses Test::Unit, known as the default Ruby unit testing framework shipping with Ruby. There are various plugins and extension that could be used with Rails built-in Test::Unit to extend its functionality for support of TDD and BDD testing practices.

[http://wiki.rubyonrails.org/addons/testing]
The link provides additional information in the form of supporting resources, whitepapers, examples, and plug-in documentation

'''Example'''
[http://wiki.rubyonrails.org/testing/test-unitrequire]

Image:class CalculatorTest < Test::Unit::TestCase
def test_add_two_numbers_for_the_sum
calculator = Calculator.new
assert_equal 4, calculator.sum(2, 2)
end
end

== TDD: Test Driven Development ==

Test Driven Development is a combination of refactoring and test first development, a form of development where the test is

written prior to completed production code. The goal of TDD is the specification of requirements and not the validation of

requirements. There are a few testing frameworks that are used to implement the TDD programming technique.

[http://ruby.about.com/b/2009/01/28/test-driven-development-with-rails.htm]
This link provides a comprehensive overview of test driven development practices and available resources for implementation.

'''RSpec'''
RSpec is a testing framework for Behavior Driven Development, complete with its own expectations, matchers and mocking and

stubbing facilities. It goes along hand in hand with Cucumber, though it plays nicely with many other testing frameworks as well.

'''Model Examples'''
These are the equivalent of unit tests in Rails’ built in testing. Ironically
(for the traditional TDD’er) these are the only specs that we feel should actually interact
with the database. Learn more ….

'''Controller Examples'''
These align somewhat with functional tests in rails, except
that they do not actually render views (though you can force rendering of views
if you prefer). Instead of setting expectations about what goes on a page, you
set expectations about what templates get rendered. Learn more….

'''View Examples'''
This is the other half of Rails’ functional testing. View specs allow
you to set up assigns (thanks to ZenTest). Learn more ….

'''Helper Examples'''
let you specify directly methods that live in your helpers. Learn more ….

[http://www.ibm.com/developerworks/web/library/wa-rspec/]
The link provides a brief overview of RSpec with a comprehensive series of examples and a conceptual view of Rpecs step by step

implementation process

'''Cucumber'''
Cucumber is used with TDD and BDD within other testing frameworks such as RSpec by letting software development teams describe how

software should behave in plain text. The text is written in a business-readable domain-specific language and serves as

documentation, automated tests and development-aid - all rolled into one format.

[http://cukes.info/]
The link provides a detail decription, definition, and examples of Cucumber implementation best practices and supported

frameworks.

'''Cucumber Example:'''
Scenario: See all vendors
Given I am logged in as a user in the administrator role
And There are 3 vendors
When I go to the manage vendors page
Then I should see the first 3 vendor names

'''Shoulda'''
An extension to Test::Unit with additional helpers, macros, and assertions.

[http://www.thoughtbot.com/projects/shoulda]
The link provides a more conclusive definition of Shoulda along with installation facts and working examples of the Shoulda

testing framework within Ruby's built in Test::Unit

== BDD: Behavior Driven Development ==
[http://eggsonbread.com/2009/07/22/behavior-driven-development-in-a-nutshell/]
Behavior driven development was born from the concepts behind the implementation of TDD. It brings together strands from

TestDrivenDevelopment and DomainDrivenDesign into an integrated whole, making the relationship between these two powerful

approaches to software development more evident. Most test driven development testing frameworks such as RSpec and Cucumber also support behavior driven development testing.

[http://behaviour-driven.org/]
The link supports BDDs definition with additional links to more viable behavior driven development resources.

----

'''Other Test Tool Resources'''
Watir
Watir is an open-source library for automating web browsers. It allows you to write tests that are easy to read and maintain. It

is simple and flexible.

[http://wtr.rubyforge.org/]

'''NullDB''' - http://avdi.org/projects/nulldb/
a way to speed up testing by avoiding database use.

'''Bleakhouse:''' memory leak detection

'''ruby-debug'''
Other than the extensive use of breakpoints, ruby-debug provides Rails with a plug-in extending the functionality of Rails built in debugger.

'''http://rubyforge.org/softwaremap/trove_list.php?form_cat=47'''
The link provides twenty debug resources available for RoR

== Conclusion ==

CSC/ECE 517 Fall 2009/wiki1b team1

2009-09-21T02:28:57Z

Los Bravo: /* Tools for Rails (other than IDEs) */

CSC/ECE 517 Fall 2009

'''
== Resources for Rails (other than IDEs) ==
'''

IDEs are a valuable resource for Rails development, however there are many other resources and tools
that can either replace or supplement IDEs.

'''Resources for Rails other than IDEs
'''

'''''Rails API''''' - http://api.rubyonrails.org/

This site documents Rails files, classes and methods that can be used to build a Rails application.

'''''Rails Forum''''' - http://railsforum.com/

A discussion forum covering all aspects of Rails for beginners and experts including planning,
programming, extensions and production.

'''''Introducing Ruby on Rails'''''

Part 1 http://www.softwaredeveloper.com/features/intro-to-ruby-on-rails-042507/

Part 2 http://www.softwaredeveloper.com/features/intro-to-ruby-on-rails-part-two-043007/

An excellent introduction to Rails for novices

'''''Installers'''
''

Windows: InstantRails - http://instantrails.rubyforge.org/wiki/wiki.pl

An all in one, single click installer for Windows that includes a Rails server.

Mac: Locomotive - http://locomotive.raaum.org/

'''''Rails Projects''''' - http://www.workingwithrails.com/

A Database of Rails projects, programmers and websites

'''''Rails plugins''''' - http://agilewebdevelopment.com/

A collection of Rails open source plugins, searchable by category or keyword.

'''''Sample Rails''''' - http://snippets.dzone.com/tag/rails

A collection of Rails code snippets.

'''''Agile Rails book''''' - http://www.amazon.com/gp/product/097669400X/002-0481267-8083260?v=glance&n=283155

An excellent resource for learning how to apply Agile programming concepts to Rails.

'''''Rails cheatsheet''''' - http://www.blainekendall.com/uploads/RubyOnRails-Cheatsheet-BlaineKendall.pdf

One user's list of best practices, gotchas and quirks of developing with Rails.

'''''Rails best practices''''' - http://www.therailsway.com/

An official best practices list for programming in Rails.

'''''Advanced Rails''''' - http://webonrails.com/

A resource for the advanced Rails programmer.

'''''Rails Blog''''' - http://weblog.rubyonrails.org/

An online community of updates about current happenings with the Rails platform.

'''''Rails Guides''''' - http://guides.rubyonrails.org/

An all in one resource for learning Rails including Howtos, security and contributing to the Rails community.

'''''Authoring Rails plugins''''' - http://nubyonrails.com/articles/2006/05/04/the-complete-guide-to-rails-plugins-part-i

A complete guide to authoring your own Rails plugins.

'''

== Tools for Rails (other than IDEs) ==
'''

'''Test Unit'''
The Rails stack uses Test::Unit, known as the default Ruby unit testing framework shipping with Ruby. There are various plugins and extension that could be used with Rails built-in Test::Unit to extend its functionality for support of TDD and BDD testing practices.

[http://wiki.rubyonrails.org/addons/testing]
The link provides additional information in the form of supporting resources, whitepapers, examples, and plug-in documentation

'''Example'''
[http://wiki.rubyonrails.org/testing/test-unitrequire]

Image:class CalculatorTest < Test::Unit::TestCase
def test_add_two_numbers_for_the_sum
calculator = Calculator.new
assert_equal 4, calculator.sum(2, 2)
end
end

== TDD: Test Driven Development ==

Test Driven Development is a combination of refactoring and test first development, a form of development where the test is

written prior to completed production code. The goal of TDD is the specification of requirements and not the validation of

requirements. There are a few testing frameworks that are used to implement the TDD programming technique.

[http://ruby.about.com/b/2009/01/28/test-driven-development-with-rails.htm]
This link provides a comprehensive overview of test driven development practices and available resources for implementation.

'''RSpec'''
RSpec is a testing framework for Behavior Driven Development, complete with its own expectations, matchers and mocking and

stubbing facilities. It goes along hand in hand with Cucumber, though it plays nicely with many other testing frameworks as well.

'''Model Examples'''
These are the equivalent of unit tests in Rails’ built in testing. Ironically
(for the traditional TDD’er) these are the only specs that we feel should actually interact
with the database. Learn more ….

'''Controller Examples'''
These align somewhat with functional tests in rails, except
that they do not actually render views (though you can force rendering of views
if you prefer). Instead of setting expectations about what goes on a page, you
set expectations about what templates get rendered. Learn more….

'''View Examples'''
This is the other half of Rails’ functional testing. View specs allow
you to set up assigns (thanks to ZenTest). Learn more ….

'''Helper Examples'''
let you specify directly methods that live in your helpers. Learn more ….

[http://www.ibm.com/developerworks/web/library/wa-rspec/]
The link provides a brief overview of RSpec with a comprehensive series of examples and a conceptual view of Rpecs step by step

implementation process

'''Cucumber'''
Cucumber is used with TDD and BDD within other testing frameworks such as RSpec by letting software development teams describe how

software should behave in plain text. The text is written in a business-readable domain-specific language and serves as

documentation, automated tests and development-aid - all rolled into one format.

[http://cukes.info/]
The link provides a detail decription, definition, and examples of Cucumber implementation best practices and supported

frameworks.

'''Cucumber Example:'''
Scenario: See all vendors
Given I am logged in as a user in the administrator role
And There are 3 vendors
When I go to the manage vendors page
Then I should see the first 3 vendor names

'''Shoulda'''
An extension to Test::Unit with additional helpers, macros, and assertions.

[http://www.thoughtbot.com/projects/shoulda]
The link provides a more conclusive definition of Shoulda along with installation facts and working examples of the Shoulda

testing framework within Ruby's built in Test::Unit

== BDD: Behavior Driven Development ==
[http://eggsonbread.com/2009/07/22/behavior-driven-development-in-a-nutshell/]
Behavior driven development was born from the concepts behind the implementation of TDD. It brings together strands from

TestDrivenDevelopment and DomainDrivenDesign into an integrated whole, making the relationship between these two powerful

approaches to software development more evident. Most test driven development testing frameworks such as RSpec and Cucumber also support behavior driven development testing.

[http://behaviour-driven.org/]
The link supports BDDs definition with additional links to more viable behavior driven development resources.

----

'''Other Test Tool Resources'''
Watir
Watir is an open-source library for automating web browsers. It allows you to write tests that are easy to read and maintain. It

is simple and flexible.

[http://wtr.rubyforge.org/]

'''NullDB''' - http://avdi.org/projects/nulldb/
a way to speed up testing by avoiding database use.

'''Bleakhouse:''' memory leak detection

'''ruby-debug'''
Other than the extensive use of breakpoints, ruby-debug provides Rails with a plug-in extending the functionality of Rails built in debugger.

'''http://rubyforge.org/softwaremap/trove_list.php?form_cat=47'''
The link provides twenty debug resources available for RoR

== Conclusion ==