Foundry376/Mailspring
1
1
Fork 0
mirror of https://github.com/Foundry376/Mailspring.git synced 2024-11-11 18:32:20 +08:00
Code Issues Projects Releases Packages Wiki Activity
Mailspring/spec_integration/package.json

20 lines
423 B
JSON
Raw Normal View History

ci(spectron): Add support to execute spectron/chrome-driver tests Summary: - Sets up spectron test suite inside its own directory and with its own dependencies (must run on a build of the app) - Sets up dummy test - Adds `run-spectron-specs` grunt task, and adds it to cibuild task - Cleans up spec tasks code Test Plan: - Run specs Reviewers: evan, bengotow Reviewed By: bengotow Differential Revision: https://phab.nylas.com/D2256
2015-11-14 01:50:57 +08:00
{
"name": "nylas-spectron",
"description": "N1 Spectron Test Suite",
"repository": {
"type": "git",
"url": "https://github.com/nylas/N1.git"
},
"scripts": {
feat(spec): add config dir to integration specs Summary: - You can now pass `--config-dir-path=/some/custom/path` to `./N1.sh` - `main.coffee` cleaned up a bit. A lot of unused params from legacy Atom stuff were still being used - Integration specs now set the config dir before booting. - New spec to check for the autoupdater in the app and make sure it's pointing at the right place. Test Plan: script/grunt run-integration-tests Reviewers: juan, bengotow Reviewed By: bengotow Differential Revision: https://phab.nylas.com/D2331
2015-12-10 23:52:20 +08:00
"test": "jasmine JASMINE_CONFIG_PATH=./jasmine/config.json"
ci(spectron): Add support to execute spectron/chrome-driver tests Summary: - Sets up spectron test suite inside its own directory and with its own dependencies (must run on a build of the app) - Sets up dummy test - Adds `run-spectron-specs` grunt task, and adds it to cibuild task - Cleans up spec tasks code Test Plan: - Run specs Reviewers: evan, bengotow Reviewed By: bengotow Differential Revision: https://phab.nylas.com/D2256
2015-11-14 01:50:57 +08:00
},
feat(ci): add Travis and AppVeyor ci support
2015-12-04 03:53:51 +08:00
"license": "GPL-3.0",
ci(spectron): Add support to execute spectron/chrome-driver tests Summary: - Sets up spectron test suite inside its own directory and with its own dependencies (must run on a build of the app) - Sets up dummy test - Adds `run-spectron-specs` grunt task, and adds it to cibuild task - Cleans up spec tasks code Test Plan: - Run specs Reviewers: evan, bengotow Reviewed By: bengotow Differential Revision: https://phab.nylas.com/D2256
2015-11-14 01:50:57 +08:00
"dependencies": {
feat(babel6): Initial babel conversion
2016-05-04 03:37:32 +08:00
"babel-register": "6.8.x",
feat(tests): add integration tests comment Adding test harness Using key strokes in main window test Tests work now Clean up argument variables Rename list manager and get rid of old spec-helper methods Extract out time overrides from spec-helper Spectron test for contenteditable fix spec exit codes and boot mode fix(spec): cleanup N1.sh and make specs fail with exit code 1 Revert tests and get it working in window Move to spec_integration and add window load tester Specs pass. Console logs still in Remove console logs Extract N1 Launcher ready method Make integrated unit test runner feat(tests): adding integration tests Summary: The /spectron folder got moved to /spec_integration There are now unit tests (the old ones) run via the renamed `script/grunt run-unit-tests` There are now integration tests run via the command `script/grunt run-integration-tests`. There are two types of integration tests: 1. Tests that operate on the whole app via Selenium/Chromedriver. These tests have access to Spectron APIs but do NOT have access to any JS object running inside the application. See the `app-boot-spec.es6` for an example of these tests. This is tricky because we want to test the Main window, but Spectron may latch onto any other of our loading windows. Code in `integration-helper` give us an API that finds and loads the main window so we can test it 2. Tests that run in the unit test suite that need Spectron to perform integration-like behavior. These are the contentedtiable specs. The Spectron server is accessed from the app and can be used to trigger actions on the running app, from the app. These tests use the windowed-test runner so Spectron can identify whether the tests have completed, passed, or failed. Unfortunately Spectron can't access the logs , nor the exit code of the test script thereby forcing us to parse the HTML DOM. (Note this is still a WIP) I also revamped the `N1.sh` file when getting the launch arguments to work properly. It's much cleaner. We didn't need most of the data. Test Plan: new tests Reviewers: juan, bengotow Differential Revision: https://phab.nylas.com/D2289 Fix composer specs Tests can properly detect when Spectron is in the environment Report plain text output in specs fixing contenteditable specs Testing slow keymaps on contenteditable specs Move to DOm mutation Spell as `subtree` not `subTree`
2015-11-20 07:29:49 +08:00
"bluebird": "^3.0.5",
ci(spectron): Add support to execute spectron/chrome-driver tests Summary: - Sets up spectron test suite inside its own directory and with its own dependencies (must run on a build of the app) - Sets up dummy test - Adds `run-spectron-specs` grunt task, and adds it to cibuild task - Cleans up spec tasks code Test Plan: - Run specs Reviewers: evan, bengotow Reviewed By: bengotow Differential Revision: https://phab.nylas.com/D2256
2015-11-14 01:50:57 +08:00
"jasmine": "^2.3.2",
test(contenteditable): add in contenteditable list specs
2015-12-03 04:43:11 +08:00
"spectron": "^0.34.1",
"chalk": "^1.1"
ci(spectron): Add support to execute spectron/chrome-driver tests Summary: - Sets up spectron test suite inside its own directory and with its own dependencies (must run on a build of the app) - Sets up dummy test - Adds `run-spectron-specs` grunt task, and adds it to cibuild task - Cleans up spec tasks code Test Plan: - Run specs Reviewers: evan, bengotow Reviewed By: bengotow Differential Revision: https://phab.nylas.com/D2256
2015-11-14 01:50:57 +08:00
}
}
Reference in a new issue Copy permalink