EiffelStudio: an EiffelSoftware project - User contributions [en]

Downloads

2010-05-31T06:01:23Z

Jacksonsophia:

[[Category:EiffelStudio]]
[[Category:Compiler]]
==EiffelStudio 6.x Pre-releases==
We provide versions of EiffelStudio for most popular platforms (Linux, Windows, Solaris, Irix, ...).

You can find the latest builds:
* from the download page of [http://sourceforge.net/project/showfiles.php?group_id=196408 the sourceforge area]
* as well as in [ftp://beta:beta57@ftp.eiffel.com the Eiffel Software beta area] (beware it also includes some nightly build which are untested).
* in [http://eiffelstudio.origo.ethz.ch/download the Origo download area] [http://custom-essay-writing-service.org/index.php custom writing company] for the PorterPackage.

Details about new features and bug fixes in the builds are on the [[EiffelStudio_Releases| releases page]].

{{Note|Please be aware that the 6.x versions released through this site are intermediate builds on the road towards official EiffelStudio 6.x. If you are experiencing problems with this release, please use the [http://eiffelstudio.origo.ethz.ch/forum EiffelStudio developer forums] [http://cvresumewriters.com/ cv writers] for discussions.}}

The convention used for filenames is the following:
Eiffel65_gpl_$BUILD-$ISE_PLATFORM.[tar.bz2|msi]
Where '''$BUILD''' is a build number, the higher number the more recent release it is, and where '''$ISE_PLATFORM''' is the name of your platform.

Mac OS X builds can be found [[EiffelOnMac|here]].

On Windows, you can use [[Installing_Microsoft_C_compiler|the latest Microsoft C compiler]], but EiffelStudio 6.1 needs [[Installing_Microsoft_C_compiler_6.1_and_older|an older compiler]].

==EiffelStudio 6.x==
You can download the official EiffelStudio 6.x release from [http://www.eiffel.com/downloads/eiffelstudio.html Eiffel Software]. The GPL release can also be downloaded from [http://sourceforge.net/project/showfiles.php?group_id=196408 http://sflogo.sourceforge.net/sflogo.php?group_id=196408.png].

==Doc Builder==
You can download the documentation generation tool for Windows 32-bit with .NET 1.1 installed by extracting the content of [http://download.origo.ethz.ch/eiffelstudio/174/doc_builder.zip doc_builder.zip] (or [http://download.origo.ethz.ch/eiffelstudio/174/doc_builder_64-bit.zip doc_builder_64-bit.zip] for the 64-bit version) onto your hard-drive. Once installed, you can launch the tool by launching the '''doc_builder.exe''' executable.

If you have both .NET 1.1 and .NET 2.0 (or greater), you need to force the loading of .NET 1.1. To do so, edit the file '''doc_builder.exe.config''' so that its content looks like:

<xml>
<configuration>
<startup>
<requiredRuntime version="v1.1.4322" safemode="true"/>
</startup>
<runtime>
<assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
<probing privatePath="Assemblies"/>
</assemblyBinding>
</runtime>
</configuration>
</xml>

Downloads

2010-05-31T05:59:33Z

Jacksonsophia:

[[Category:EiffelStudio]]
[[Category:Compiler]]
==EiffelStudio 6.x Pre-releases==
We provide versions of EiffelStudio for most popular platforms (Linux, Windows, Solaris, Irix, ...).

You can find the latest builds:
* from the download page of [http://sourceforge.net/project/showfiles.php?group_id=196408 the sourceforge area]
* as well as in [ftp://beta:beta57@ftp.eiffel.com the Eiffel Software beta area] (beware it also includes some nightly build which are untested).
* in [http://eiffelstudio.origo.ethz.ch/download the Origo download area] [http://custom-essay-writing-service.org/index.php custom writing company] for the PorterPackage.

Details about new features and bug fixes in the builds are on the [[EiffelStudio_Releases| releases page]].

{{Note|Please be aware that the 6.x versions released through this site are intermediate builds on the road towards official EiffelStudio 6.x. If you are experiencing problems with this release, please use the [http://eiffelstudio.origo.ethz.ch/forum EiffelStudio developer forums] [http://essaywritingservices.org/index.php writing services] for discussions.}}

The convention used for filenames is the following:
Eiffel65_gpl_$BUILD-$ISE_PLATFORM.[tar.bz2|msi]
Where '''$BUILD''' is a build number, the higher number the more recent release it is, and where '''$ISE_PLATFORM''' is the name of your platform.

Mac OS X builds can be found [[EiffelOnMac|here]].

On Windows, you can use [[Installing_Microsoft_C_compiler|the latest Microsoft C compiler]], but EiffelStudio 6.1 needs [[Installing_Microsoft_C_compiler_6.1_and_older|an older compiler]].

==EiffelStudio 6.x==
You can download the official EiffelStudio 6.x release from [http://www.eiffel.com/downloads/eiffelstudio.html Eiffel Software]. The GPL release can also be downloaded from [http://sourceforge.net/project/showfiles.php?group_id=196408 http://sflogo.sourceforge.net/sflogo.php?group_id=196408.png].

==Doc Builder==
You can download the documentation generation tool for Windows 32-bit with .NET 1.1 installed by extracting the content of [http://download.origo.ethz.ch/eiffelstudio/174/doc_builder.zip doc_builder.zip] (or [http://download.origo.ethz.ch/eiffelstudio/174/doc_builder_64-bit.zip doc_builder_64-bit.zip] for the 64-bit version) onto your hard-drive. Once installed, you can launch the tool by launching the '''doc_builder.exe''' executable.

If you have both .NET 1.1 and .NET 2.0 (or greater), you need to force the loading of .NET 1.1. To do so, edit the file '''doc_builder.exe.config''' so that its content looks like:

<xml>
<configuration>
<startup>
<requiredRuntime version="v1.1.4322" safemode="true"/>
</startup>
<runtime>
<assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
<probing privatePath="Assemblies"/>
</assemblyBinding>
</runtime>
</configuration>
</xml>

Compiling EiffelStudio

2010-05-31T05:53:03Z

Jacksonsophia:

[[Category:Compiler]]
[[Category:EiffelStudio]]

== Installing EiffelStudio ==

To compile EiffelStudio, you need an already working EiffelStudio compiler on your machine. The current source tree '''requires at least version 6.5''' of EiffelStudio. You can download it from http://dev.eiffel.com/Downloads. Read the [http://docs.eiffel.com/eiffelstudio/installation/index.html existing documentation] to install EiffelStudio.

'''Note:''' on Windows you will need the Microsoft C compiler to compile Eiffel Studio. How to install the free version of the Microsoft C compiler: [[Installing Microsoft C compiler]]. It is not possible to compile EiffelStudio with the free Borland compiler.

===Compilation methods===
Currently there are two compilation methods.
* You can compile EiffelStudio from scratch following the instructions in this document ('''This is the recommended approach''').
* You can use one of the [[Automatic Build Scripts]], and if you encounter any errors please report them to the [http://forums.eiffel.com EiffelStudio Development forum].

==Extracting source code==

===Checking out from SVN===
#Point the environment variables called '''EIFFEL_SRC''' and '''ISE_LIBRARY''' to the directory where you want to compile EiffelStudio.<br>Usually we use the '''XXdev''' convention for this directory name - where XX is the version number of the currently developed version of the compiler.
#Make sure that '''ISE_EIFFEL''', '''ISE_PLATFORM''' and '''ISE_C_COMPILER''' (on Windows only) are properly defined.
#Perform the following checkout procedures:

'''DOS'''
<pre>
set SVNURL=https://svn.eiffel.com/eiffelstudio/trunk
svn co %SVNURL%/Src 65dev
svn co %SVNURL%/Delivery 65dev/Delivery
svn co %SVNURL%/Documentation 65dev/Documentation
svn co %SVNURL%/free_add_ons 65dev/free_add_ons
</pre>

'''Bash'''
<pre>
export SVNURL=https://svn.eiffel.com/eiffelstudio/trunk
svn co $SVNURL/Src 65dev
svn co $SVNURL/Delivery 65dev/Delivery
svn co $SVNURL/Documentation 65dev/Documentation
svn co $SVNURL/free_add_ons 65dev/free_add_ons
</pre>

To update the source files to the latest revision, perform the following steps:

'''Bash and DOS'''
<pre>
cd 65dev
svn up
svn up free_add_ons
svn up Delivery
svn up Documentation
</pre>

==Compiling C libraries==

===Compiling run-time on Windows===

'''DOS'''
<pre>cd %EIFFEL_SRC%/C
configure [win32|win64] [b|g|m|m6]</pre>

'''Bash'''
<pre>cd $EIFFEL_SRC/C
./configure.bat [win32|win64] [b|g|m|m6]</pre>

The first argument indicated whether you are compiling the run-time for 32 or 64 bits. The second one is to tell which C compiler will be used. For now only `b' (Borland), `g' (MinGW), `m' (Microsoft) and `m6' (for those forced to use Microsoft VC++ 6.0) are officially supported.

On Windows 32 bits to clean up all the generated files '''(including the library files needed by EiffelStudio)''' it suffices to do:

'''DOS'''
<pre>configure clean</pre>
'''Bash'''
<pre>./configure.bat clean</pre>

===Compiling run-time on Unix===

The command is simply:
<pre>cd $EIFFEL_SRC/C
./quick_configure</pre>
This requires that '''ISE_PLATFORM''' is properly defined. The `quick_configure' script will look for the file CONFIGS/$ISE_PLATFORM and use it to extract the platform specific information to compile the run-time. If not found then an error will be reported.

To clean up the generated files '''including the library files needed by EiffelStudio''':
<pre>make clobber</pre>

===Compiling C code from libraries===

Here is the list of commands to compile all required C libraries on Windows:

'''DOS'''
<pre>cd %EIFFEL_SRC%\library\net\Clib
finish_freezing -library
cd %EIFFEL_SRC%\library\vision2\Clib
finish_freezing -library
cd %EIFFEL_SRC%\library\wel\Clib
finish_freezing -library
cd %EIFFEL_SRC%\library\cURL\Clib
finish_freezing -library</pre>
'''Bash'''
<pre>cd $EIFFEL_SRC/library/net/Clib
finish_freezing -library
cd $EIFFEL_SRC/library/vision2/Clib
finish_freezing -library
cd $EIFFEL_SRC/library/wel/Clib
finish_freezing -library
cd %EIFFEL_SRC%/library/cURL/Clib
finish_freezing -library</pre>

On Unix it is slightly different:
<pre>cd $EIFFEL_SRC/library/net/Clib
finish_freezing -library
cd $EIFFEL_SRC/library/vision2/Clib
finish_freezing -library
cd $EIFFEL_SRC/library/vision2/implementation/gtk/Clib
finish_freezing -library
cd $EIFFEL_SRC/library/cURL/Clib
finish_freezing -library</pre>

Make sure that '''ISE_EIFFEL''' is set correctly to your current "EiffelStudio" installation!

===Compiling C code from C_library===

This is only required on Windows to read PNG file. On Unix, this is not required because it is included in GTK+2.4. So on Windows, simply do the following:

'''DOS'''
<pre>cd %EIFFEL_SRC%/C_library/zlib
finish_freezing -library
cd %EIFFEL_SRC%/C_library/libpng
finish_freezing -library</pre>
'''Bash'''
<pre>cd $EIFFEL_SRC/C_library/zlib
finish_freezing -library
cd $EIFFEL_SRC/C_library/libpng
finish_freezing -library</pre>

===Compiling C code from compiler===

This is only required on Windows as this C code is a tiny wrapper [http://essaywritingservices.org/index.php writing service] around the Microsoft C++ API to generate and to debug .NET code.

To compile it, you first need to install the Microsoft .NET SDK. You can download it from their website.

After installing it, you need to update your '''LIB''' and '''INCLUDE''' environment variable to include the path the lib and include directory of the .NET Framework SDK.

Once properly installed, you can do:

'''DOS'''
<pre>cd %EIFFEL_SRC%/framework/cli_writer/Clib
finish_freezing -library
cd %EIFFEL_SRC%/framework/cli_debugger/Clib
finish_freezing -library</pre>
'''Bash'''
<pre>cd $EIFFEL_SRC/framework/cli_writer/Clib
finish_freezing -library
cd $EIFFEL_SRC/framework/cli_debugger/Clib
finish_freezing -library</pre>

==Compiling EiffelStudio==

Now that we have taken care of the C code compilation we can compile the compiler. We assume that '''ec''' is in your path.

The configuration file of the compiler contains two active targets:
* '''batch''': for the command line compiler.
* '''bench''': for the graphical compiler, aka EiffelStudio.

Go to $EIFFEL_SRC/Eiffel/Ace and type the following command and replace ''target_name'' with either '''batch''' or '''bench'''.

<pre>ec -config ec.ecf -target target_name -c_compile</pre>

===Mac OS X specific===

Get a mac binary from [[EiffelOnMac|here]], then follow the instructions for unix.

==Launching the Compiler==

There are two ways of launching the compiler for [http://cvresumewriters.com/ cv writers]:
# Command line compiler: add the following arguments '''-config path_to_config_file.ecf'''. This will compile the project represented by `path_to_config_file.ecf'
# Graphical compiler (aka EiffelStudio): add the following argument '''-gui'''.

CddBranch

2010-05-31T05:50:10Z

Jacksonsophia:

[[Category:Testing]]
[[Category:EiffelDebugger]]
[[Category:CDD]]

== What is the CDD EiffelStudio? ==

[[Image:cdd_logo.png|center]]
<center>
[http://se.ethz.ch/people/leitner/cdd/video/ '''Play CDD Video''', click here]
</center>
CDD (short for Contract Driven Development) is a project developed at [http://se.ethz.ch ETH Zurich]. It adds advanced support for unit testing to EiffelStudio. With CDD EiffelStudio you can

* Write test cases
* Manage test cases (using tags)
* Run test cases
* View test outcomes
* '''Automatically extract test cases'''

If you have questions, feedback, or would like to report a bug please visit the [http://eiffelstudio.origo.ethz.ch/forum/20 CDD forum].

CDD EiffelStudio adds the following panel to regular EiffelStudio:

[[Image:cdd_panel.png|center]]

== Publications ==

Leitner, A., Ciupa, I., Oriol, M., Meyer, B., Fiva, A., "Contract Driven Development = Test Driven Development - Writing Test Cases", in Proceedings of ESEC/FSE'07: European Software Engineering Conference and the ACM SIGSOFT Symposium on the Foundations of Software Engineering 2007, (Dubrovnik, Croatia), September 2007 [http://se.ethz.ch/people/leitner/publications/cdd_leitner_esec_fse_2007.pdf pdf] [http://se.ethz.ch/people/leitner/publications/ESEC_FSE2007.bib.txt bibtex]

Leitner, A., Pretschner A., Mori S., Meyer B., Oriol M., "On the Effectiveness of Test Extraction without Overhead", under submission

== News ==
14.May 2008: Added patch for Windows and Linux that fixes a bug that can cause a crash during extraction.

10.April 2008: If installation exits with cryptic error codes, please have a look at the [[CDD Common Problems|Common Problems]] page.

08.April 2008: CDD EiffelStudio final 7 available
* Important bug fix: EiffelStudio no longer freezes when opening projects with many test cases

02.April 2008: CDD EiffelStudio Final 6 available
* Less mess: Redundant or duplicate test cases are no longer extracted
* Smoother upgrade: Cleaning a project will automatically clean the test suite
* Fixed bug in invarant checking
* Fixed bug that caused EiffelStudio to freeze in some situations
* Improved logging
* Installer ''might'' work with mingw on Windows now. (Not yet tested, reports welcome)

== Download CDD ==

The following packages contain the full EiffelStudio 6.1 plus the CDD extension. You do not need to have EiffelStudio installed already in order to install below packages. On Windows you do have to have either the Platform SDK or Visual C++ installed. Do not use EiffelStudio with the gcc/mingw or the .Net backend.

=== Linux ===
* Full Linux version: http://se.ethz.ch/people/leitner/cdd/Eiffel61_cdd_final_7.tar.bz2
* Full Linux version (for Debian stable): http://se.ethz.ch/people/leitner/cdd/Eiffel61_cdd_final_7_debian_stable.tar.bz2
* Installation instructions: http://docs.eiffel.com/eiffelstudio/installation/studio/060_linux.html
Notes:
* If you are '''upgrading''' from a previous version, make sure you delete the old version first (rm -rf)

Download the above file and install it just like you would install a EiffelStudio tar ball. Afterwards proceed to section "Using CDD". Make sure you set/update the environment variables PATH, ISE_EIFFEL, and ISE_PLATFORM according to the installation instructions.

=== Linux Patch ===
* Patch for CDD EiffelStudio Final 7: Download http://se.ethz.ch/people/leitner/cdd/ec and replace it with the '$ISE_EIFFEL/studio/spec/linux-x86/bin/ec' from Final 7. This patch fixes a crash that sometimes occurs during extraction of test cases. You may need to delete the precompile and EIFGENs of your project after applying the patch.

=== Windows ===

* Full Windows version (with installer): http://n.ethz.ch/~moris/download/Eiffel61_cdd_final_7-windows.msi
Notes:
* Installation is independent of installations of official EiffelStudio 6.1 (neither overwrites nor invalidates nor is influenced by those)
* If you are '''upgrading''' from a previous version, you first have to uninstall the old version then delete the existing precompilations (= delete EIFGENs in subdirectories of <INSTALL_DIRECTORY>/precomp/spec/windows/) and then install the new version.
* Which C compiler to install?
** Use the Microsoft C compiler either from Visual Studio or the Windows SDK:
*** Visual Studio (up to Visual Studio 2005, but no later, and only the non-express version)
*** Windows SDK (up to version 6.0, but no later)
** Do not use the gcc/mingw.
** Do not use the .NET compiler backend.

Have a look at http://dev.eiffel.com/Installing_Microsoft_C_compiler_6.1_and_older to learn how to install either Visual C++ or the Windows SDK for use with EiffelStudio.

==== Windows Patch ====

* Patch for CDD EiffelStudio Final 7: Download http://se.ethz.ch/people/leitner/cdd/ec.exe and replace it with the '$ISE_EIFFEL/studio/spec/windows/bin/ec.exe' from Final 7. This patch fixes a crash that sometimes occurs during extraction of test cases. You may need to delete the precompile and EIFGENs of your project after applying the patch.

== Documentation ==

=== Manually Written Test Cases ===
CDD Eiffelstudio allows you to create a new “empty” test case. These test cases are similar to jUnit test cases. A manually written test class must start with the word “TEST” and all test routines also have to start with the word “test”. It also has to inherit from class CDD_TEST_CASE.

=== Extracted Test Cases ===
CDD EiffelStudio automatically extracts test cases whenever you run your program and an exception is triggered. This feature is novel and not yet part of any other testing environment. You will be the first to try it out.

=== Test outcomes ===
A test case checks whether your program contains a particular bug. A test cases can fail indicating that the bug is present in your program, or pass indicating your program does not contain this bug. Sometimes test cases will be unresolved, in which case the testing framework was unable to find out whether the test case passed or failed. A test case can be unresolved for several reasons.

[[Image:cdd_buttons.png|center]]

=== Debug Test Case ===
Select a test case and press this button to run a test case in the debugger.

=== Enable/Disable Execution of Test Cases in Background ===
If enabled, all test cases are retested every time you press compile. If disabled no test cases are executed.

=== Enable/Disable automatic extraction of Test Cases ===
If enabled every time an exception is triggered a set of test cases that try to reproduce this exception is extracted. If disabled no test cases are extracted.

=== Clean up/Delete ===
You can use the “Clean Up/Delete” button in two different ways. By simply pressing it you will delete all unresolved test cases. By pick and dropping a test case to the “Clean up/Delete” button (right click on test case, move mouse to button and right click again) you can delete a test case. By the way, test cases are just regular classes. So you can use all existing tools that apply to classes in EiffelStudio too.

Update: To remove duplicate test cases (until the next cdd update), please use the command-line tool from the [http://clean-cdd.origo.ethz.ch/ clean-cdd project].

=== Create new manual test class ===
Press this button to create a empty test class. You can then edit the class to add manually written test cases. This is how a manually written test case can look like:

<eiffel>
class TEST_BANK_ACCOUNT
inherit CDD_TEST_CASE
feature
test_deposit
local
ba: BANK_ACCOUNT
do
create ba.make_with_balance (0)
ba.deposit (100)
check
money_depisited: ba.balance = 100
end
end
end
</eiffel>

Redefine routine `set_up' or `tear_down' if you want something to be executed before resp. after every test routine of a class.

[[Image:cdd_buttons_2.png|center]]

=== Search for tags ===
Enter keywords through [http://essaywritingservices.org/index.php writing services] to search for paritcular test cases. Some tags are automatically set for you like the name of the test case. You can also easily add your own tags by adding an indexing item "tag" to your test class or routine:

<eiffel>
indexing
tag: "fixme"
class TEST_BANK_ACCOUNT
inherit CDD_TEST_CASE
feature
...
end
</eiffel>

Tags can be adde to all test routines and classes. Whether they are extracted or manually written does not matter.

=== Restrict execution of test cases ===

Once you have many test cases, you will run into situation where you don't want to execute all of them. The restrict button will help you to achieve this. As long as the "Restrict" button is pushed test cases that don't show up in the test case view will not be tested. Execution is restricted to those test cases that do show up.

=== Change test case view ===

Select one of several predefined test case views. For example you can group test cases as [http://cvresumewriters.com/ cv writer] by their outcome to quickly see only failing test cases.

== Further Documentation and Common Problems ==
Please visit [[Using CDD]] for further documentation or look at
[[CDD Common Problems|Common Problems]] if you run into problems.

== Related Publications ==

* Sunghun Kim, Shay Artzi, and Michael D. Ernst, "reCrash: Making Crash Reproducible" MIT Computer Science and Artificial Intelligence Laboratory technical report MIT-CSAIL-TR-2007-054, (Cambridge, MA), November 20, 2007. [http://recrash.googlecode.com/files/MIT-CSAIL-TR-2007-054.pdf (pdf)]

== Project Internal Stuff ==

[[CddBranchInternal]]