- Mastering Software Testing with JUnit 5
- Boni García
- 153字
- 2021-07-02 15:34:21
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, path names, dummy URLs, user input, and Twitter handles are shown as follows: “The @AfterAll and @BeforeAll methods are executed only once”.
A block of code is set as follows:
package io.github.bonigarcia;
import static org.junit.jupiter.api.Assertions.assertTrue;
import org.junit.jupiter.api.Test;
class StandardTest {
@Test
void verySimpleTest () {
assertTrue(true);
}
}
Any command-line input or output is written as follows:
mvn test
New terms and important words are shown in bold like this: “Compatibility is the degree to which a product, system or component can exchange information with other products”.
Warnings or important notes appear in a box like this.
Tips and tricks appear like this.
推薦閱讀
- Learn TypeScript 3 by Building Web Applications
- Unreal Engine Physics Essentials
- Python數據分析入門與實戰
- Android Studio Essentials
- PostgreSQL技術內幕:事務處理深度探索
- Learn Swift by Building Applications
- Mastering Unity Shaders and Effects
- C語言實驗指導及習題解析
- Jupyter數據科學實戰
- 程序是怎樣跑起來的(第3版)
- Android傳感器開發與智能設備案例實戰
- jQuery從入門到精通(微課精編版)
- C語言從入門到精通
- Learning Cocos2d-JS Game Development
- Android嵌入式系統程序開發(基于Cortex-A8)