karma-runner/karma-qunit

Issues

• QUnit.todo() with a failure are reported as failling

  #111 opened 6 years ago by hashar
  1

• Karma Runner is deprecated

  #183 opened 10 months ago by mauriciolauffer
  1

• Problem with path while loading a file for testing

  #158 opened 3 years ago by kalwalt
  4

• qunit 2.x not usable as a module dependency with karma

  #57 opened 3 years ago by rjatkins
  2

• Karma 5.x support

  #137 opened 5 years ago by aliaksandr-yermalayeu
  1

• Release 3.1.0

  #124 opened 6 years ago by XhmikosR
  1

• JS coding in 2.1.0 when first test fails

  #115 opened 6 years ago by vobu
  3

• "Adapter did not report total number of specs" error

  #8 opened 7 years ago by lazd
  5

• qunit-fixture has incorrect styles

  #109 opened 6 years ago by asapach
  12

• qunit-fixture is not reset between tests properly

  #104 opened 7 years ago by asapach
  1

• v2.x throws "No tests were run"

  #103 opened 7 years ago by XhmikosR
  7

• Promise support

  #37 opened 7 years ago by sechel
  3

• QUnit 2.3.0 compatibility?

  #87 opened 7 years ago by marsjaninzmarsa
  2

• Possible regression on `0.1.5`

  #28 opened 7 years ago by paulfalgout
  6

• "TypeError: toolbar is null" on QUnit v1.17

  #23 opened 7 years ago by uyeong
  5

• Can not run tests on QUnit 0.18.0

  #26 opened 7 years ago by patkoscsaba
  3

• Support the new package name for `QUnit` (after version `2.4.1`)

  #98 opened 7 years ago by brandonocasey
  3

• Existing fixture should be preserved

  #92 opened 7 years ago by Krinkle
  1

• Autostart from adapter conflicts with autostart from user

  #27 opened 7 years ago by Krinkle
  4

• running qUnit test: test is not defined

  #99 opened 7 years ago by SlavikCA
  1

• QUnit 2.0.0 Support

  #43 opened 8 years ago by bworsfold
  5

• Never ending loop when `singlerun: false` and failing test

  #47 opened 8 years ago by brunoscopelliti
  6

• Mark skipped tests correctly

  #38 opened 8 years ago by sechel
  2

• Show the qunit ui

  #40 opened 8 years ago by sechel
  2

• karma-qunit doesn't display failing values

  #7 opened 9 years ago by codinguncut
  1

• Expected/Actual object values in test failure are reported as [object Object]

  #24 opened 9 years ago by Krinkle
  3

• Publish latest stuff

  #34 opened 9 years ago by tailsu
  2

• Allow users to specify qunitjs version

  #25 opened 10 years ago by Krinkle
  0

• DOM-elements isn't injected

  #18 opened 10 years ago by SimenB
  5

• karma-qunit can't resolve qunitjs from github

  #14 opened 10 years ago by nikolas
  2

• Can not install with qunitjs 1.15.0

  #19 opened 10 years ago by Waxolunist
  4

• peerinvalid Peer karma-qunit@0.1.1 wants qunitjs@~1.12.0

  #12 opened 11 years ago by jlchereau
  1

• tests from Default Module have unexpected suite information

  #5 opened 11 years ago by segrey
  1

• Error: No provider for "framework:qunit"! (Resolving: framework:qunit)

  #9 opened 11 years ago by thenickcox
  1

• Use qunitjs npm module

  #1 opened 11 years ago by vojtajina
  0

• Failed expectation does not show the actual/expected values

  #6 opened 11 years ago by vojtajina
  0

• Create unit tests and setup Travis CI.

  #2 opened 11 years ago by dignifiedquire
  1

• Support integration with RequireJS

  #3 opened 11 years ago by vojtajina
  9