How to set up JetBrains IDE to run Stencil e2e tests? - ide

We're developing a design system with Stencil. We are now writing e2e tests as described in Stencil docs.
There is shared VS Code config which allows to run the tests with Visual Studio Code, but we're using JetBrains IDEs (IntelliJ IDEA and WebStorm) and it is not obvious how to set up tests to run them with IDE interface.
Did anyone managed to set up them in JetBrains IDEs?

You can try using the Node.js run configuration with similar setup: specify the project root folder as a Working directory, path/to/node_modules/.bin/stencil as JavaScript file, add test --e2e $FilePath$ to Application parameters

Related

How to debug visual studio code extension in intellij

I have a visual studio code extension, but usually I develop in java so I'm much more experienced in intellij IDEA than vs code. So my question is, is there a way to debug my vs code extension in intellij?
Intellij has plugins for compiling and run typescript programs, it also supports node development.
I think I should create an npm run configuration, where I put npm compile script from package.json to before launch section and then run another npm script that will launch the vs code with the compiled extension. But I don't actually know how this script should look like, or if there is a better way to go.
Try importing all the libraries first.
InelliJ has an excellent feature of running each and every method and class individually, use that feature,
To use that feature, there is a green triangle at the right side, click on that to debug

How to setup Geb 2.0 in IntelliJ (run/debug configurations)?

I'm using Geb 2.0 (http://gebish.org/) and have downloaded the Gradle sample (https://github.com/geb/geb-example-gradle).
All works just fine on my machine with all browsers (Chrome, Firefox, ChromeHeadless).
I have imported the project in IntelliJ (latest Ultimate edition) and all normal code editing functions are working fine.
What fails is attempting to run a spec. I get an exception with the helpful hint of the path to the driver executable must be set by the webdriver.chrome.driver system property.
However, I can't figure out what to point it at. I've tried pointing at the selenium-chrome-driver-3.6.0.jar but that results in failure also.
I'm using -Dgeb.env=chrome and -Dwebdriver.chrome.driver=SOMERANDOMEPATHSHERE
Help?
The Gradle example Geb project is set up to generate the appropriately configured IntelliJ project capable fo running the specs from the IDE. Simply run ./gradlew idea and load the project by opening the geb-example-gradle.ipr file in IntelliJ instead of loading the project by importing it's Gradle build the way you do.

Source Control for Selenium Tests written in Java

In my company, I have plans to introduce Web Automation using Selenium WebDriver and Cucumber JVM using Maven builds.
Since the developers write their code in C#, they are all using TFS for source code repository and recommending the QA team also to use TFS to maintain my tests written in JAVA.
These are the questions I have got in my mind:
QA team will use IntelliJ IDE for writing Selenium tests in JAVA. Is IntelliJ compatible with TFS? Or is it a pain to configure it to work with TFS?
As we will move towards TDD very soon, we have to setup CI server as well.
Is it possible for me to run Selenium Tests triggered from TFS or do I need to use a separate CI server like Jenkins or Teamcity?
Does maven build work smoothly with TFS?
We have to adhere to stringent ISO guidelines for maintaining the source code. If I were to recommend source code repositories like github, can I ensure that the code is still secure? Is it difficult to setup the security in github?
Answering your questions regarding TFS:
IntelliJ IDEA supports TFS up to TFS 2015. Check:
Visual Studio Team Foundation Plugin for IntelliJ and Android Studio
Using TFS Integration
TFS supports CI build. After you've deployed a Windows build agent or an Xplat build agent, you are ready to define a CI build that compiles your Java app with Maven whenever your team checks in code.
Yes. Check:
Build your Java app with Maven

Instrumentation testing in Android Studio

I'm new to testing and currently trying to write some tests in Android Studio. I have a sample application module and now trying to figure out, whether the instrumentation test needs to be a module of its own or whether the tests should go inside the src folder... I have read contradicting information on the web. If anyone had a sample, that would be great!
With eclipse ADT plugin and older version of the SDK it was a requirement to put the integration tests in a separate module.
With the gradle build system and android-studio you should be able to put your integration tests in src/test/java and running them from the IDE or gradle command line without pain.
That's why you find contradicting information on the web.
Here is the reference
This post contains a very good explanantion on how to do the integration testing in Android Studio:
How can I create tests in Android Studio?

Which IDE should i use for Google's Native Client?

I'm planning to try out Google's NaCL. Which IDE should i use for developing? It would be nice to be able to compile the project from the IDE and run it in Chrome. Some basic debugging would be also very useful.
We do not have any IDE support yet. You can try Eclipse (with CDT) + Standard Make C or C++ project to automate compilation. Launching and debugging will not be possible from Eclipse.
Alternatively, you can use any editor with syntax highlighting and compile/launch by hand from cmd/bash.
Debugging on NaCl is very tricky by itself. There is no sane way to do this now.
You can use NACL_EXE_STDOUT and NACL_EXE_STDERR environment variables (set them to absolute paths to files where stdout and stderr of NaCl program will be written) plus --no-sandbox chrome flag for debug printf's.
Update (March 2014)
We have Visual Studio plugin now which can be installed with naclsdk update vs_addin. See also: https://developers.google.com/native-client/dev/devguide/devcycle/vs-addin
Also, I created a page that describes how to use Eclipse with CDT to compile and debug NaCl applications: http://www.chromium.org/nativeclient/how-tos/debugging-documentation/debugging-with-debug-stub-recommended/debugging-nacl-apps-in-eclipse-cdt