[root]/groovy/groovy-core/src/test/groovy/security
| Author | Changes | Lines of Code | Lines per Change |
|---|---|---|---|
| Totals | 49 (100.0%) | 1063 (100.0%) | 21.6 |
| jstrachan | 15 (30.6%) | 539 (50.7%) | 35.9 |
| paulk | 8 (16.3%) | 328 (30.9%) | 41.0 |
| dierk | 11 (22.4%) | 139 (13.1%) | 12.6 |
| goetze | 2 (4.1%) | 20 (1.9%) | 10.0 |
| bran | 1 (2.0%) | 15 (1.4%) | 15.0 |
| blackdrag | 4 (8.2%) | 11 (1.0%) | 2.7 |
| glaforge | 5 (10.2%) | 6 (0.6%) | 1.2 |
| popescu | 1 (2.0%) | 4 (0.4%) | 4.0 |
| cstein | 2 (4.1%) | 1 (0.1%) | 0.5 |
reformat test code
316 lines of code changed in:
increased coverage
4 lines of code changed in:
test was passing only if user.home/.maven/repository dir was available (nothing to do with the groovy.policy)
4 lines of code changed in:
build fixes
1 lines of code changed in:
Minor refactoring to make tests work better across environments, e.g. SerializeTest uses SystemClassLoader, rename BinaryStreamsTest to include it in test suite
7 lines of code changed in:
marks the testGroovyMethodsTest as not implemented
2 lines of code changed in:
Disabled the Jar signed test until the changes are back in GCL
Also disabled the test in SecurityTest calling a test class calling system.getProperty() which is failing on Windows / JDK 1.5
2 lines of code changed in:
Added additional PrivilegedActions to fix broken security tests.
3 lines of code changed in:
Dummy commit on SignedJarTest to see whether BeetleJuice has badly checked out the file or something?
1 lines of code changed in:
Dummy commit on SignedJarTest to see whether BeetleJuice has badly checked out the file or something?
3 lines of code changed in:
corrected SignedJarTest
1 lines of code changed in:
reenable test
2 lines of code changed in:
enables the securty tests
6 lines of code changed in:
going forward with moving commented tests into notYetImplemented() ones, finding out their passing restrictions
118 lines of code changed in:
GROOVY-1202: provide a feature to declare TestCases as 'notYetImplemented' and thus expected to fail: disable all security tests...
0 lines of code changed in:
GROOVY-1202: provide a feature to declare TestCases as 'notYetImplemented' and thus expected to fail: re-disable the environment specific Security tests that fail on the build server
1 lines of code changed in:
GROOVY-1202: provide a feature to declare TestCases as 'notYetImplemented' and thus expected to fail: re-disable the environment specific Security tests that fail on the build server
2 lines of code changed in:
GROOVY-1202: provide a feature to declare TestCases as 'notYetImplemented' and thus expected to fail: re-enable the environment specific Security tests
13 lines of code changed in:
GROOVY-1202: provide a feature to declare TestCases as 'notYetImplemented' and thus expected to fail: first attempt to make this run on the build server
5 lines of code changed in:
Introducing JMock 1.0.1 for testing.
Added first (and way too simple) GroovyServlet test case to the new UberTestCase4, which collects all text, servlet and other template related test cases. Moved single test case from UTC2 to UTC4.
Updated Eclipses ".classpath". It now includes the "src/test" directory. Of course, it needs a successful Maven build run, that generates the "target/test-classes" directory.
Removed not used imports from some test cases.
1 lines of code changed in:
(5 more)
