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

Jump to bottom

Style Guide suggestion: tests #9106

Closed
cjcenizal opened this issue Nov 16, 2016 · 2 comments
Closed

Style Guide suggestion: tests #9106

cjcenizal opened this issue Nov 16, 2016 · 2 comments
Labels
Meta

Comments

@cjcenizal
Copy link
Contributor

Let's create a style guide for how to write good unit and functional tests.

Unit tests

  • The purpose of unit tests.
  • The purpose of unit tests in directives/components.
  • describe vs context: Use both or only one?
  • How to use describe blocks to group interface tests and behavior tests separately.
  • How to use describe to group and subgroup tests.
  • How to use the code coverage generator.

Functional tests
@Bargs
Copy link
Contributor

Bargs commented Nov 17, 2016

Also API tests https://github.com/elastic/kibana/tree/b7fd17b4924d7cfd30a668c9f5ded6413641f81a/test/unit/api

@cjcenizal cjcenizal added Meta and removed discuss labels Nov 21, 2016
This was referenced Nov 21, 2016
Closed
Open
Closed
@cjcenizal
Copy link
Contributor Author

cjcenizal commented Nov 21, 2016 •
edited
Loading

To-do

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Meta
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@cjcenizal @Bargs