Skip to content

Issues: emberjs/ember-mocha

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

12 Open 104 Closed
12 Open 104 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

#ember-testing-container is alway empty and shows no preview.
#693 opened Jun 9, 2022 by kushagra-singh-vineti
Not compatible with Ember 4+
#691 opened Mar 4, 2022 by arthur5005
Ember Upgrade: global is not defined
#655 opened Apr 2, 2021 by bmoellers
Upgrade path
#638 opened Feb 17, 2021 by yads
7
Flaky Cannot assign to read only property 'owner' of object '#<Context>'
#561 opened May 13, 2020 by rreckonerr
2
Setting same properties name causing tests fail
#430 opened Sep 5, 2019 by brunoocasali
1
6
What's needed for 1.0? question
#215 opened Aug 27, 2018 by mike-north
2
Ember-Mocha + Ember-Cli-Mocha = invalid /tests HTML enhancement
#211 opened Jul 31, 2018 by mike-north
3
setupTest is eating exceptions
#209 opened Jul 26, 2018 by mupkoo
Question: can mocha dependency be upgraded? question
#206 opened May 14, 2018 by pixelhandler
10
Existing run loop at the beginning of test interferes with Ember.run.join behavior breaking internal
#160 opened Aug 24, 2017 by ming-codes
1
Component tests run fine if in the 'root' describe block, but throw 'You have turned on testing mode, which disabled the run-loop's autorun' error when in nested describe blocks
#132 opened Jan 24, 2017 by fushi
15
ProTip! Type g p on any issue or pull request to go back to the pull request listing page.