I'm sure that I'm making some kind of rookie mistake, but I'm using EclEmma for the first time right now and can't figure out, despite checking numerous guides, how to export my coverage report. For reference, this is on Windows 8 x64 and using Eclipse Kepler (let me know if you need any more information than that).
I can see that the EclEmma has successfully run, and I can get into and play with the Coverage view as below:
However, right-clicking anywhere in the report offers only an option to "Export Session," never "Export Report," and going through my File -> Export dialog doesn't seem to do any better. I tried exporting the session as XML and a few different configurations, but it never got the code coverage report that I was looking for.
Is there something I'm doing wrong or need to ensure before I can export it? Thanks in advance.
As you do before, click right button and select "Export Session".
Type "report" and you can find the "coverage report" option.
Click "next"
You can get the Export report panel.
Related
I'm reviewing install4j (9.0.7, windows 10) and have created a simple java installer with some additional screens to enter custom variables that we use to configure our product.
The installer that is generated seems to work ok.
Because it is recommended for search purposes (to see were for example you are using custom variables) to generate a "project report" I tried this and to my surprise it generates an empty html file of 0kb in size.
Is this a "bug" or did I miss something that I should have done before generating the project report.
Any help is greatly appreciated.
This is a regression that can happen in 9.0.7, it will be fixed in the next bugfix release. Please contact support#ej-technologies.com to get a build where this is already fixed.
I have a lot of test cases which are currently in Excel that I need to migrate those to VSTS/Azure DevOps. Can someone recommend me a good way to do that.
This is a manual way but maybe it will be useful for you.
On IE or Edge. You can try the grid view on your test plan and just copy/past test cases:
In test suite select creation of test cases with grid view:
Copy/past you test cases and save edits:
Install Team Foundation Server Office® Integration (Excel Add-In)
Open Excel and go to Team Tab and then click on New List
Connect to your TFS
Choose Input List then click OK
Click on choose columns so we get all the necessary ones for creating test cases
The Work Item item is set to "All Work Item Types", change this to "Test Case"
Click Add Required and you should have about 8 columns, then click ok
Now you should see a slightly different excel worksheet. -Change the work item type on the first line to "Test Case" and it should auto-populate the defaults
I searched for almost an entire week before getting this to work and there were no answers online so, I thought I would share.
Install the Test & Feedback plugin for Chrome. (*this may or may not be necessary but it worked for me and I have this installed)
Navigate to the *old view of the Test Plan.
Note: To confirm you are in the 'old view', a blue link in the upper right hand side that says 'Switch to new view' will be displayed.
Note: When you hover over the test icon in the left navigation bar, choose the option "Test Plans" not "Test Plans*". The latter is the new view.
Select the folder that contains the test cases on the left and wait for the Test Cases to populate in the pane on the right side.
Click "Offline Test Execution" at the top of the pane above the Test Cases.
Choose to export the entire Test Plan or entire suite of Test Cases, etc., and click 'Export'.
Note: If you try to export the entire plan or several folders worth of test cases and the export fails, choose less test cases at a time to export.
Hope this helps.
I was able to upload the test cases including the test steps using Microsoft Test Manager and which can be accessed through Azure devops.
If you guys have Microsoft Test Manager, please find the required information at the below link.
https://github.com/premboyapati/Test-Case-Migrator-Plus
Eclipse allows multiple source windows (obviously) and even multiple console windows to be open at the same time.
I'm looking to see if there is a way to open multiple Variable windows at a time. While debugging I sometimes want to visually compare several structures and this would be easier if I could open each object in its own Variable window.
Thanks.
Yes, in the upper right hand corner of the Variables window, there should be a button 'Open New View'.
EDIT: I'm not sure if this is necessarily the best way to get what you want, but it worked for me. I just downloaded a fresh Kepler install, and you can get the "Open New View" button by installing the C/C++ Development Tools. To install go to Help > Install New Software.
Note: I had to clean my workspace after installing because I was getting "Editor does not contain a main type errors". But after that everything worked fine and the button was available.
Hope this helps!
right now we are using svn to share code for our force.com/visualforce project. It works great controllers, components, pages and static resources.
The problem is it seems the salesforce.schema file is not really a local file, its a placeholder that checks your server and tells you your current schema.
We want to baseline our schema changes/updates to a file so we can share in svn.
I found this:
http://boards.developerforce.com/t5/General-Development/Custom-Objects-in-Force-com-IDE/td-p/445363
But we cant seem to figure out what do do/how to get it to work.
So in a nutshell, we are looking for a way for Developer A to create a custom schema object in their own SF Sandbox, somehow get this info into a file in svn (ideally through the force.com ide), then check it in so developer B can check it out and apply it to their server. (the same way we do for code).
Any help would be great!
thanks
Joel
Ok, we finally figured this out through trial and error:
To make this work:
right click on project, click "Force.com/Add Remove Metadata Components"
go down to custom ojbjects, open that up, make sure all your custom objects are checked, click apply, then say "NO" to dialog
then right click on src and click "Force.com/Syncronize with Server, find your objects, and click "Apply Server to Project"
now your files will be local, check them into SVN and you are golden.
Hi I am going to dig a little more in Java so I would like to see how the program executed in the core class. For example, I would like to know how String.chatAt() is implemented, so I set breakpoint and tried to step into with debug mode. But I failed, I set bp at the second line when the program hit it, I used step into it still continue to the third line.
String a = "1231231241241";
char b = a.charAt(0);
System.out.println(b);
I think it should go into the source and show "no source found" and then give me a chance to attach the source file, right? But why it cannot get in? I can only use ctrl+right click on a method to get into source and attach.
It might be that your Eclipse is not setup to run with JDK, it might run with JRE instead.
Check this link.
Also, I might suggest you to try and use Maven for your Java projects management, it makes the life so much easier, when you get a grasp of it.
Most likely, you have the "Step filtering" functionality activated.
When debugging, it can sometimes be a bit annoying when the debugger steps into trivial classes whose internals you were not really interested in. Because of this, you can configure "Step filters". Classes or packages that are added as step filters will be ignored by the "Step into" operation.
If you want to configure which classes/packages should be included in the step filter, you can go to: Window --> Preferences --> Java --> Debug --> Step Filtering
My guess is that you have a java.* package filter defined there, meaning that the debugger will never step into any class within a package which starts with "java". Uncheck this package filter if you want to be able to step into java.lang.String
Alternatively, if you want to activate/deactivate step filtering completely, you can do this by clicking the Use step filtering button in the debug view, as shown below:
To be able to look at the code of libriaries you are using in your project you should configure your build path by attaching the soruces and JavaDoc.
Source Lookup
Seems like you dont have the "Source Attachment" set. Go to Preferences -> Java -> Installed JREs. Select the JRE you use and click "Edit", then set the Source Attachment to the src.zip that comes with the jdk by selecting the jars and clicking "Source Attachment" :).
You can do this with all of the jars at the same time by selecting them via shift-click.
for example in this System.out.println("test") piece of code if you want to step into System class just click on System and click F3 you will be redirected to attach the source code if you haven't already attached.Just attached the src folder of the jdk