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

Testing - Automate and update jsunit test suite #12

Closed
thisandagain opened this issue Jan 19, 2016 · 5 comments · Fixed by #1147
Closed

Testing - Automate and update jsunit test suite #12

thisandagain opened this issue Jan 19, 2016 · 5 comments · Fixed by #1147

Comments

@thisandagain
Copy link
Contributor

Test suite will need to be updated to reflect new grammar, blocks, and generators. While doing so, we should automate the jsunit and jslint testing via Travis-CI which should help with open source contribution quite a bit.

@tmickel
Copy link
Contributor

tmickel commented Aug 24, 2016

@thisandagain Do you think we're ready to have eslint run with Travis? I'd be pretty happy if that was working, even if it doesn't yet pass the linter. Seeing the tests failing would be a good motivator to fix it up... :) Don't know how to set it up (or if I can), though.

@thisandagain
Copy link
Contributor Author

@tmickel Agreed. That sounds great. You are an admin so you should be able to enable Travis for this repo from your https://travis-ci.org settings page.

@tmickel
Copy link
Contributor

tmickel commented Aug 29, 2016

Ok, I did that! Not sure how to do jsunit but I'll look into that also for a bit

@tmickel
Copy link
Contributor

tmickel commented Aug 29, 2016

Hmmm, given the weirdness of the closure jsunit setup and the small number of tests, I wonder if it might even be worth it just to rewrite the tests using our normal test framework...

@RoboErikG
Copy link
Contributor

We're also looking into Travis on the Blockly side. It's not moving very fast, but we'll let you know if we get anything working there.

picklesrus pushed a commit to picklesrus/scratch-blocks that referenced this issue Aug 4, 2017
…s, + menu bar (scratchfoundation#83)

* Covers parts of these issues: GUI layout panes (scratchfoundation#69), sprite libraries (scratchfoundation#12), import buttons (scratchfoundation#64), menu bar (scratchfoundation#67), and sprite info area (scratchfoundation#53)

~ Refactored layout pane structure by removing `display: flex` from `.box`, by default. Declaring flex instead only where specifically needed. This helped fix layout quirks, and should help us avoid hard to find issues related to nested flex boxes

~ Added descriptive classnames to boxes/containers/wrappers. Moved more padding, margins + layout into these wrappers to help with component reusability.

~ Set up a spacer unit variable inside `gui.css`, to start keeping consistent padding, margins and rounded corners between panes. Used [CSS/PostCSS Modules](https://github.com/css-modules/postcss-modules-values) to avoid SCSS dependency.

~ Refactored inline styles from JSX, into CSS files. 2 reasons: a) prepping for reuse of CSS Module variables. b) Feels easier to debug complex flex layouts when all the styles are in one place vs JS/HTML/CSS syntax mixed together

~ Added menu bar into layout via new component, and sprite info header in sprite selector pane, with stubs for the labels + forms. Sprite items are correctly scrolling, while leaving the header fixed, in Chrome. Mostly working in FFx. Not working in Safari, IE yet.

~ Style pass on library modal

~ Experimenting with a few different transition styles: Logo in menu bar, sprite library items, Add buttons.
picklesrus pushed a commit to picklesrus/scratch-blocks that referenced this issue Aug 4, 2017
* Design pass on libraries to make sprites look more like they do in the SpriteSelector. Fixed scrolling overflow when reaching the bottom
* Started a colors variables file
* Added a light transform on sprite item hover

Related scratchfoundation#12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants