You have just bought a new Personal Computer, but before you can get any use out of your computer, and be productive with it, you will need some software. Your new computer may have come with some bundled ‘free’ software; if it did, be careful, much of the software that you thought was free, is actually only a free trial, which may expire. In this series of articles, I will tell you how to set up a powerful, productive computer, for free!
I recently decided to enhance my software’s professionalism and improve my users’ experience, by signing my software applications. My goal was to be able to sign my windows executables (.exe), Java applets and jar, (.jar) files and Mac .app bundles. By signing my code I could assure my customers of the authenticity of my software, and help ensure the integrity of the files.
Test Automation is often seen as the Holy Grail of Software Testing, and anyone who has manually executed the same test case over and over again, on various builds and releases of a software application, will attest to the usefulness of automated tests.
Entering and tracking defects, is one of the main tasks for testers. It is important that any time that a defect is found (whether it was actively being looked for or not), that it is logged. Even if you are not sure if it really is a defect, or if you think it maybe isn’t really that big of a deal; I believe it is better to log it, analyze and then if necessary close it, than it is to just ignore it. This article explains the process of software defect tracking and give recommendations on how to implement a defect tracking system.
So you have decided you want to implement a more formal approach to testing your software, but don’t really know where to begin. In this article I will outline a basic structure of the software testing process, including some tips for test case writing, and suggestions for some tools to use in testing. There is no one set process that works for all types of projects or for all teams, so I’m hoping this will get you started, and you can adapt the process to fit your own needs.
When doing a little reading about how to test software you will quickly find that there are a lot ways to test software with a lot of different terms used. In this article I will give a brief overview of the various types of testing commonly used in Software Testing, as well as provide advice on when each type of testing is appropriate.
As most Java developers have come to realize, one of the most challenging aspects of developing cross-platform Java applications, is how to deploy them, in the most native way possible, to their various target platforms e.g. Windows, Linux and Mac OS X. There are several commercial solutions available, but these cost in the range of $500 to $2000, which may be a bit steep for an independent software developer. In this article, I will provide an overview of how I approached this problem, while developing PWMinder, using a combination of open source tools; and I hope this will provide a framework for those of you facing similar issues.