- Scala Test-Driven Development
- Gaurav Sood
- 190字
- 2021-07-08 10:44:56
Conventions
In this book, you will find a number of text styles that distinguish between different kinds of information. Here are some examples of these styles and an explanation of their meaning.
Code words in text, database table names, folder names, filenames, file extensions, pathnames, dummy URLs, user input, and Twitter handles are shown as follows: "The cancel()
method forces the test to be interrupted."
A block of code is set as follows:
test("one plus one with result") { val two = 2 assertResult(two) { 1 + 1 } }
Any command-line input or output is written as follows:
$ sbt test [info] Loading project definition from /helloworld/project [info] Set current project to Chap1 (in build file:/Packt/ helloworld /) [info] Compiling 1 Scala source to /Packt/ helloworld /target/scala/classes...
New terms and important words are shown in bold. Words that you see on the screen, for example, in menus or dialog boxes, appear in the text like this: "Tail-call optimization is where we can escape allocating a new stack frame for a function."
Note
Warnings or important notes appear in a box like this.
Tip
Tips and tricks appear like this.
- 極簡算法史:從數學到機器的故事
- Testing with JUnit
- 小創(chuàng)客玩轉圖形化編程
- Java Web開發(fā)之道
- 從學徒到高手:汽車電路識圖、故障檢測與維修技能全圖解
- 大學計算機基礎實驗指導
- Domain-Driven Design in PHP
- 大話Java:程序設計從入門到精通
- Spring技術內幕:深入解析Spring架構與設計原理(第2版)
- Learning Nessus for Penetration Testing
- Android系統(tǒng)下Java編程詳解
- WebStorm Essentials
- Deep Learning for Natural Language Processing
- Spring Data JPA從入門到精通
- Web前端測試與集成:Jasmine/Selenium/Protractor/Jenkins的最佳實踐