This repository has been archived by the owner on Nov 26, 2020. It is now read-only.
Project Testers and feedback needed! #49
Labels
Comments
|
I'd like to extend a special invitation to my friends from the Cypress team: @brian-mann, @jennifer-shehane, @bahmutov, and @chrisbreiding. This repo has been completely rewritten since you saw it last. As this is going to be used to teach people how to use Cypress, I thought you'd appreciate a chance to look and provide some feedback on how I'm doing things :) Feel free to open a new issue (or PR!) if you have comments/suggest/feedback. Thanks! |
Closed
This was referenced Feb 2, 2018
|
verified on win 10 home with node: v9.1.0 and npm 5.6.0 |
|
Thanks for letting us know about these issues - so sorry about the state of things on windows platform - that OS is a can of worms ;) |
|
I think I see what @Dubes is experiencing. In the cypress error section, it says a missing system dependency should be installed first. Specifically xvfb; the exiting error code given by test:e2e was 255. After running |
|
Thanks for digging @edm00se! |
|
I think I got past that all; it's mostly Cypress complaining about a lack of GUI it can use. Using Windows System Linux — Ubuntu (Win10's "BASH"), I had to install some dependencies; some of which didn't surface without running Here's a command to install the required dependencies. sudo apt-get install xvfb libgtk2.0-0 libxtst6 libxss1 libgconf-2-4Output of `npm run setup --silent` after installing dependencies.
Output of `npm run validate` after installing dependencies.
@kentcdodds If you want to peruse the two output logs, it may be worthwhile to verify that the only errors I have remaining are the intentional ones for out of the box (freshly cloned) behavior. |
|
That's pretty weird. From what it looks like, your machine failed to install dependencies properly. Could you try running: |
|
🤔 Well, I ran it. I'm not sure it was terribly enlightening. Output of `npm run clean && npm run setup`.
Output of `ls shared/node_modules/`
|
|
Could you verify that It's saying it can't find that module, but if it's there for you then I don't know what's up :-( |
|
Confirmed, it exists and exports an array of Latin looking words. Probably a module resolution issue? I did see in the logs above an issue with optional dep fsevents being skipped since os type "linux" and "darwin" weren't met. 🤔 😞 |
|
Sounds like it. Super odd that nobody else appears to be experiencing this issue 🤔 I just tried again to be sure there's not a dependency problem and it worked for me. |
|
For the record, this seems isolated to my Windows System Linux ("Bash on Ubuntu on Windows") environment. My cloned copy that ran purely on Win10 in PowerShell seems to run perfectly fine with both the setup and validate scripts. |
|
Hi Kent, Here is the error info. FAIL demo/integration/tests/users.js ✓ can get users (6ms) Test Suites: 1 failed, 1 total Every thinig is exactly same as you showed at FEM. I have Node v9.5.0, npm 5.6.0, yarn 1.3.2 |
|
@davidnomo, it looks like you're on an old version of master or a different branch. Make sure you're on the |
|
I've given the workshop now and I don't think there were any serious setup issues so I'm going to close this issue. Thanks everyone! |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hey folks 👋
I have a few needs for this project!
Project testing
I could use a hand making sure this project can run on anyone's computer and is intuitive to set up. If there is a problem with your environment, this project should hopefully provide enough context for you to fix the problem on your own.
I especially need testers on Windows and Linux machines because I work exclusively on a Mac 🍎.
Instructions:
I'm not going to explain how to set up the project in this issue. Please just follow the instructions on the README. If something's unclear or you experience issues, please file a new issue about it❗️ If everything goes well for you, please add an emoji reaction to this comment of 👍. Thanks so much!
Feedback
After you've set up the project, if you'd like to go through some of the tests, please do so. Note that the testing is not yet split up for exercises/quizzes/workshoppy things yet. It's all just tests like a normal app would be. In the next few weeks I'll be splitting things up to make them conducive to the workshop experience.
Instructions:
Because this workshop is instructor led, there are no instructions on how all the scripts work. So just pull up the root
package.jsonand look at the available scripts. Hopefully that should be enough to get you going. The most important scripts though are:npm run testto run the client/server unit/integration tests in watch modenpm run test:e2eto run the cypress tests in development modeIf anything is unclear 🤔 to you about how things work or why I made certain decisions, or if you disagree 🙅 with some of my decisions, please feel free to file an issue and make suggestions or ask questions. I make no promises I'll follow your suggestions, or even take the time to justify my position (I'm very limited on my time). I'll try though :)
Thanks! 🙏
Thank you so much for taking the time to help me out with this! I'll be giving part of this workshop at Assert(js) later this month. Then I'll be giving it in March in San Francisco (details forthcoming), and in April for Frontend Masters! 🕶
The text was updated successfully, but these errors were encountered: