- `create` on the navbar opens the getting started tutorial if the user is not logged in
- replaced any other use of `tip_bar=getStarted` with `tutorial=getStarted` (with the exception of Tips page)
- did not replace other uses of `tip_bar=home` as those should probably go to the new tips/ideas page.
set-cookie causes the cache to not cache the page. Since we’re not trying to track the user beyond, we don’t want to try resetting the cookie again with the same info
* put helper functions in separate file following Paul's style in scratch-gui
* remove console statements
* address review comments, object destructuring
* added new tests for invalid username/ passwords and the + New Project, + New Studio buttons
* uncomment out test after talking to Ray
* added a test for no username and no password
* Add error checking and testing for translations. Also make build-locales quieter if there are no problems.
* Allow build with broken translations (to allow development), but fail test so that broken translations don't get merged or deployed
* put helper functions in separate file following Paul's style in scratch-gui
* remove console statements
* address review comments, object destructuring
* add tests for signing in and my stuff
* flesh out tests, reorganize a bit
* add more tests
* tests for my stuff & signing in
* fix some of the errors causing build to fail
* pass in credentials from commandline rather than uncommitted file
* switch root back to staging
* address pr review comments, rename username & password vars
* update testing readme
* added a test for the stats page
* add newline at end of file
* added additional tests for more charts on the stats page
* fixed starting URL value (should be staging, not prod)
* Put close parens on new lines
* change comment style
* Add waits to prevent intermittent failure
* Switch root url back again to staging
* try new style of test & remove breaking tests
* moving away from t.ok
* check for class value rather than t.ok
* remove comments, use correct comment style, note not testable on staging atm
* add messages for tests
* more arrow functions
* remove selenium from package.json
* Add package.json & README for the integration directory
* add newline at end of file
* add chromedriver dependency
* test for missing string ids
* Switched to multiple tests (1 per intl page) and changed comment style
* Add back in comment I accidentally . Add comment for the function.
* Change variable names, call function in-line
This also moves all helper methods in `configure-fastly` into a separate utility file, and adds some additional unit tests for those utilities now that they are separated.
We’ve now exceeded our max number of characters for a condition in the Fastly API, and we need to make it larger to accommodate regex conditionals that can match on any of the routes in www currently.
This fixes the issue by moving the conditions – and the states that are affected by it, like setting the backend or cache ttls – to two custom vcl files that are updated via the Fastly API. One is for the `vcl_rev` config, and one is for the `vcl_fetch` config.
* automated tests for footer links
* renamed navbar test file and removed footer links to separate file
* run with make smoke
* added tests for join scratch and sign in in navbar
* fix linter errors & update www links
* addressed some of ray's comments
* fix failing test - projects row link
* maybe fix error?
* continue switching to click, convert so it runs with disabled selenium promise manager, and refactor to be less location dependent
* finish switching off of implicit reliance on selenium promise manager
Added tx-import, expects TX_TOKEN environment variable to be set to an API token for Transifex. If no API token exists it’ll just use the default English strings for everything.
Removed the localization spot checks because they were checking tha json got built from po files. With Tx-import the files are already json, and may possibly be missing.
* Don’t allow duplicate strings in a single l10n file
Added check_duplicate_strings to test for duplicates in a single file.
removed duplicates - tried to keep the more generic ‘key’
* revised test case for safer file reads
Since it's using `require` to get the localisation strings, check if the error is `MODULE_NOT_FOUND` before moving on – because if it isn't, then there is an unknown error that should be thrown. Thanks @rschamp for the suggestion!
Before we were using glob, which was about to start failing on subdirectories in views (which we started using in `conference`). Instead of searching for `l10n.json`, it seemed more appropriate to instead look for localization by using the configured pages that need to be localized.
