jasmine-core 2.6.2 → 2.8.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -1,17 +1,44 @@
1
- ### Are you creating an issue in the correct repository?
1
+ ## Are you creating an issue in the correct repository?
2
2
 
3
3
  - When in doubt, create an issue here.
4
4
  - If you have an issue with the Jasmine docs, file an issue in the docs repo
5
5
  here: https://github.com/jasmine/jasmine.github.io
6
6
  - This repository is for the core Jasmine framework
7
- - If you are using a test runner that wraps Jasmine (Jasmine npm, karma, etc),
8
- consider filing an issue with that library if appropriate
7
+ - If you are using a test runner that wraps Jasmine, consider filing an issue with that library if appropriate:
8
+ - [Jasmine npm](https://github.com/jasmine/jasmine-npm/issues)
9
+ - [Jasmine gem](https://github.com/jasmine/jasmine-gem/issues)
10
+ - [Jasmine py](https://github.com/jasmine/jasmine-py/issues)
11
+ - [Gulp Jasmine Browser](https://github.com/jasmine/gulp-jasmine-browser/issues)
12
+ - [Karma](https://github.com/karma-runner/karma/issues)
13
+ - [Grunt Contrib Jasmine](https://github.com/gruntjs/grunt-contrib-jasmine/issues)
9
14
 
10
- ### When submitting an issue, please answer the following:
15
+ <!--- Provide a general summary of the issue in the Title above -->
11
16
 
12
- - What version are you using?
13
- - What environment are you running Jasmine in (node, browser, etc)?
14
- - How are you running Jasmine (standalone, npm, karma, etc)?
15
- - If possible, include an example spec that demonstrates your issue.
17
+ ## Expected Behavior
18
+ <!--- If you're describing a bug, tell us what should happen -->
19
+ <!--- If you're suggesting a change/improvement, tell us how it should work -->
16
20
 
17
- Thanks for using Jasmine!
21
+ ## Current Behavior
22
+ <!--- If describing a bug, tell us what happens instead of the expected behavior -->
23
+ <!--- If suggesting a change/improvement, explain the difference from current behavior -->
24
+
25
+ ## Possible Solution
26
+ <!--- Not obligatory, but suggest a fix/reason for the bug, -->
27
+ <!--- or ideas how to implement the addition or change -->
28
+
29
+ ## Suite that reproduces the behavior (for bugs)
30
+ <!--- Provide a sample suite that reproduces the bug. -->
31
+ ```javascript
32
+ describe("sample", function() {
33
+ });
34
+ ```
35
+ ## Context
36
+ <!--- How has this issue affected you? What are you trying to accomplish? -->
37
+ <!--- Providing context helps us come up with a solution that is most useful in the real world -->
38
+
39
+ ## Your Environment
40
+ <!--- Include as many relevant details about the environment you experienced the bug in -->
41
+ * Version used:
42
+ * Environment name and version (e.g. Chrome 39, node.js 5.4):
43
+ * Operating System and version (desktop or mobile):
44
+ * Link to your project:
@@ -0,0 +1,30 @@
1
+ <!--- Provide a general summary of your changes in the Title above -->
2
+
3
+ ## Description
4
+ <!--- Describe your changes in detail -->
5
+
6
+ ## Motivation and Context
7
+ <!--- Why is this change required? What problem does it solve? -->
8
+ <!--- If it fixes an open issue, please link to the issue here. -->
9
+
10
+ ## How Has This Been Tested?
11
+ <!--- Please describe in detail how you tested your changes. -->
12
+ <!--- Include details of your testing environment, and the tests you ran to -->
13
+ <!--- see how your change affects other areas of the code, etc. -->
14
+
15
+ ## Types of changes
16
+ <!--- What types of changes does your code introduce? Put an `x` in all the boxes that apply: -->
17
+ - [ ] Bug fix (non-breaking change which fixes an issue)
18
+ - [ ] New feature (non-breaking change which adds functionality)
19
+ - [ ] Breaking change (fix or feature that would cause existing functionality to change)
20
+
21
+ ## Checklist:
22
+ <!--- Go over all the following points, and put an `x` in all the boxes that apply. -->
23
+ <!--- If you're unsure about any of these, don't hesitate to ask. We're here to help! -->
24
+ - [ ] My code follows the code style of this project.
25
+ - [ ] My change requires a change to the documentation.
26
+ - [ ] I have updated the documentation accordingly.
27
+ - [ ] I have read the **CONTRIBUTING** document.
28
+ - [ ] I have added tests to cover my changes.
29
+ - [ ] All new and existing tests passed.
30
+
@@ -0,0 +1,46 @@
1
+ # Contributor Covenant Code of Conduct
2
+
3
+ ## Our Pledge
4
+
5
+ In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation.
6
+
7
+ ## Our Standards
8
+
9
+ Examples of behavior that contributes to creating a positive environment include:
10
+
11
+ * Using welcoming and inclusive language
12
+ * Being respectful of differing viewpoints and experiences
13
+ * Gracefully accepting constructive criticism
14
+ * Focusing on what is best for the community
15
+ * Showing empathy towards other community members
16
+
17
+ Examples of unacceptable behavior by participants include:
18
+
19
+ * The use of sexualized language or imagery and unwelcome sexual attention or advances
20
+ * Trolling, insulting/derogatory comments, and personal or political attacks
21
+ * Public or private harassment
22
+ * Publishing others' private information, such as a physical or electronic address, without explicit permission
23
+ * Other conduct which could reasonably be considered inappropriate in a professional setting
24
+
25
+ ## Our Responsibilities
26
+
27
+ Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior.
28
+
29
+ Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.
30
+
31
+ ## Scope
32
+
33
+ This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers.
34
+
35
+ ## Enforcement
36
+
37
+ Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at jasmine-maintainers@googlegroups.com. The project team will review and investigate all complaints, and will respond in a way that it deems appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.
38
+
39
+ Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership.
40
+
41
+ ## Attribution
42
+
43
+ This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, available at [http://contributor-covenant.org/version/1/4][version]
44
+
45
+ [homepage]: http://contributor-covenant.org
46
+ [version]: http://contributor-covenant.org/version/1/4/
package/README.md CHANGED
@@ -43,12 +43,12 @@ To install Jasmine standalone on your local box (where **_{#.#.#}_** below is su
43
43
  Add the following to your HTML file:
44
44
 
45
45
  ```html
46
- <link rel="shortcut icon" type="image/png" href="jasmine/lib/jasmine-core/jasmine_favicon.png">
47
- <link rel="stylesheet" type="text/css" href="jasmine/lib/jasmine-core/jasmine.css">
46
+ <link rel="shortcut icon" type="image/png" href="jasmine/lib/jasmine-{#.#.#}/jasmine_favicon.png">
47
+ <link rel="stylesheet" type="text/css" href="jasmine/lib/jasmine-{#.#.#}/jasmine.css">
48
48
 
49
- <script type="text/javascript" src="jasmine/lib/jasmine-core/jasmine.js"></script>
50
- <script type="text/javascript" src="jasmine/lib/jasmine-core/jasmine-html.js"></script>
51
- <script type="text/javascript" src="jasmine/lib/jasmine-core/boot.js"></script>
49
+ <script type="text/javascript" src="jasmine/lib/jasmine-{#.#.#}/jasmine.js"></script>
50
+ <script type="text/javascript" src="jasmine/lib/jasmine-{#.#.#}/jasmine-html.js"></script>
51
+ <script type="text/javascript" src="jasmine/lib/jasmine-{#.#.#}/boot.js"></script>
52
52
  ```
53
53
 
54
54
  ## Supported environments
package/RELEASE.md CHANGED
@@ -40,7 +40,10 @@ When ready to release - specs are all green and the stories are done:
40
40
 
41
41
  ### Release the Python egg
42
42
 
43
- 1. `python setup.py register sdist upload` You will need pypi credentials to upload the egg.
43
+ Install [twine](https://github.com/pypa/twine)
44
+
45
+ 1. `python setup.py sdist`
46
+ 1. `twine upload dist/jasmine-core-<version>.tar.gz` You will need pypi credentials to upload the egg.
44
47
 
45
48
  ### Release the Ruby gem
46
49
 
package/bower.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "jasmine-core",
3
- "homepage": "http://jasmine.github.io",
3
+ "homepage": "https://jasmine.github.io",
4
4
  "authors": [
5
5
  "slackersoft <gregg@slackersoft.net>"
6
6
  ],
@@ -1,6 +1,6 @@
1
1
  Metadata-Version: 1.1
2
2
  Name: jasmine-core
3
- Version: 2.6.1
3
+ Version: 2.8.0
4
4
  Summary: Jasmine is a Behavior Driven Development testing framework for JavaScript. It does not rely on browsers, DOM, or any JavaScript framework. Thus it's suited for websites, Node.js (http://nodejs.org) projects, or anywhere that JavaScript can run.
5
5
  Home-page: http://jasmine.github.io
6
6
  Author: Pivotal Labs
@@ -210,7 +210,7 @@ jasmineRequire.HtmlReporter = function(j$) {
210
210
 
211
211
  if (specsExecuted < totalSpecsDefined) {
212
212
  var skippedMessage = 'Ran ' + specsExecuted + ' of ' + totalSpecsDefined + ' specs - run all';
213
- var skippedLink = order && order.random ? '?random=true' : '?';
213
+ var skippedLink = addToExistingQueryString('spec', '');
214
214
  alert.appendChild(
215
215
  createDom('span', {className: 'jasmine-bar jasmine-skipped'},
216
216
  createDom('a', {href: skippedLink, title: 'Run all specs'}, skippedMessage)