Change History for GSoC/2014/TestingFrameworkForGRASS

Version Date Author Comment
62 10 years wenzeslaus fix the table for Trac 1.0.5: no empty lines between rows, spaces/no …
61 10 years wenzeslaus link documentation, clarify purpose
60 10 years wenzeslaus add note about debug messages
59 11 years wenzeslaus add benchmarks into todo
58 11 years wenzeslaus remove unwanted section (trac sometimes does not like editing at the …
57 11 years wenzeslaus final report and todo
56 11 years wenzeslaus remove dead link
55 11 years wenzeslaus link to final source code state in GRASS repository
54 11 years wenzeslaus Weekly report 13
53 11 years wenzeslaus add closing comment for #2105
52 11 years wenzeslaus Weekly report 12 (no formatting)
51 11 years wenzeslaus Weekly report 11
50 11 years wenzeslaus Weekly report 10
49 11 years wenzeslaus week links from plan
48 11 years wenzeslaus update source link
47 11 years wenzeslaus Weekly report 9
46 11 years wenzeslaus add Testing framework now in trunk announcement
45 11 years wenzeslaus Weekly report 8
44 11 years wenzeslaus Weekly report 7 (no formatting)
43 11 years wenzeslaus updates of data ideas
42 11 years wenzeslaus Weekly report 6 (no formatting)
41 11 years wenzeslaus add more to Python static analyses
40 11 years wenzeslaus link to source code
39 11 years wenzeslaus Weekly report 5
38 11 years wenzeslaus Weekly report 4
37 11 years wenzeslaus add pep257 to static analyses
36 11 years wenzeslaus Weekly report 3 (no formatting)
35 11 years wenzeslaus list of static analysis tools for Python
34 11 years wenzeslaus code coverage as an available addition
33 11 years wenzeslaus short note about static source code analysis
32 11 years wenzeslaus testing GRASS modules which are Python scripts
31 11 years wenzeslaus last line of a page is duplicated when editing section at the end of …
30 11 years wenzeslaus Weekly report 2
29 11 years wenzeslaus English messages versus locale idepended tests
28 11 years wenzeslaus note problems with stadard output of helper subprocesses
27 11 years wenzeslaus
26 11 years wenzeslaus improve test internal invocation desc
25 11 years wenzeslaus example for test discovery
24 11 years wenzeslaus suggestion to deal with dependecies of test code
23 11 years wenzeslaus importing and running modules: using unittest
22 11 years wenzeslaus how the test methods are invoked
21 11 years wenzeslaus discuss more the usage of doctests
20 11 years wenzeslaus problem of environment specific outputs, idea to use doctest's …
19 11 years wenzeslaus more on result directory structure
18 11 years wenzeslaus special dependencies of testing code
17 11 years wenzeslaus note on documentation for tests
16 11 years wenzeslaus improve issues on ms windows section
15 11 years wenzeslaus report structure
14 11 years wenzeslaus explain more valgrind for libraries
13 11 years wenzeslaus dependencies, grass fatal, ms windows, locations, reports (mostly …
12 11 years wenzeslaus Weekly report 1
11 11 years wenzeslaus note about doctest which needs test and documenation datasets
10 11 years wenzeslaus about maps in location
9 11 years wenzeslaus tests should have main
8 11 years wenzeslaus first draft of data handling (after discussing with Soeren)
7 11 years wenzeslaus layout, basic invoking and others (from conversation with Soeren)
6 11 years wenzeslaus consider also valgrind friends
5 11 years wenzeslaus naming conventions for files and test methods
4 11 years wenzeslaus notes about valgrind
3 11 years wenzeslaus first draft of basic part of API
2 11 years wenzeslaus link existing work mentioned in proposal
1 11 years wenzeslaus copy of relevant parts of the proposal from melange