CSC/ECE 517 Fall 2011/ch2 2e ad - Revision history

Agalford: /* Examples */

2011-09-30T13:11:51Z

Examples

← Older revision		Revision as of 13:11, 30 September 2011
Line 171:		Line 171:
	'''TravelTime'''		'''TravelTime'''

	The ~~example~~ that we have used below is a simple travel time example. If you give it a distance between two cities it will calculate the time it will take you to travel from City A to City B. It assumes that you will be driving at 60 miles/Hr with minimal traffic on the road.		The sample that we have used below is a simple travel time example. If you give it a distance between two cities it will calculate the time it will take you to travel from City A to City B. It assumes that you will be driving at 60 miles/Hr with minimal traffic on the road.

	<pre>		<pre>

Agalford: /* Introduction */

2011-09-30T13:10:04Z

Introduction

← Older revision		Revision as of 13:10, 30 September 2011
Line 5:		Line 5:
	==Introduction==		==Introduction==

	A testing framework is used on a software project when it has grown large enough that manual debugging and system upkeep would be too time and resource intensive. The framework provides a way to automate testing to provide for low cost maintenance. The framework itself contains a set of assumptions, concepts, and tools that allow for various types of testing. Choosing the right framework depends on many factors associated with the system in development and the mindset of the developers and [http://en.wikipedia.org/wiki/Stakeholder stakeholders]. Every framework has a few basic features: A process for defining the format to express user expectations, a way to execute the tests, and a way to report the results of the test to the user Examples are provided later to help give context to the ~~examples~~ below.		A testing framework is used on a software project when it has grown large enough that manual debugging and system upkeep would be too time and resource intensive. The framework provides a way to automate testing to provide for low cost maintenance. The framework itself contains a set of assumptions, concepts, and tools that allow for various types of testing. Choosing the right framework depends on many factors associated with the system in development and the mindset of the developers and [http://en.wikipedia.org/wiki/Stakeholder stakeholders]. Every framework has a few basic features: A process for defining the format to express user expectations, a way to execute the tests, and a way to report the results of the test to the user Examples are provided later to help give context to the definitions below.

	===Definitions===		===Definitions===

Agalford: /* Introduction */

2011-09-30T13:07:47Z

Introduction

← Older revision		Revision as of 13:07, 30 September 2011
Line 5:		Line 5:
	==Introduction==		==Introduction==

	A testing framework is used on a software project when it has grown large enough that manual debugging and system upkeep would be too time and resource intensive. The framework provides a way to automate testing to provide for low cost maintenance. The framework itself contains a set of assumptions, concepts, and tools that allow for various types of testing. Choosing the right framework depends on many factors associated with the system in development and the mindset of the developers and [http://en.wikipedia.org/wiki/Stakeholder stakeholders]. Every framework has a few basic features: A process for defining the format to express user expectations, a way to execute the tests, and a way to report the results of the test to the user.		A testing framework is used on a software project when it has grown large enough that manual debugging and system upkeep would be too time and resource intensive. The framework provides a way to automate testing to provide for low cost maintenance. The framework itself contains a set of assumptions, concepts, and tools that allow for various types of testing. Choosing the right framework depends on many factors associated with the system in development and the mindset of the developers and [http://en.wikipedia.org/wiki/Stakeholder stakeholders]. Every framework has a few basic features: A process for defining the format to express user expectations, a way to execute the tests, and a way to report the results of the test to the user Examples are provided later to help give context to the examples below.

	===Definitions===		===Definitions===

Agalford: /* References */

2011-09-30T13:03:20Z

References

← Older revision		Revision as of 13:03, 30 September 2011
Line 409:		Line 409:
	* [1] Test-Unit Site [http://test-unit.rubyforge.org/ Unit testing framework]		* [1] Test-Unit Site [http://test-unit.rubyforge.org/ Unit testing framework]
	* [2] RSpec Site [http://rspec.info/ RSpec Testing]		* [2] RSpec Site [http://rspec.info/ RSpec Testing]
	* [3] Mike Gunderloy [http://www.rubyinside.com/cucumber-the-latest-in-ruby-testing-1342.html Cucumber: The Latest in Ruby Testing]		* [3] Win32-autogui Site [https://github.com/robertwahler/win32-autogui Win32-autogui on Github]
	* [4] Win32-autogui Site [https://github.com/robertwahler/win32-autogui Win32-autogui on Github]		* [4] Mike Gunderloy [http://www.rubyinside.com/cucumber-the-latest-in-ruby-testing-1342.html Cucumber: The Latest in Ruby Testing]

	==Expand your knowledge==		==Expand your knowledge==

Agalford: /* Additional Testing Frameworks */

2011-09-30T13:02:47Z

Additional Testing Frameworks

← Older revision		Revision as of 13:02, 30 September 2011
Line 394:		Line 394:
	User interface (UI) testing frameworks allow for the testing of systems within a graphical environment. This could take the form of a custom GUI written for the system to use, or leverage programs that are already developed, such as a word processor or web browser.		User interface (UI) testing frameworks allow for the testing of systems within a graphical environment. This could take the form of a custom GUI written for the system to use, or leverage programs that are already developed, such as a word processor or web browser.
	====Win32-AutoGUI====		====Win32-AutoGUI====
	Win32-AutoGUI is a framework that allows for GUI application testing of Windows binaries and Windows applications. It facilitates integration testing of these binaries using Ruby based tools like RSpec and Cucumber regardless of the language used to create the binaries.		Win32-AutoGUI is a framework that allows for GUI application testing of Windows binaries and Windows applications. It facilitates integration testing of these binaries using Ruby based tools like RSpec and Cucumber regardless of the language used to create the binaries[https://github.com/robertwahler/win32-autogui].

	===Acceptance testing===		===Acceptance testing===

Agalford: /* References */

2011-09-30T13:02:02Z

References

← Older revision		Revision as of 13:02, 30 September 2011
Line 410:		Line 410:
	* [2] RSpec Site [http://rspec.info/ RSpec Testing]		* [2] RSpec Site [http://rspec.info/ RSpec Testing]
	* [3] Mike Gunderloy [http://www.rubyinside.com/cucumber-the-latest-in-ruby-testing-1342.html Cucumber: The Latest in Ruby Testing]		* [3] Mike Gunderloy [http://www.rubyinside.com/cucumber-the-latest-in-ruby-testing-1342.html Cucumber: The Latest in Ruby Testing]
			* [4] Win32-autogui Site [https://github.com/robertwahler/win32-autogui Win32-autogui on Github]


	==Expand your knowledge==		==Expand your knowledge==

Dapatel2: /* Conclusion */

2011-09-29T13:30:00Z

Conclusion

← Older revision		Revision as of 13:30, 29 September 2011
Line 403:		Line 403:

	==Conclusion==		==Conclusion==
			As shown from above ruby testing frameworks have evolved tremendously over time and today there are many different testing frameworks that are available for testing ruby. But selection of right testing framework depends on the requirements and needs of the project. Many different factors like use of testing framework (Unit testing, Acceptance testing etc), test execution time, and Quality of test failure results contribute in selection of the best testing framework.

	==References==		==References==

Dapatel2 at 13:18, 29 September 2011

2011-09-29T13:18:40Z

← Older revision		Revision as of 13:18, 29 September 2011
Line 401:		Line 401:
	====Cucumber====		====Cucumber====
	Cucumber is designed to allow you to execute feature documentation written in plain text (often known as "stories") [http://www.rubyinside.com/cucumber-the-latest-in-ruby-testing-1342.html]. Cucumber testing framework is a basic testing framework which allows you to describe your test cases in plain English text. On the back end, you make a file with regular expressions which can parse this plain English text and perform the test case. Today cucumber is widely used in Ruby projects, especially with the RSpec testing framework.		Cucumber is designed to allow you to execute feature documentation written in plain text (often known as "stories") [http://www.rubyinside.com/cucumber-the-latest-in-ruby-testing-1342.html]. Cucumber testing framework is a basic testing framework which allows you to describe your test cases in plain English text. On the back end, you make a file with regular expressions which can parse this plain English text and perform the test case. Today cucumber is widely used in Ruby projects, especially with the RSpec testing framework.

			==Conclusion==

	==References==		==References==

Dapatel2 at 14:21, 28 September 2011

2011-09-28T14:21:12Z

← Older revision		Revision as of 14:21, 28 September 2011
Line 407:		Line 407:
	* [2] RSpec Site [http://rspec.info/ RSpec Testing]		* [2] RSpec Site [http://rspec.info/ RSpec Testing]
	* [3] Mike Gunderloy [http://www.rubyinside.com/cucumber-the-latest-in-ruby-testing-1342.html Cucumber: The Latest in Ruby Testing]		* [3] Mike Gunderloy [http://www.rubyinside.com/cucumber-the-latest-in-ruby-testing-1342.html Cucumber: The Latest in Ruby Testing]
	* [4] Dan Noth [http://behaviour-driven.org/ Behavior Driven Development]
	* [5] Dave Astels [http://blog.daveastels.com/files/BDD_Intro.pdf A new look at Test Driven Development]
	* [6] Scott W Ambler[http://www.agiledata.org/essays/tdd.html Introduction to Test Driven Design (TDD)]
	* [7] IBM [http://publib.boulder.ibm.com/infocenter/db2luw/v8/index.jsp?topic=/com.ibm.db2.udb.doc/admin/c0005059.htm Benchmark Testing]		==Expand your knowledge==
	* [8] IBM Developers Work [http://www.ibm.com/developerworks/library/j-mocktest/index.html Unit testing with mock objects]
	* [9] Steve Freeman [http://www.mockobjects.com/ Mock Objects]		* [1] Dan Noth [http://behaviour-driven.org/ Behavior Driven Development]
			* [2] Dave Astels [http://blog.daveastels.com/files/BDD_Intro.pdf A new look at Test Driven Development]
			* [3] Scott W Ambler[http://www.agiledata.org/essays/tdd.html Introduction to Test Driven Design (TDD)]
			* [4] IBM [http://publib.boulder.ibm.com/infocenter/db2luw/v8/index.jsp?topic=/com.ibm.db2.udb.doc/admin/c0005059.htm Benchmark Testing]
			* [5] IBM Developers Work [http://www.ibm.com/developerworks/library/j-mocktest/index.html Unit testing with mock objects]
			* [6] Steve Freeman [http://www.mockobjects.com/ Mock Objects]

Dapatel2: /* Test:Unit */

2011-09-28T13:05:25Z

Test:Unit

← Older revision		Revision as of 13:05, 28 September 2011
Line 89:		Line 89:

	====Test:Unit====		====Test:Unit====
	Test-Unit is one of the oldest testing frameworks for Ruby testing. Test-Unit is basically used for performing test driven development similar to how Java’s JUnit is used. It’s in a way very similar to Java’s JUnit. Test-Unit framework, when initially released, was part of the ruby distribution package. The newer version since then has been converted to gems and has been provided to developers as a standalone package. Additionally, some of the features like notify, capybara, GTK+, Tk, and FOX Toolkit have been split from the package and provided separately[http://test-unit.rubyforge.org/].		Test-Unit is one of the oldest testing frameworks for Ruby testing. Test-Unit is basically used for performing test driven development similar to how Java’s JUnit is used. It’s in a way very similar to Java’s JUnit. Test-Unit framework, when initially released, was part of the ruby distribution package. The newer version since then has been converted to gems and has been provided to developers as a standalone package. Additionally, some of the features like notify, capybara, [http://en.wikipedia.org/wiki/GTK%2B GTK+],[http://en.wikipedia.org/wiki/Tk_%28framework%29 Tk], and [http://en.wikipedia.org/wiki/Fox_toolkit FOX Toolkit] have been split from the package and provided separately[http://test-unit.rubyforge.org/].

	====RSpec====		====RSpec====