Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 5 years ago.
Improve this question
I have made a couple dozens of tests for a legacy system I was handed over.
They generally test/describe some high level feature of the system, and I generally include in the test file itself a little comment about that feature. In this way, I both have a regression test suite and I'm compiling knowledge of the system in a single place, so others in the future don't have to lose all the time I lost trying to understand the (up to now) undocumented system.
Now, I was looking for some tool that would allow me to organize and see the high level features in a simpler way than having to look up to the test files. If it allowed a tag system, even better.
I have heard of Fitnesse but it doesn't look to fit really in what I'm looking for. I'm not looking for a tool to bridge the communication between the client and developers.
This project is coded in Java.
Thanks
If you moved the documentation from the unit tests to the classes you are testing, you could use either standard JavaDoc or doxygen.
Related
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 5 years ago.
Improve this question
I am using MireDot for generating documentation for my REST service.
While it is awesome for generating the models and general information on the resources, I don't believe it currently has a way of "nicely" adding concrete example input/output.
That said, I am resorting to pure JavaDoc for writing the Json examples. And it's painful.
Does anybody know of any tool out there that helps write JavaDoc... and in particular makes it easy to insert formatted JSON/etc into it?
This is an old question I posted when I was just experimenting with ways to document an API.
Eventually I switched to Apiary over MireDot, which makes this task trivial. The reason for this transition was mostly to decouple the JavaDoc from the actual API documentation, as I found coupling those two can create a very messy code-base for a sophisticated API that requires a lot of documentation.
Ideally would have built documentation using an all-encompassing API management platform like Mashery or the like, but at the time that was not an option.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 7 years ago.
Improve this question
I have a application that is deployed on tomcat container.
I'm running the jmeter load (x threads with HttpRequests).
then I'm looking on TPS, latencies, cpu, and memory (through jmx).
I'm looking for a automatic way to do all this, and may be better.
Any good references, blogs, articles, maybe some github sources is appresiated
You'd really need to be more specific about what you would like to automate, running the test, analyzing the results, monitoring your AUT or?
That said, you could try this: https://github.com/oliverlloyd/jmeter-ec2. This will automate test execution using remote hosts which can be useful to some people in some scenarios.
Ehm so are you searching for what exactly? I was using JProfiler and it was very efficient for me. I recorded measurement data from my app which i could analyze on the fly and afterwards as well. But i'm not sure if this is what you need. "Automatic stress test". Maybe you could run a bunch of Selenium tests while running JProfiler? Will you use commercial or do you prefer 'free' (sorry for the term) tools?
Have fun anyway :)
Dave
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 3 years ago.
Improve this question
I need to manipulate control flow graphs for Java code in a project. What might be a good java library to generate control flow graphs in Java. So far I have found a couple eclipse plugins (heavily dependent on eclipse APIs) and standalone tools (cannot embed in my code).
A tool to do this stuff is Soot, and this questions is a duplicate of Tool for generating control flow in Java
I'll throw another tool into the mix.
Atlas is an Eclipse plugin that enables program analysis. It has a querable graph database that includes the control flow graph (as well as data flow and other relationships).
jSonde will create sequence diagrams from your actual running code (which is arguably more useful than from source, since source analysis will not show implementation-specific functionality).
javacalltracer does something similar.
Most tools are integrated into Eclipse/similar so they have access to the AST, which makes such things pretty trivial.
It's actually not ridiculously complex to pull the information from byte code yourself (and it's an interesting exercise). Or instrument using AspectJ and create the runtime information yourself.
Edit Original answer, still valid.
JGraph is open-source, and pretty cool.
JDiagram is a Swing component, commercial product.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 6 years ago.
Improve this question
I want to generate a program dependence graph (PDG) from Java Bytecode for further programmatic analysis. Since this is old (the paper is from '87) and presumably well-known technology, I thought that appropriate tools would be readily available---however I wasn't able to find them.
In fact an extensive search turned up only a few results:
The Bandera project which was abandoned in 2006.
The Indus project which seems not to have received any effort since 2007, except for it being made Open Source in 2009.
The Moose JEE Project which seems to be pretty new as there is basically no documentation whatsoever.
And the Soot framework, which provides some classes (see JavaDoc) but seems to lack an implementation for the generation. In fact, Soot is the basis for Bandera and Indus.
So my question is the following: Is there any alive and maintained implementation out there? Does anybody have experience in either one of the aforementioned projects? What would you recommend?
Thank you already for your input, it is highly appreciated!
I suggest you check out WALA, a system that extracts SSA representations from java byte code files.
I have no experience with this, but have reviewed a number of software engineering technical papers that seemed well-thought out, and apparantly used WALA as a foundation for their research.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 4 years ago.
Improve this question
I need a static code analyzer for Java that produces an output file about the: relationships of the classes (also inheritance relationships), fields of the classes, method signatures, and method call hierarchies.
The important point is that the analysis data can be (easily) processed by a program. (I need the analysis for a kind of automatic "refactoring" tool for university.)
JastAdd is a good source level analyzer (and much more).
You might prefer to work on bytecode level though. This is simpler, faster, provides all information you requested, works without source (obviously) and with other JVM-based languages. For that, either Soot or ASM is a good choice.
UPDATED
Of course with bytecode you can't really perform source level refactoring (though you could do bytecode modification).
For completeness you may want to combine both approaches.