Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update issue templates #3460

Merged
merged 1 commit into from
Apr 9, 2020
Merged

Update issue templates #3460

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
24 changes: 24 additions & 0 deletions .github/ISSUE_TEMPLATE/bug_report.md
View file
Open in desktop
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.