Because I think it always makes/build/etc every time I run the project, unlike in eclipse when I run the project it immediately installed in the device. Is there any workaround here to run the project like in eclipse?
Thanks.
Android Studio is slower than eclipse in many ways. I don't think there is a way of speeding the software up all together from the user side, all we can do it wait for a update for the software.
Follow this post: Android studio Gradle build speed up
Might help you make things faster on Android Studio.
Related
I am having an issue getting selenium end to end tests to work after an automated deployment using visual studio team services (VSTS).
I have a build working that generates a build artefact. This is triggered from VSTS but runs on an on premises build server. I have a deployment working that deploys to an on premises development web server. All this works including unit tests running after the build.
When I try to add testing after the deployment is when I run into the problem. The tests are to be run on the build server and point to the dev server website. The deployment has two phases. A deploy and then an agent phase that runs a test assemblies task using the build agent on the build server. The problem seems to be that the test dll's are not being included in the build artifact and so are never found when the test process runs. Deploy setup us as follows.
I have a copy files before the publish artifact in the build definition that seems to copy the files in to the right place but they are not included in the zip file artefact. I've looked at several websites and posts on here but I still seem to be missing a vital bit of knowledge that will get this working.
Use of the log did help as recommended so thanks for that.
I have managed to get this working. I separated the selenium tests out into a separate solution and built that separately creating it's own build artefact. I then added this to the agent task in the deploy. This worked. The only thing I need to get sorted now is the correct search path to find the test DLL's. It's not quite as dynamic as I would like at the moment. I can play tunes on that until I get it right though.
I accept this is working around rather than solving the original problem but needs and timescales must. I think moving the end to end UI tests out of the main solution makes sense anyway but no doubt others may think differently.
Thanks for your help everyone
I want to write a custom IDE on top of IntelliJ Platform. Android Studio is an example. It was built based on IntelliJ Platform and was designed to support Android application development.
There are lots of git GUI out there. However, in Linux, I don't satisfy with any. That is my motivation to write a git IDE for Linux. IntelliJ IDEA already have a very good Git plugin. Using IntelliJ IDEA is a solution. But it is too heavy for opening entire project with different functionalities (Run, Debug, Refactor...) for just Git operations. Therefore, I want to make that plugin a complete IDE for only Git operation.
On IntelliJ Platform forum page, there are tutorials to write plugins. However, it doesn't have the guide for writing a complete IDE.
Are there any tutorials to help me get started?
IntelliJ platform is probably not the best choice for writing a general purpose RCP applications.
https://intellij-support.jetbrains.com/hc/en-us/community/posts/207769065-Developing-a-desktop-Business-Application-using-the-JetBrains-Platform
Git plugin has 65k lines of code, you are talking about gutting ~13M lines IDE (respectively 3M lines of pure Java source code).
The title pretty much sums it up. I'm brand new to IntelliJ IDEA, and it's not clear to me if I need separate installs, one for my Android projects and one for my vanilla Java (and beyond) projects. I've read through the docs and couldn't find an answer. Thanks
Android Studio is self-contained for Android projects. If you're going to be doing significant plain Java development, you may prefer to use IntelliJ, becuase Android Studio is in many ways tuned to doing Android development, and could be restrictive for other types of projects.
For example, Android Studio is designed to work with the Gradle build system, which may not be what you want for Java projects; it's possible to use Android Studio with IntelliJ's built-in Java builder, though you can't create new projects that way.
If you are going to be working with many non-Android Java projects, then IntelliJ is definitely the way to go. You may even find that after you start using it you will stop using Android Studio altogether.
IntelliJ includes most of what Android Studio provides for Android development as well as fantastic support for other types of projects. Additionally, IntelliJ has far fewer issues for Android development.
As for running both - they keep all their files separate (config, etc) and it is perfectly safe to run both (even at the same time).
If you do decide to use both then I would just advise you to keep your Android SDK install in a separate location - it just makes it easier to manage and you can point both at a single updated target :)
I'm trying to add a step on my Jenkins server for testing my iOS app automatically. I know how to deploy the TestStudio app on the simulator but I have to:
run the Test Studio app on the simulator from the Terminal console
execute the test (still from terminal)
I think that using terminal commands is the best solution to integrate this operation in a Jenkins job,but if anybody comes up with a better idea I would be more than happy to hear that. Any idea how to perform these tasks?
Currently it is not possible to execute Test Studio for iOS tests from the command line.
Our next major version, due out in early 2013, includes an API automation framework. With that you can write coded unit tests that can be triggered from the command line and integrated with Jenkins.
I've got a project using Maven 2 as the build tool. Now I am using Netbeans 6 as my IDE and really want to be able to use the profiler. Is there any way I can get this to work?
I thought this might be more complicated. It wasn't. To use the Netbeans profiler with your Maven 2 project you simply need to add a single pair of parameters when running your java app. Call up the project's Properties dialogue, select the "Run" tab and add something like the following to the jvm args:
-agentpath:"C:\Program Files\NetBeans 6.0\profiler2\lib\deployed\jdk15\windows\profilerinterface.dll=\"C:\\\"Program Files\"\\\"NetBeans 6.0\"\\profiler2\\lib\\"",5140
This meant that now when I ran my app (F6) execution would wait for me to attach the profiler. Cue real time graphy goodness. Sweet.