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
In order to improve my open source project, I need testers. I have created my project independently, so up to now I have been the sole coder and tester. I have tested the thing to death, but as we all know it is dangerous as a developer to test your own code. I'm looking for ideas on how I can get some other eyes to exercise it.
To clarify, I have released it on sourceforge and posted it on freshmeat, dzone, reddit, etc.
Are you looking for "testers" or "users"? There's a world of difference.
A tester uses his time and energy to find your bugs. How many people are willing to do that? At a rough guess, I'd say zero.
A user uses your software to solve his problems. He reports bugs to you because he thinks that you might fix them for him. So you've got to find people with a problem, and convince them that your software will fix it.
One thing you'll need is lots of documentation. A 1-minute screencast, in-depth API, and everything in between. You need to persuade someone that, "If I use tox, I will totally rock!"
That's your tester.
Release an early version, announce it on freshmeat, and wait for the world to beat a path to your door?
Go to where the testers are. Find sites where testers go. http://www.stickyminds.com, local QA groups (like mine) http://redearthqa.blogspot.com/ or local recruiters that have QA people looking for experience.
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 8 years ago.
Improve this question
I've already tried EazFuscator and Dotfuscator but are bad! I was able to easily read the source and pay it, and frankly I'm tired of the people that I copy the software.
I ask you which obfuscator use, at least to protect all the software by beginners.
From the great Joel Coehoorn ... you can read more here
How can I protect my .NET assemblies from decompilation?
One thing to keep in mind is that you want to do this in a way that makes business sense. To do that, you need to define your goals. So, exactly what are your goals?
Preventing piracy? That goal is not achievable. Even native code can be decompiled or cracked; the multitude of warez available online (even products like Windows and Photoshop) is proof of that.
If you can't prevent piracy, then how about merely reducing it? This, too, is misguided. It only takes one person cracking your code for it to be available to everyone. You have to be lucky every time. The pirates only have to be lucky once.
On another note, I would recommend SmartAssembly by RedGate. Ive used this before and its great compared to others. Please note that like any obfuscator, you cannot stop someone cracking your software if they are determined to do so.
You can get more information here...
http://www.red-gate.com/products/dotnet-development/smartassembly/
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
Background
There is a hardware project going on. A hardware accelerator has been being developed by a team of students but there is no general documentation.
There are READMEs here and there, some docxs and in-code (Verilog, C and Lua) comments, but nothing else. The code is written with Vim, versioned with Git and Markdown is our friend, even if we are not on Github (yet).
Since this “thing” is growing, I feel the necessity of writing down something (user manual? developer notes?) but I don't know where to start.
Question
When someone feels the urge of documenting his project, where does it start?
More specifically, what are the generally accepted criteria to do it and what are the best tools?
My hypothetical answer
We quite clearly need both a developer and user manual. One with details of the algorithmic solutions, the other... like for monkeys.
About the tools, I believe that something like a Github Wiki would work fine, but (1) we are not on Github and (2) wouldn't be LaTeX a better way of writing stuff in order to publicise it, eventually. I know we can get our Markdown rendered in a printable way with http://www.cocowrite.com/, but is it the most efficient solution? LaTeX would be a nuisance for collaborative editing and online HTML publishing.
A partial answer can be found here: “What tools are used to write documentation?”.
Second part of the answer can be found here: “What amount of documentation is needed for a non-trivial one-man software project”
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 looking into ways of documenting my code in a JavaDocs kinda way.
Any ideas?
I use UFT 11.52
So far I have seen NaturalDocs + Perl.
Any other ideas?
Thanks in advance.
At least one solution looks
practical,
mature,
is delivered in source code form (consists of one huge (but very professionally written) VBS script that generates the documentation fragments),
and is absolutely free:
VBSdoc, "A VBScript API Documentation Generator"
See http://www.planetcobalt.net/sdb/vbsdoc.shtml.
The author appears to be very competent, given his high SO rep (see https://stackoverflow.com/users/1630171/ansgar-wiechers), and the general quality of his website's content.
Of course, this one is built for standalone VBS scripts, not QTP/UFT scripts. But this should be no obstacle, given the source code is available.
I'd love to hear from you about experiences with this one. Feel free to edit them into this answer, be it accepted or not.
I had success using Natural Docs several years ago. It's one of the few things I blogged about: automated code documentation for QTP
There is a product called Test Design Studio, an IDE alternative for QuickTest and UFT. One of the key features it provides is the ability to generate detailed documentation. It uses XML-style comments to mark up your code, and those comments drive documentation. The same comments also drive detailed IntelliSense for editing your code.
It does exactly what you're talking about.
Test Design Studio
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 8 years ago.
Improve this question
What are the best free uml drawing tools?
All the ones I have found require membership payments and only offer limited functionality based to public users on a trial basis...rubbish!
For my (very simple) needs I used ArgoUML. I'm not an expert about, but I found it enough easy to use. It's open source and, on the web page, you can find a good user guide.
Have a look at StarUML ( http://staruml.sourceforge.net/en/ )
It's free, open source, and incredibly fully featured.
For a full list, check out the ones marked as Open Source here: http://en.wikipedia.org/wiki/List_of_Unified_Modeling_Language_tools
But I'd really recommend StarUML!
For my first two software engineering courses, I used the stand alone version of UMLet, but it is just for diagrams. It exports to standard graphics, or pdf. They also have an eclipse plugin version, but I never used it.
For a no frill drawing tool, I find Google Docs (drawings) pretty good. Note that printing works better under Mozilla than Chrome, strangely enough. In Chrome, I cannot get dashed lines to print.
Try UMLet. Supports Eclipse IDE.
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
For years I've missed a wiki so everyone could describe the new tools programmed, the servers where they are running, svn information, the internal rules of programming, how-tos, code samples, etc.
The wiki might be used for the dozen of programmers in the company and the externals.
I've been using a pmwiki (easy install) and now I want a better approach.
What wiki do you use? What plug-ins? Do you think there are better systems than wiki for this?
We're using TWiki for internal dev stuff, and I don't particularly like it. I'd rather use MediaWiki, as that's what Wikipedia uses, and more people are familiar with it.
We've been using a TWiki for several years, but it is being retired and replaced by TRAC.
Wen we started using TWiki I had great hopes, but the requirement for a special markup (like here on SO) never caught on with the management and admin types.
TRAC, as a wiki, is no better in that regard, but it suported by our IT guys and brings more tools for the development process.