Elastic-job Project source code analysis 3--talking about source code analysis

Introduction

Today's content, and source analysis is irrelevant, but from the first two of the soft text, was inspired by the shallow thought (on my way to ride the Little Donkey)

In writing this article, always like to ask you a few questions, why do "source code analysis." What our motives are. Gets the knowledge point. Rise in salary.

Of course, I'm not going to discuss this today. Let's discuss why the source analysis, which determines your awareness of a set of systems, the higher the awareness of the more able to hold the system, you can easily pinch the motives of interest by the need to learn by means of interest

Sex index: ★★★★★
Drive Force Index: ★★★★★

In my definition, interest is a time when one has the most ability to read and to learn. The ability to remember the brain is most impressive when demand dictates

Sex index: ★★★★
Drive Force Index: ★★★★★

This kind of scene is generally, the work needs, carries on the technical pre-research or the use, the inquiry method should be very comprehensive, but does not know the study by

Sex INDEX: ★
Driving Force Index: ★

This is generally a learning feature, using the demo stage; see examples to increase skill understanding by

Sex INDEX: ★
Driving Force Index: ★

This level, is purely to understand a product, or technology selection. Special care about the characteristics of the product, or at the same time compare several products how source analysis

Here I explore the way I know about the program architecture

This is the most abstract part of the frame composition of the text, the word is gold, more one appears cumbersome, less one appears weak.
You may not understand it at first, only after you have a deep understanding of it, and then we will review the architecture of Elastic-job.
Program entry

This is a heavy, original aim approach, like the Javamain in Elastic-job.

In addition to Javamain, similar to what index is the stack call chain

This is what we normally call the debug mode;
Put a breakpoint in there, when the program runs here, you can see the call chain, the depth of the call chain reflects the author's thinking level, and planning control ability. Test Package

Here's the test class, we need to see.
From the standard software test, only the automatic test case coverage to 100% when the software is available in production, only one test case does not pass, or can not be sent on-line. Of course this is only theoretically, in practice, something we can skip, such as edge testing that does not involve the core business, or not involving financial-related edge testing, which are more or less past.

Take a look at my usage scenarios in the project

Let's take a look at Basetest, the base class, and all the test classes inherit it.

In more small companies, this link is not, as long as the project can be launched on the good. Alas, they do not have much manpower to do this, and I hope that after reading this paper, everyone will add the unit test.