瀏覽代碼

More page bundles

master
Chris Smith 4 年之前
父節點
當前提交
c27aa11e21
簽署人: Chris Smith <chris@chameth.com> GPG 金鑰 ID: 3A2D4BBDC4A3C9A9

+ 2
- 0
nginx.conf 查看文件

@@ -62,6 +62,8 @@ http {
62 62
         /res/images/yubikey/wisdom_of_the_ancients.png  /2016/08/11/offline-gnupg-master-yubikey-subkeys/wisdom_of_the_ancients.png;
63 63
         /res/images/ssh/openssh.png                     /2016/10/18/shoring-up-sshd/openssh.png;
64 64
         /res/images/ssh/ssh-audit-github.png            /2016/10/18/shoring-up-sshd/ssh-audit-github.png;
65
+        /res/images/android-tests/spoon.png             /2017/05/16/android-tests-espresso-spoon/spoon.png;
66
+        /res/images/android-tests/spoon-espresso.png    /2017/05/16/android-tests-espresso-spoon/spoon-espresso.png;
65 67
     }
66 68
 
67 69
     server {

+ 1
- 1
site/assets/style/modules/_articles.sass 查看文件

@@ -19,7 +19,7 @@ article
19 19
   img
20 20
     max-width: 100%
21 21
 
22
-  img + p
22
+  img + p, img + h3
23 23
     margin-top: 1.5em
24 24
 
25 25
   p a, figcaption a

site/content/post/2017-05-16-android-tests-espresso-spoon.md → site/content/post/2017-05-16-android-tests-espresso-spoon/index.md 查看文件

@@ -1,10 +1,16 @@
1 1
 ---
2 2
 date: 2017-05-16
3 3
 title: Android testing with Espresso and Spoon
4
-url: /2017/05/16/android-espresso-spoon/
5
-image: /res/images/android-tests/spoon-espresso.png
6 4
 description: Automatically running Android UI tests, reducing flakeyness, and getting useful debugging information back on failure.
7 5
 area: Android
6
+url: /2017/05/16/android-espresso-spoon/
7
+
8
+resources:
9
+  - src: spoon-espresso.png
10
+    name: Spoon output details, showing a screenshot captured of the failure
11
+    default: true
12
+  - src: spoon.png
13
+    name: Spoon output summary, showing results of 171 tests run on 3 devices
8 14
 ---
9 15
 
10 16
 I've been spending some time recently setting up automated testing for our
@@ -49,7 +55,7 @@ Spoon produces HTML reports, showing the status of each test run on each device.
49 55
 We have the report output folder collected as a build artefact, so the reports
50 56
 can be seen right from the build server:
51 57
 
52
-<img src="/res/images/android-tests/spoon.png" alt="Spoon output summary, showing results of 171 tests run on 3 devices">
58
+{{< img "Spoon output summary, showing results of 171 tests run on 3 devices" >}}
53 59
 
54 60
 ### Flake-free UI testing with Espresso
55 61
 
@@ -160,7 +166,7 @@ Espresso's original handler so that it can output its debugging information
160 166
 and fail the test. The Spoon runner automatically picks up the screenshot and
161 167
 adds it to the report:
162 168
 
163
-<img src="/res/images/android-tests/spoon-espresso.png" alt="Spoon output details, showing a screenshot captured of the failure">
169
+{{< img "Spoon output details, showing a screenshot captured of the failure" >}}
164 170
 
165 171
 Having the screenshot, error message and logs all presented in a clean UI
166 172
 makes debugging failures much, much easier than searching through a huge build

site/static/res/images/android-tests/spoon-espresso.png → site/content/post/2017-05-16-android-tests-espresso-spoon/spoon-espresso.png 查看文件


site/static/res/images/android-tests/spoon.png → site/content/post/2017-05-16-android-tests-espresso-spoon/spoon.png 查看文件


site/content/post/2019-04-01-understanding-docker-volume-mounts.md → site/content/post/2019-04-01-understanding-docker-volume-mounts/index.md 查看文件

@@ -1,16 +1,16 @@
1 1
 ---
2 2
 date: 2019-04-01
3 3
 title: Understanding Docker volume mounts
4
-url: /2019/04/01/understanding-docker-volume-mounts/
5
-image: /res/images/docker/logo.png
6 4
 description: It's basically magic.
7 5
 area: Docker
6
+url: /2019/04/01/understanding-docker-volume-mounts/
7
+
8
+resources:
9
+  - src: logo.png
10
+    name: The Docker project logo
8 11
 ---
9 12
 
10
-<figure class="left">
11
-  <img src="/res/images/docker/logo.png" alt="Docker logo">
12
-  <figcaption>The Docker project logo</figcaption>
13
-</figure>
13
+{{< figure "left" "The Docker project logo" >}}
14 14
 
15 15
 One thing that always confuses me with Docker is how exactly mounting
16 16
 volumes behaves. At a basic level it's fairly straight forward: you

二進制
site/content/post/2019-04-01-understanding-docker-volume-mounts/logo.png 查看文件


Loading…
取消
儲存