danger-junit 0.7.0 → 0.7.1
Sign up to get free protection for your applications and to get access to all the features.
- checksums.yaml +4 -4
- data/README.md +4 -4
- data/danger-junit.gemspec +1 -1
- data/lib/junit/gem_version.rb +1 -1
- metadata +4 -4
checksums.yaml
CHANGED
@@ -1,7 +1,7 @@
|
|
1
1
|
---
|
2
2
|
SHA1:
|
3
|
-
metadata.gz:
|
4
|
-
data.tar.gz:
|
3
|
+
metadata.gz: 070ac5947388c5a92ae5a02db8df8dfd2560ae1d
|
4
|
+
data.tar.gz: a55896e6350aa839e04b0d20f7903b7cb2fe34a4
|
5
5
|
SHA512:
|
6
|
-
metadata.gz:
|
7
|
-
data.tar.gz:
|
6
|
+
metadata.gz: 2c1d6ab9ca7edf89907da3a4f1c2f3aa4b1418da5e4f54c3769c5a4b5e49802de25b1fa322f142d29a7663496b979066b3c8efcb583cf92d4b06884d1200377e
|
7
|
+
data.tar.gz: a9d939e384a611ad3406169ae254abd9c41b20521716b0e8aa973f5b8bd8a478f447ba8e013090a9ff013d0eb9c190e9059456403cb004c1c77268ad6e06b9e8
|
data/README.md
CHANGED
@@ -27,7 +27,7 @@ Then you can pass the `junit-results.xml` file to the plugin in your `Dangerfile
|
|
27
27
|
|
28
28
|
In a Jasmine, or Jest testing project, you want to install the module `jasmine-reporters`. Then as you are setting up your Jasmine runner, [add the following](https://github.com/larrymyers/jasmine-reporters#basic-usage):
|
29
29
|
|
30
|
-
```
|
30
|
+
```javascript
|
31
31
|
var junitReporter = new jasmineReporters.JUnitXmlReporter({
|
32
32
|
savePath: 'junit-results.xml',
|
33
33
|
consolidateAll: false
|
@@ -42,10 +42,10 @@ Then you can pass the `junit-results.xml` file to the plugin in your `Dangerfile
|
|
42
42
|
You have a lot of options:
|
43
43
|
|
44
44
|
* [trainer](https://github.com/krausefx/trainer) is the fastest way to generate the junit file.
|
45
|
-
* [xcpretty](https://github.com/supermarin/xcpretty#reporters) is used in both
|
46
|
-
* [
|
45
|
+
* [xcpretty](https://github.com/supermarin/xcpretty#reporters) is used in both [fastlane](https://fastlane.tools), and a lot of standard setups.
|
46
|
+
* [xctool](https://github.com/facebook/xctool#included-reporters) includes it's own reporter for creating the file.
|
47
47
|
|
48
|
-
###
|
48
|
+
### JUnit
|
49
49
|
|
50
50
|
Report, or inspect any JUnit XML formatted test suite report.
|
51
51
|
|
data/danger-junit.gemspec
CHANGED
@@ -18,7 +18,7 @@ Gem::Specification.new do |spec|
|
|
18
18
|
spec.test_files = spec.files.grep(%r{^(test|spec|features)/})
|
19
19
|
spec.require_paths = ['lib']
|
20
20
|
|
21
|
-
spec.add_runtime_dependency 'danger', '
|
21
|
+
spec.add_runtime_dependency 'danger', '> 2.0'
|
22
22
|
spec.add_runtime_dependency 'ox', '~> 2.0'
|
23
23
|
|
24
24
|
# So we can run our specs with junit
|
data/lib/junit/gem_version.rb
CHANGED
metadata
CHANGED
@@ -1,27 +1,27 @@
|
|
1
1
|
--- !ruby/object:Gem::Specification
|
2
2
|
name: danger-junit
|
3
3
|
version: !ruby/object:Gem::Version
|
4
|
-
version: 0.7.
|
4
|
+
version: 0.7.1
|
5
5
|
platform: ruby
|
6
6
|
authors:
|
7
7
|
- Orta Therox
|
8
8
|
autorequire:
|
9
9
|
bindir: bin
|
10
10
|
cert_chain: []
|
11
|
-
date: 2016-08-
|
11
|
+
date: 2016-08-21 00:00:00.000000000 Z
|
12
12
|
dependencies:
|
13
13
|
- !ruby/object:Gem::Dependency
|
14
14
|
name: danger
|
15
15
|
requirement: !ruby/object:Gem::Requirement
|
16
16
|
requirements:
|
17
|
-
- - "
|
17
|
+
- - ">"
|
18
18
|
- !ruby/object:Gem::Version
|
19
19
|
version: '2.0'
|
20
20
|
type: :runtime
|
21
21
|
prerelease: false
|
22
22
|
version_requirements: !ruby/object:Gem::Requirement
|
23
23
|
requirements:
|
24
|
-
- - "
|
24
|
+
- - ">"
|
25
25
|
- !ruby/object:Gem::Version
|
26
26
|
version: '2.0'
|
27
27
|
- !ruby/object:Gem::Dependency
|