班級(jí)人數(shù)--熱線:4008699035 手機(jī):15921673576( 微信同號(hào)) |
增加互動(dòng)環(huán)節(jié),
保障培訓(xùn)效果,堅(jiān)持小班授課,每個(gè)班級(jí)的人數(shù)限3到5人,超過(guò)限定人數(shù),安排到下一期進(jìn)行學(xué)習(xí)。 |
授課地點(diǎn)及時(shí)間 |
上課地點(diǎn):【上海】:同濟(jì)大學(xué)(滬西)/新城金郡商務(wù)樓(11號(hào)線白銀路站) 【深圳分部】:電影大廈(地鐵一號(hào)線大劇院站)/深圳大學(xué)成教院 【北京分部】:北京中山學(xué)院/福鑫大樓 【南京分部】:金港大廈(和燕路) 【武漢分部】:佳源大廈(高新二路) 【成都分部】:領(lǐng)館區(qū)1號(hào)(中和大道) 【廣州分部】:廣糧大廈 【西安分部】:協(xié)同大廈 【沈陽(yáng)分部】:沈陽(yáng)理工大學(xué)/六宅臻品 【鄭州分部】:鄭州大學(xué)/錦華大廈 【石家莊分部】:河北科技大學(xué)/瑞景大廈
開(kāi)班時(shí)間(連續(xù)班/晚班/周末班):2020年3月16日 |
課時(shí) |
◆資深工程師授課
☆注重質(zhì)量
☆邊講邊練
☆若學(xué)員成績(jī)達(dá)到合格及以上水平,將獲得免費(fèi)推薦工作的機(jī)會(huì)
★查看實(shí)驗(yàn)設(shè)備詳情,請(qǐng)點(diǎn)擊此處★ |
質(zhì)量以及保障 |
☆
1、如有部分內(nèi)容理解不透或消化不好,可免費(fèi)在以后培訓(xùn)班中重聽(tīng);
☆ 2、在課程結(jié)束之后,授課老師會(huì)留給學(xué)員手機(jī)和E-mail,免費(fèi)提供半年的課程技術(shù)支持,以便保證培訓(xùn)后的繼續(xù)消化;
☆3、合格的學(xué)員可享受免費(fèi)推薦就業(yè)機(jī)會(huì)。
☆4、合格學(xué)員免費(fèi)頒發(fā)相關(guān)工程師等資格證書(shū),提升您的職業(yè)資質(zhì)。 |
☆課程大綱☆ |
|
JUnit jumpstart
Proving it works
Starting from scratch
Understanding unit testing frameworks
Setting up JUnit
Testing with JUnit
Exploring JUnit
Exploring core JUnit
Launching tests with test runners
Composing tests with TestSuite
Collecting parameters with TestResult
Observing results with TestListener
Working with TestCase
Stepping through TestCalculator
Sampling JUnit
Introducing the controller component
Let's test it!
Testing exception-handling
Setting up a project for testing
Examining software tests
Why we need unit tests
Kinds of tests
Determining how good tests are
Test-driven development
Automating JUnit
A day in the life
Running tests from Ant
Running tests from Maven
Running tests from Eclipse
Coarse-grained testing with stubs
Introducing Stubs
Practicing on an HTTP Connection sample
Stubbing the web server's resources
Stubbing the connection
Testing in isolation with mock objects
Introducing mock objects
Mock tasting's simple example
Using mock objects as a refactoring technique
Practicing on an HTTP connection sample
Using mocks as Trojan horses
Deciding when to use mock objects
In-container testing with Cactus
The problem with unit-testing components
Testing components using mock objects
Integration unit tests
Introducing Cactus
Testing components using Cactus
How Cactus works
Unit-testing servlets and filters
Presenting the Administration application
Writing servlet tests with Cactus
Testing servlets with mock objects
Writing filter tests with Cactus
When to use Cactus, and when to use mock objects
Unit-testing JSPs and taglibs
Revisiting the Administration application
JSP unit testing
Unit-testing a JSP in isolation with Cactus
Unit-testing taglibs with Cactus
Unit-testing taglibs with mock objects
When to use mock objects, and when to use Cactus
Unit-testing database applications
Database unit testing
Testing business logic in isolation from the database
Testing persistence code in isolation from the database
Writing database integration unit tests
Running the Cactus test using Ant
Tuning for build performance
Overall database unit-testing strategy
Unit-testing EJBs
Defining a sample EJB application
Using a fa?ade strategy
Unit testing JNDI code using mock objects
Unit-testing session beans
Using mock objects to test message-driven beans
Using mock objects to test entity beans
Choosing the right mock object strategy
Using integration unit tests
Using JUnit and remote calls
Using Cactus
|