feature/tests: Add tests as a module #5
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- e2e tests with chrome and phantomjs - gulp build tasks - travis yml to run e2e tests on travis-ci.org
- Update unit test dependencies in TestEnvironment - Split session.inc class and function into session_utils.inc. This simplifies the dependencies in the unit tests.
- add, update, readback for customer - add, update, readback for supplier
cambell-prince
changed the title
|
The builds can be seen on travis-ci.org |
|
This is now outdated. I currently test with headless chrome rather than phantom. You can pull it in from my repo if you wish. |
cambell-prince
changed the title
FrontAccountingERP
pushed a commit
that referenced
this pull request
Jul 28, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Add tests as a module
I would like to see the tests included with the main code as this will keep them in sync with the code that they test. The tests folder is excluded via .gitattributes if so they will not appear in a tarball generated via git archive.
Currently the e2e tests using chrome and phantomjs are working (though see PR #3).