Mercurial > getan
comparison TODO @ 442:7125e67d5acb
dd getan testdata, add multi-selection Bug report.
* add /test_data/getan_test_data.py to create a new getan database
with test data.
* update report 20170317 BER. Add a guide to recreating the bug.
* TDOD: Fix the bug.
| author | Magnus Schieder <mschieder@intevation.de> |
|---|---|
| date | Thu, 18 Jan 2018 11:14:24 +0100 |
| parents | f441913a5cdc |
| children | dc79952b36b0 |
comparison
equal
deleted
inserted
replaced
| 440:f441913a5cdc | 442:7125e67d5acb |
|---|---|
| 1 | |
| 2 20180117 Magnus Schieder | |
| 3 | |
| 4 20170317 BER: Reproduce and then fix a defect that it is surprising which | |
| 5 entries are moved by `m` or deleted by 'd'. | |
| 6 It probably has to do how multi-selection are handled. Maybe they | |
| 7 are not cleared properly at the end of an operation. | |
| 8 One description: It happens when you have changed a lot of entries | |
| 9 from different projects (I assume), e.g. by editing the description, | |
| 10 the length or timedate and then use move where you intend to only move | |
| 11 one, the unwanted result is several moved entries. | |
| 12 | |
| 13 Update: | |
| 14 getan 2.1 | |
| 15 | |
| 16 Creating a new database with test data: | |
| 17 | |
| 18 1) Delete getan_test_data.db if it already exists to create a new database. | |
| 19 2) Execute getan_test_data.py to get the test database getan_test_data.db. | |
| 20 (getan/test_data/getan_test_data.py) | |
| 21 | |
| 22 - Bug 1.0 | |
| 23 2) Open getan with the test database. (getan /path/getan_test_data.db) | |
| 24 3) Switch to the entries from the project pro1 with tab. | |
| 25 4) Mark with return and arrow keys ent1 and ent2. | |
| 26 5) Go back to the projects with tab. | |
| 27 6) Switch back to the entries of project pro1. | |
| 28 7) Mark this time ent3 and ent4. | |
| 29 8) Press m, then 3 and then y to move ent3 and ent4 to pro3. | |
| 30 | |
| 31 Expectation: | |
| 32 ent3 and ent4 are moved to pro3. | |
| 33 | |
| 34 Result: | |
| 35 ent1, ent2, ent3 and ent4 were moved to pro3. | |
| 36 | |
| 37 - Bug 1.1 | |
| 38 Execute 1) to 7) from 1.0. | |
| 39 8) Press d to delete ent3 and ent4. | |
| 40 | |
| 41 Expectation: | |
| 42 ent3 and ent4 are deleted. | |
| 43 | |
| 44 Result: | |
| 45 ent1, en2, ent3 and ent4 are deleted. | |
| 46 | |
| 47 - Bug2 | |
| 48 Execute 1) to 4) from 1.0. | |
| 49 5) Press m. | |
| 50 6) Now also mark ent3 and pro ent4. | |
| 51 7) Press 3 and then y to move ent1, ent2, ent3 and ent4 to pro3. | |
| 52 | |
| 53 Expectation: | |
| 54 After pressing m, you can not mark additional entries. | |
| 55 | |
| 56 Result: | |
| 57 Only ent1 and ent2 are moved, though all are selected. | |
| 58 | |
| 1 20180104 BER (minor) Display licensing information with --version and | 59 20180104 BER (minor) Display licensing information with --version and |
| 2 usage. Implementation idea: change this when moving away from optparse. | 60 usage. Implementation idea: change this when moving away from optparse. |
| 3 | 61 |
| 4 20170709 BER: Give scripts/getan-eval.py a more specific name and add | 62 20170709 BER: Give scripts/getan-eval.py a more specific name and add |
| 5 it as a script to be installed. | 63 it as a script to be installed. |
| 8 to argparse. Affects getan/main.py and scripts/getan-eval.py. | 66 to argparse. Affects getan/main.py and scripts/getan-eval.py. |
| 9 | 67 |
| 10 20170504 BER: Some multi-user installations do not want a logfile by default. | 68 20170504 BER: Some multi-user installations do not want a logfile by default. |
| 11 We could solve this requirement by making it configurable. | 69 We could solve this requirement by making it configurable. |
| 12 | 70 |
| 13 20170317 BER: Reproduce and then fix a defect that it is surprising which | 71 |
| 14 entries are moved by `m` or deleted by 'd'. | |
| 15 It probably has to do how multi-selection are handled. Maybe they | |
| 16 are not cleared properly at the end of an operation. | |
| 17 One description: It happens when you have changed a lot of entries | |
| 18 from different projects (I assume), e.g. by editing the description, | |
| 19 the length or timedate and then use move where you intend to only move | |
| 20 one, the unwanted result is several moved entries. | |
| 21 | 72 |
| 22 20160912 BER: Better code: states.py: classes EditEntryState and | 73 20160912 BER: Better code: states.py: classes EditEntryState and |
| 23 AdjustEntryState have same methods exit() and set_focus(), maybe join them? | 74 AdjustEntryState have same methods exit() and set_focus(), maybe join them? |
| 24 | 75 |
| 25 Older: | 76 Older: |