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.

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

Reviewed "Automated tests" #38

Merged
merged 2 commits into from
Nov 26, 2014
Merged

Reviewed "Automated tests" #38

merged 2 commits into from
Nov 26, 2014

Conversation

mnapoli
Copy link
Contributor

@mnapoli mnapoli commented Nov 23, 2014

Related to #22. Depends on #34 too, merge #34 before this one.

The guide was still talking about:

  • unit tests
  • integration tests
  • ui tests

I've renamed "integration tests" with "system tests" (as that's what I understood) and added a new "integration tests" which is basically old unit tests that used the database or the server.

Also just to be sure, I've seen plugins use tests/ and Test/ as a subdirectory. I don't know which one is the best, but I've edited the guide to be consistent (I've used Test/ as I think that's the one I've seen the most in plugins, and that's the one which makes sense with autoloading).


_Note: All test files must be put in a **tests** directory located in the root directory of your plugin and every test you write should have the `@group` set to the name of your plugin (for example, `@group MyPlugin`)._
*Note: All test files must be put in a `Test/` directory located in the root directory of your plugin and every test you write should have the `@group` set to the name of your plugin (for example, `@group MyPlugin`).*
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

is it still true that

every test you write should have the `@group` set to the name of your plugin (for example, `@group MyPlugin`).

maybe this can be removed ?

@mattab
Copy link
Member

mattab commented Nov 25, 2014

Would it make sense to split the guide about System tests in one smaller guide, and also move Screenshot test doc in one small guide?

@mattab
Copy link
Member

mattab commented Nov 25, 2014

Nice one! though the guide feels too long (took me much concentration to read it ;)

@mnapoli
Copy link
Contributor Author

mnapoli commented Nov 26, 2014

Fixed all the comments, going to merge. I'll have a look at splitting the guide in #43

mnapoli added a commit that referenced this pull request Nov 26, 2014
@mnapoli mnapoli merged commit 8becd00 into master Nov 26, 2014
@mnapoli mnapoli deleted the automated-tests branch November 26, 2014 00:31
@mnapoli
Copy link
Contributor Author

mnapoli commented Nov 26, 2014

Guide splitted in the PR #43! It look soooo much nicer :)

mnapoli added a commit that referenced this pull request Nov 26, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants