User Tools
eiffel:etf:debugger:start
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | |||
|
eiffel:etf:debugger:start [2020/03/08 21:54] jonathan |
eiffel:etf:debugger:start [2020/03/08 21:55] (current) jonathan |
||
|---|---|---|---|
| Line 12: | Line 12: | ||
| Of course it is much better to set up the Python script to do regression testing. | Of course it is much better to set up the Python script to do regression testing. | ||
| - | When an acceptance tests such as ''at1.txt'' is being developed (or failing), we might wish to use the debugger to determine where our implementation or contracts are failing. To do this, we must execute our code under development (usually in the W-code directory) from the IDE directly. To do this we must set up the **Execution Parameters** (accessible from the **Run** menu). | + | However, when an acceptance tests such as ''at1.txt'' is being developed (or failing), we might wish to use the debugger to determine where our implementation or contracts are failing. To do this, we must execute our code under development (usually in the W-code directory) from the IDE directly. To do this we must set up the **Execution Parameters** (accessible from the **Run** menu). |
| Click on the **Add** tab and provide a name for the profile, e.g. ''at1.txt''. | Click on the **Add** tab and provide a name for the profile, e.g. ''at1.txt''. | ||
eiffel/etf/debugger/start.1583704481.txt.gz · Last modified: 2020/03/08 21:54 by jonathan
Page Tools
