I have a .fpr report generated by HP Fortify scan. I am able to open it in Audit Workbench. Now, i want to generate a PDF report from this which list all the issues with the file names, source snippet and line numbers.
I have tried various options from Audit Workbench Report Generation, but don't seem to find the right combination for being able to do so.
Can someone help me out on this? Thanks a lot in advance!
Try this command:
ReportGenerator -format XML -f abcd.xml -source abcd.fpr
I was able to generate all the issues into PDF and i think the same approach can be taken for other formats than pdf. The trick was to unchek the "Limit number of issues in each group"
Open Audit Workbench. Click Tools > Generate Legacy Report
Related
I have gone through the Opencover wiki documentation and tried a lot to figure out what would be the filter criteria for not to include test assembly as part of code coverage. Here is the problem
for eg I have many assemblies starts with sample name like sample.submodule.assembly1.dll, sample.submodule.assembly2.dll, my tests assembly also starts with sample like sample.submodule.tests.dll, here I applied the filter criteria for openCover
1.-filter: "+[sample*]* -[*tests]*"
it didn't work, not generating report file.
-filter: "+[sample*]* -[sample.submodule.tests]*" didn't work, not generating report file,
-filter: "+[sample*]* -[*]*tests*" didn't work, not generating report file too,
can somebody please advise what can be the filter criteria here to exclude all the test files from code coverage
First run OpenCover without any filters.
Now you can look at the XML report produced (or you can use ReportGenerator to turn it into HTML) and identify assemblies/modules that you wish to exclude.
now you can apply filters using the filter switch e.g.
-filter:"+[*]* -[*.tests]* -[*.Tests]*"
NOTE: no space between : and first "
or
"-filter:+[*]* -[*.tests]* -[*.Tests]*"
if you are talking about writing unit test using visual studio nunit adaptor then you have open cover UI visual studio extension available for all such purpose. it is wonderful.
Step 1) Install open cover from latest relese build https://github.com/opencover/opencover/releases
Step 2) Usuall it will install C:\Users\goma1940\AppData\Local\Apps\OpenCover (%localappdata%\Apps\OpenCover)
Steo 3) Install VS Extn from gallery https://visualstudiogallery.msdn.microsoft.com/6950a046-8919-4935-8542-c6f37956f688
Step 4) you have open cover test explorer and open cover coverage result pane as below…
I've written an ePub generator by using ZipArchive in .NET and looking at the spec (in Wikipedia) & a example.
It doesn't work! But I only get a generic error so I'm unable to fix anything from here.
Where could I go to upload my ePub and be told what is wrong with it? Or is there a tool that is better for it? I'm currently using Adobe ePub reader...
I realize this is an old question, but in case others come across this I wanted to contribute. The IDPF which is responsible for the ePub standard has a tool for checking ePubs called epubcheck. It can be found at https://github.com/IDPF/epubcheck.
In addition, they have their own online validator that uses epubcheck. It is located at http://validator.idpf.org/
I found an online validator tool at http://www.epubconversion.com/ePub-validator-iBook.jsp.
There are two basic black box approaches.
First: Generate a file and put it into a validator.
Second: Take a set of in- and output without using your code (other generator, example, do it manual). Then use a file comparison tool (maybe extract zip first).
Here is a good offline checking tool for Windows, Mac or Linux OS:
http://www.pagina-online.de/produkte/epub-checker/
It's a great tool which even i used to validate and generate epub files also clearly give errors if any.
I use the lpk_tool.exe to generate the LPK file for my ActiveX control. But it seems that Microsoft have abandoned this technology, I cannot even find the download link on Microsoft Download.
But that's not a problem, I can download it from other website. The problem is now I want generate LPK file without the GUI. I tried to find the API or command line support for LPK tool, but failed to find any. I have also asked the support form Microsoft and they don't provide the API or source code of the LPK tool.
Anyone can help me?
Is there any way to convert odt documents to doc or rtf on linux without openoffice or any library that relies on having openoffice installed ?
OpenOffice.org and its derivatives (LibreOffice, Symphony, etc) currently have one of the best converters between ODF and the Microsoft formats (besides the ODF support built into MS Office).
If those converters are not an option for you, you can choose between some alternatives: Foremost you might want to check out the KOffice project which also offers command line tools for file conversion:
KOffice - File Filters
Then there is another open source project with a free BSD license available on SourceForge:
OpenXML/ODF Translator
This project offers not only add-ins for Microsoft Office, but also a stand-alone command line version which also runs on Linux.
Then there would also be a different approach: You can automate Google Docs using command line tools:
googlecl: Command line tools for the Google Data APIs
Google Docs file conversion have internally been based on the OpenOffice.org file filters, but as far as I know they have been replaced by Aspose, a library for document formats.
Aspose is available in several versions, and as you have a Linux dependency you might want to check out their Java version.
Aspose.Words for Java
The library has its price, but you won't find another library that is not a full office suite with that quality.
If you don't want to use OpenOffice, Google Docs is your best bet. Cross-platform, web-based, and free, it takes about 2 minutes. You would upload the file, and check convert, then redownload as a doc or pdf (depends on what you want).
http://docs.google.com/
You could try this freeware (Docx2Rtf) and run it under WINE.
Checkout unoconv. It relies on OpenOffice.org its core, but it doesn't rely on any GUI packages. I assume this is what you want?
Use http://zamzar.com/ It has great support for all those formats. And is not reliant on any other installed program.
And of course, being a web page, it will work on any OS.
With issues gathering on bitbucket, I'd like to have a way to gather and back them up in the event that I need an offline copy, or no longer use Bitbucket, or something else. The site doesn't offer this service. Is there an alternative mechanism I can use?
From now on you can Import/Export your Issues:
Goto: -> Administration -> Import/Export
Youtube-Video: Bitbucket Issue Export
You can get your issues via the Bitbucket API.
Here is an example URL to get the issues for one of my projects:
https://api.bitbucket.org/1.0/repositories/christianspecht/bitbucket-backup/issues/
However, this returns a list of the issues in JSON format.
I doubt that you can do anything useful with a list of issues in JSON, but I don't know if there's a better file format for issues.
I just asked exactly that here on StackOverflow, because I'm dealing with the same thing at the moment:
Is there a standard file format for exporting issues from an issue tracker?
Full disclosure I am the author of Issue2Markdown because I really needed it.
As mentioned previously you can export your issues from Bitbucket project by going to Settings->Issues->Import & Export and then downloading the resultant ZIP file.
Inside that ZIP file, you will find JSON file and attachments archive. You can import those into some other issue repository. Or if you are like me you may be working with a remote team that is reluctant to use an issue tracker and would like to be able to read a human-readable version of the issues.
That is where Issue2Markdown comes in. You can use that to render your issues as a single Markdown document. You can find pre-built binaries for Linux, Windows, and MacOS under releases.
I hope that helps the next person who could not find the solution.
There doesn't currently appear to be any way to export your issues :(
You could export issues from settings in the repository. Then download the and extract the zip file, that would give you a json that you just could parse any way you prefer
I wrote a small python script to convert issues json file to excel that you can find it here. Hope it gives you some ideas:
https://github.com/anath2/bitbucket-issues-to-excel