| 34 | | (see xt/actions.t ) |
| | 34 | Instead of adding events directly to menu items Padre has a separate Action system. |
| | 35 | Each action then can be added to the menu or the toolbar or to the right-click pop-up window |
| | 36 | or probably elsewhere. Padre also has a way to automatically execute a set of actions |
| | 37 | that were given to it on the command line. This enables us to write certain |
| | 38 | automated test. An example for such test can be found in the xt/actions.t file in |
| | 39 | the Padre source code. |
| | 40 | |
| | 41 | The task is to add about 30 test cases to provide a good coverage of Padre via the actions system. |
| | 42 | As this has never been tested full probably the action system itself will need further extension |
| | 43 | to be able to test various important features of Padre. |
