As we are planning to add support for testing external plugins, I have adjusted build script to also copy those tests (if -t flag is present). This is a part of bigger task, see also ckeditor/ckeditor4#4234.
How to test - only this change?
Add any plugin with tests to /plugins/ directory (or just some fake test to `wsc`, `scayt` plugins).
Run build.sh full all -t.
The tests folder should be present in resulted CKEditor 4 build (so under build/version/full-all/ckeditor/plugins/plugin-name/tests/).
How to test - entire workflow?
Switch to this branch.
Replace ckeditor submodule with your local ckeditor4 copy (switched to t/load-external branch - see ckeditor/ckeditor4#4234).
Checkout Export to PDF plugin repo somewhere (on t/79 branch) and build dist version (npm i && npm build).
Copy Export to PDF plugin dist folder and tests to /plugins/ folder like:
All unit and manual tests for Export to PDF plugin should be there and should pass the same way they pass when run from external repo (so basically just pass).
As we are planning to add support for testing external plugins, I have adjusted build script to also copy those tests (if
-tflag is present). This is a part of bigger task, see also ckeditor/ckeditor4#4234.How to test - only this change?
/plugins/directory (or just some fake test to `wsc`, `scayt` plugins).build.sh full all -t.The
testsfolder should be present in resulted CKEditor 4 build (so underbuild/version/full-all/ckeditor/plugins/plugin-name/tests/).How to test - entire workflow?
ckeditorsubmodule with your localckeditor4copy (switched tot/load-externalbranch - see ckeditor/ckeditor4#4234).t/79branch) and build dist version (npm i && npm build)./plugins/folder like:cp -r .../ckeditor4-plugin-pdfexport/dist /plugins/exportpdfcp -r .../ckeditor4-plugin-pdfexport/tests/ /plugins/exportpdf/tests/full-allpreset -build.sh full all -t.All unit and manual tests for Export to PDF plugin should be there and should pass the same way they pass when run from external repo (so basically just pass).