forked from karma-runner/karma
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Update issue templates (karma-runner#3460)
- Loading branch information
1 parent
9fad813
commit c30bf44
Showing
1 changed file
with
24 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,24 @@ | ||
--- | ||
name: Bug report | ||
about: Create an actionable bug report | ||
title: '' | ||
labels: '' | ||
assignees: '' | ||
|
||
--- | ||
|
||
karma has an extensive set of tests and we have limited time to help with bugs. Here are some suggestions to get you unstuck. | ||
|
||
** npm audit vulnerabilities ** | ||
Please open a Pull Request that will fix the issue. | ||
|
||
We get lots of these reports, from multiple automated services, from other projects, and from users. The vast majority are minor: please open a pull request if you want a fix. We only take direct action to fix serious issues that affect online users. | ||
|
||
** how to diagnose issues ** | ||
Many issues can be diagnosed by running with `--logLevel=DEBUG` or the corresponding config option. The log prints the final configuration: does it have the values you expected? Please always post the DEBUG log in bug reports. | ||
|
||
Is your issue related to another tool? Issues with Angular setups are probably better debugged by consulting with other Angular users. Issues with coverage are probably related to your config, the compiler for coverage instrumentation, or possibly karma-coverage. | ||
|
||
`karma` is all JavaScript code: perhaps you can debug your issue by adding logging? | ||
|
||
Because of the complexity of test setups, we rarely work to fix bugs without steps to reproduce. The best approach is to create a github project that installs all the components and reproduces the bug. |