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

Add regression tests #41

Merged
merged 1 commit into from
Jan 21, 2019
Merged

Conversation

DanielBallaSZTE
Copy link
Contributor

  • Now regression tests for resolved issues can be added to the project.
  • Regression tests are enabled by default.
  • They can be manually run by appending regression-tests to the run-tests.py command.
  • There is an expected-failures directory for tests that should fail.

The .gitignore file was modified as well to making sure it doesn't ignore these testfiles.

Signed-off-by: Daniel Balla [email protected]

.gitignore Outdated Show resolved Hide resolved
test/regression-tests/issue-jerryscript-642.js Outdated Show resolved Hide resolved
tools/run-tests.py Outdated Show resolved Hide resolved
tools/run-tests.py Outdated Show resolved Hide resolved
tools/run-tests.py Outdated Show resolved Hide resolved
tools/run-tests.py Outdated Show resolved Hide resolved
tools/run-tests.py Outdated Show resolved Hide resolved
tools/run-tests.py Outdated Show resolved Hide resolved
tools/run-tests.py Outdated Show resolved Hide resolved
@akosthekiss
Copy link
Contributor

@DanielBallaSZTE In your next update, please add the test cases of the recently fixed issues #31 and #33 .

@DanielBallaSZTE
Copy link
Contributor Author

@akosthekiss Patch updated, thank you for the review.

test/regression-tests/issue-33.js Outdated Show resolved Hide resolved
test/regression-tests/issue-5.js Show resolved Hide resolved
test/regression-tests/issue-33.js Outdated Show resolved Hide resolved
test/regression-tests/issue-31.js Outdated Show resolved Hide resolved
tools/run-tests.py Outdated Show resolved Hide resolved
tools/run-tests.py Outdated Show resolved Hide resolved
tools/run-tests.py Outdated Show resolved Hide resolved
@DanielBallaSZTE DanielBallaSZTE force-pushed the regression-tests branch 2 times, most recently from 7f7aa46 to 0998653 Compare January 4, 2019 14:12
test/regression-tests/issue-5.js Outdated Show resolved Hide resolved
test/regression-tests/issue-31.js Outdated Show resolved Hide resolved
tools/run-tests.py Outdated Show resolved Hide resolved
tools/run-tests.py Outdated Show resolved Hide resolved
tools/run-tests.py Outdated Show resolved Hide resolved
@DanielBallaSZTE
Copy link
Contributor Author

@akosthekiss Thank you for the review, PR updated

tools/run-tests.py Outdated Show resolved Hide resolved
test/regression-tests/issue-5.js Outdated Show resolved Hide resolved
@DanielBallaSZTE DanielBallaSZTE force-pushed the regression-tests branch 2 times, most recently from 5466420 to 955d2ec Compare January 7, 2019 12:07
Copy link
Contributor

@akosthekiss akosthekiss left a comment

Choose a reason for hiding this comment

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

Current technical content looks good to me in general. But it just occured to me that the new test suite is not executed on CI. Could you please add them to {x86, x86-64}{linux, darwin}{debug, release} travis CI jobs?

@akosthekiss
Copy link
Contributor

The test cases of issues fixed by PRs #45 (merged) and #42 (approved and ready to be merged) should also be added to the commit.

@DanielBallaSZTE
Copy link
Contributor Author

@akosthekiss I have updated the PR with the suggested changes, thank you

.travis.yml Outdated Show resolved Hide resolved
.travis.yml Outdated Show resolved Hide resolved
.travis.yml Show resolved Hide resolved
test/regression-tests/issue-28.js Show resolved Hide resolved
@DanielBallaSZTE DanielBallaSZTE force-pushed the regression-tests branch 2 times, most recently from 52391ac to 073ee65 Compare January 11, 2019 12:13
@DanielBallaSZTE
Copy link
Contributor Author

#53 should land to make Travis pass.

Now regression tests for resolved issues can be added to the project.
Regression tests are enabled by default.
They can be manually run by appending `regression-tests` to the `run-tests.py` command.
There is an `expected-failures` directory for tests that should fail.
The .gitignore file was modified as well to making sure it doesn't ignore these testfiles.

Signed-off-by: Daniel Balla [email protected]
@DanielBallaSZTE
Copy link
Contributor Author

@akosthekiss I've updated the PR, since #53 landed, Travis will probably take some time to run, however it should pass since my local travis passed as well.

Copy link
Contributor

@akosthekiss akosthekiss left a comment

Choose a reason for hiding this comment

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

LGTM

Copy link
Contributor

@clover2123 clover2123 left a comment

Choose a reason for hiding this comment

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

LGTM

@yichoi yichoi merged commit 7d32087 into Samsung:master Jan 21, 2019
clover2123 referenced this pull request in clover2123/escargot Jan 22, 2019
Now regression tests for resolved issues can be added to the project.
Regression tests are enabled by default.
They can be manually run by appending `regression-tests` to the `run-tests.py` command.
There is an `expected-failures` directory for tests that should fail.
The .gitignore file was modified as well to making sure it doesn't ignore these testfiles.

Signed-off-by: Daniel Balla [email protected]
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.

4 participants