Eclipse Plug-in Continuous Testing introduction

Introduced

Now more than ever, it developers are concerned about the importance of testing, and the lack of well tested code is more likely to be problematic. In extreme programming, test-driven development has proven to be an effective way to improve software quality. In the test-driven development approach, the software engineer writes the test code first before writing the functional code, which guarantees the correctness of the program's code from the very beginning, and is able to automate regression testing every time the program evolves.

Unit tests are the types of tests that are most closely related to the developer. It is usually written and executed by developers. Because unit tests often occur shortly after an error has occurred, the cost of finding errors through unit tests and then correcting them is usually relatively small. Unit testing is so important that some extreme programming enthusiasts advocate that any untested code should be automatically deleted. JUnit is the de facto standard of unit testing for Java developers. Despite the more sophisticated testing tools such as testng and JTiger, JUnit is still the head of the test tool.

One evidence of JUnit's dominance of the market is that there are currently many extensions and Plug-ins developed for JUnit. What we're going to talk about today is a eclipse plug-in continuous testing with JUnit. It can perform tests using the machine's idle calculation cycle and display it as an error in the problem view and editor's markup area.

Performing tests during the idle time of writing code consumes some CPU time and other resources. But we don't need to be preoccupied with the benefits of continuous testing. Remember the first time you used incremental compilation of Eclipse?

I remember being dismissive of this feature, and now I have relied entirely on incremental compilation to correct my occasional grammatical errors. For software developers, any tool that can effectively shorten the write-compile-test-modify cycle is of great significance. In this regard, I believe that continuous testing is of great significance for software developers. On the http://www.eclipse-plugins.info/we can see that continuous testing is well received by many users

Install continuous testing

The method of installing continuous testing in Eclipse is very simple, similar to installing other plugin methods. First we start Eclipse3.1, click menu Items Help->software update->find and Install. In the Pop-up wizard dialog, we select "Search new Features to Install" and click "New Remote Site" In the pop-up dialog box, as shown in Figure 1. Enter Http://beust.com/eclipse in the URL and click "OK". As shown in Figure 1, by clicking Finish, Eclipse will help us add a site for update. The reader who is familiar with eclipse must not be unfamiliar with the process.

Figure 1 New update Site