I have an ember-cli project and all the tests are written using ember-qunit. I am using browserstack-runner to run the tests on Browserstack.
browserstack-runner provides the plugin for qunit which I am using. Below is my browserstack.json
{
"username": "USERNAME",
"key": "SECRETKEY",
"test_framework" : "qunit",
"test_path": ["tests/index.html"],
"timeout": "120",
"browsers": [
{
"browser": "chrome",
"browser_version": "latest",
"os": "Windows",
"os_version": "7",
"browserstack.debug": true
}
]
}
Tests are running correctly on browserstack. the only problem is, even after all the tests are run(passed) there is no activity and I am getting timeout error after specified value(120s).
I am not able to understand why it's happening. I guess it has something to do with plugin which is written specifically for qunit and not ember-qunit, which is a wrapper arount qunit.
Has anyone tried integrating browserstack with ember-cli project then please guide me.
Related
I'm trying to use a modified version of imgui through vcpkg.
I've created a git repository to be used for the registry (https://github.com/altschuler/vcpkg-custom-ports), and copied over the imgui port configuration, and made the changes I needed (following guides like this and this).
However, vcpkg seems to ignore the entry for the custom repo in vcpkg-configuration.json, it simply doesn't load anything from it (I know because I tried changing the repository url to something that doesn't exist). If I set the default-repository to my custom one it does load stuff, but then all the packages I want from the builtin registry obviously fail to install.
Note: the reason I need a custom port for imgui is that I need to compile some definitions (basically just do target_compile_definitions in its CMakeLists). If you know of an easier way to do that I'm all ears.
vcpkg-configuration.json:
{
"registries": [
{
"kind": "git",
"baseline": "e3b33f3a548f20ba06b2959aa3701bd50ece0638",
"repository": "https://github.com/altschuler/vcpkg-custom-ports.git",
"packages": ["imgui"]
}
]
}
vcpkg.json:
{
"name": "tester",
"version-string": "0.1.0",
"dependencies": [
"lager",
"sdl2",
{
"name": "imgui",
"features": ["docking-experimental", "sdl2-binding", "opengl3-binding"]
},
"immer",
"cereal",
"rxcpp",
"range-v3",
"glew",
"boost"
]
}
Try setting an environment variable
VCPKG_FEATURE_FLAGS=manifests,binarycaching,registries
AFAIK, some features are not enabled by default. Seems that manifests are automatically enabled, so vcpkg.json gets picked up, but perhaps "registries" are not enabled by default. (Disregard "binarycaching", if you don't use it).
This is what is working for me.
What I'm trying to do seems simple enough, but it's been crazy hard to actually get there. I have a Django application that runs in a docker-compose environment, and I want to run and debug the unit tests with breakpoints in Vscode.
Since this is a big project with a team that doesn't necessarily use vscode, I can't add libraries willy-nilly (like ptvsd, for example). I'm hoping there's a magic configuration for tasks.json and launch.json that will makes things work.
I have a container for a postgres database, one for django, and one for redis, all defined in docker-compose.yml. There's a command that I can run in the terminal that will run the tests, it's:
docker-compose run --rm app python manage.py test
where app is the django app container. I'd love to be able to run this command in such a way that it can hit breakpoints in vscode.
My incomplete stab at the launch.json file looks like this:
{
"configurations": [{
"name": "Docker: Python - Django",
"type": "docker",
"request": "launch",
"preLaunchTask": "compose-for-debug",
"python": {
"pathMappings": [{
"localRoot": "${workspaceFolder}",
"remoteRoot": "/app"
}],
"projectType": "django"
}
}]
}
And my tasks.json:
{
"version": "2.0.0",
"tasks": [{
"type": "docker-build",
"label": "docker-build",
"platform": "python",
"dockerBuild": {
"tag": "dockerdebugging:latest",
"dockerfile": "${workspaceFolder}/Dockerfile",
"context": "${workspaceFolder}",
"pull": true
}
},
{
"type": "docker-run",
"label": "docker-run: debug",
"dependsOn": [
"docker-build"
],
"python": {
"args": [
"test",
"--nothreading",
"--noreload"
],
"file": "manage.py"
}
}
]
}
I think I need to convert the build task to a docker compose task somehow, but I just can't figure out how its done. It may also make sense to run the containers in the terminal, and somehow make vscode attach to them with breakpoints enabled.
Even some help with how to approach this would be great. I know it's a tricky one.
This question became somewhat popular, but a direct answer never came. If you've landed here looking for a way to hit breakpoints inside vscode using docker, my suggestion is to use the Remote Container extension.
When the container is up, right click it and open a vscode window inside of the container itself. Then everything will just work.
What should I set in Run Debug Configuration in WebStorm to debug a app created by create-react-native-app?
I'm at a loss on how to debug since it doesn't use ~/.node_modules/lib/node_modules/react-native-cli but a custom module called react-native-scripts to start the compiling:
package.json:
"main": "./node_modules/react-native-scripts/build/bin/crna-entry.js",
"scripts": {
"start": "react-native-scripts start",
"eject": "react-native-scripts eject",
"android": "react-native-scripts android",
"ios": "react-native-scripts ios",
"test": "node node_modules/jest/bin/jest.js --watch",
"menu": "adb shell input keyevent 82"
},
You have to use Webstorm/Intellij 2018.1 (through EAP at the moment)
https://youtrack.jetbrains.com/issue/WEB-26951
https://blog.jetbrains.com/webstorm/2018/02/webstorm-2018-1-eap-181-3263/#debugging-expo
I dont think you can do this, at least not in an easy way, and why would you wan't to do it anyway?
React Native ships with great debugging capabilities "out of the box" via Chrome Developer Tools.
Here you can debug code, both running on emulators, and even better on a real device.
See here for details: https://facebook.github.io/react-native/docs/debugging.html
I am currently wondering, why ESLint is not working in my project in Visual Studio 2017. There is the file ".eslintrc" in the project-root:
{
"extends": "defaults/configurations/eslint",
"env": {
"browser": true
},
"globals": {
"xhr": true
},
"rules": {
"eqeqeq": [ "error", "always", { "null": "ignore" } ]
}
}
If I remove the line with "eqeqeq", everything is working fine. But as soon as I add this line, no errors will be displayed at all.
Question 1: Is there any way to see an error-message about the issue ESLint obviously has?
Question 2 as a fallback: What is the issue with this line?
Thanks to btmills I took a dive into the sources and found the version: VS 2017 uses ESLint 2.0.0 (released 2016-02-12).
The correct configuration is:
"eqeqeq": [ 2, "allow-null" ]
Documentation is available here:
Getting started
Rules
The links from the error-list in VS 2017 lead to the current documentation, where you can find many features that do not work in version 2.0.0.
Is there a way to use lein's REPL in VS Code? I mean, using tasks.js, or something.
I wanted an integrated enviroment to run, test and build my clojures applications. I think maybe I could achieve something like this using vs code, because it has support to third parties compilers.
I could use lein run, but it did not work with lein repl.
I've read tasks' documentation, but there's nothing related to REPL.
Here's the tasks.js code I've used:
{
// See http://go.microsoft.com/fwlink/?LinkId=733558
// for the documentation about the tasks.json format
"version": "0.1.0",
"command": "lein",
"tasks":
[
{
"taskName": "run",
"showOutput": "always",
"args": ["run"],
"isBuildCommand": true,
"isWatching": false
},
{
"taskName": "repl",
"showOutput": "always",
"args": ["repl"],
"isWatching": true
}
],
"isShellCommand": true
}
As the author of Calva I can recommend it. 😀
Seriously, at the moment it is supporting interactive programming the best. There is a short summary of what it can do in the Editors section of the shadow-cljs user guide: https://shadow-cljs.github.io/docs/UsersGuide.html#_calva_vs_code
Updated (July 2021)
For Clojure and ClojureScript development in VSCode, Calva is the recommended plugin, as it has added a lot of support.
Original Answer (2016)
There's extension available now which you can use.
Github
VS Code Market Place
I don't believe a real REPL is possible at the moment in VSCode.
With that being said, this is currently being worked on over here: https://github.com/Microsoft/vscode/issues/547