balderdashy / balderdashy/sails
Testing with Parasails
- Dominant language
- JavaScript
- Stars
- 22.8k
- Forks
- 1.9k
- PR merge metrics
- No merged PRs in 30d
Description
**Node version**: N/A
**Sails version** _(sails)_: N/A
**ORM hook version** _(sails-hook-orm)_: N/A
**Sockets hook version** _(sails-hook-sockets)_: N/A
**Organics hook version** _(sails-hook-organics)_: N/A
**Grunt hook version** _(sails-hook-grunt)_: N/A
**Uploads hook version** _(sails-hook-uploads)_: N/A
**DB adapter & version** _(e.g. sails-mysql@5.55.5)_: N/A
**Skipper adapter & version** _(e.g. skipper-s3@5.55.5)_: N/A
Developing on Parasails is quite arduous.
So, testing Frontend logic without running E2E tests would help a lot to ease friction.
Is there any documentation/example which shows how to run smaller unit tests on a Parasails application running Vue 2.6?
Ideally, there should be a way to run unit tests via the vue-test-utils package. Not able to get this working due to the nature of Parasails (specifically how it expects Frontend dependencies to be inserted into the Assets directory)...
@mikermcneil @rachaelshaw @eashaw
Contributor guide
Research direction
Start by reviewing how Parasails inserts frontend dependencies into the Assets directory for a Vue 2.6 application, then compare that setup with vue-test-utils. Document a reproducible unit-testing example that runs without E2E tests; done means a newcomer can follow it successfully.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- documentation, frontend, testing
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100