From 5f5fdaf9024bfd1dc381cb0798884a9101f08328 Mon Sep 17 00:00:00 2001
From: woodyZootopia <piequalsabout314159@gmail.com>
Date: Sat, 19 Dec 2020 23:47:53 +0900
Subject: [PATCH] Set configurations of the post to pass the compile

---
 blog/content/edition-2/posts/04-testing/index.ja.md | 6 +++++-
 1 file changed, 5 insertions(+), 1 deletion(-)

diff --git a/blog/content/edition-2/posts/04-testing/index.ja.md b/blog/content/edition-2/posts/04-testing/index.ja.md
index e3112419..b72a1bc2 100644
--- a/blog/content/edition-2/posts/04-testing/index.ja.md
+++ b/blog/content/edition-2/posts/04-testing/index.ja.md
@@ -1,11 +1,15 @@
 +++
 title = "Testing"
 weight = 4
-path = "testing"
+path = "ja/testing"
 date = 2019-04-27
 
 [extra]
 chapter = "Bare Bones"
+# Please update this when updating the translation
+translation_based_on_commit = "dce5c9825bd4e7ea6c9530e999c9d58f80c585cc"
+# GitHub usernames of the people that translated this post
+translators = ["woodyZootopia"]
 +++
 
 This post explores unit and integration testing in `no_std` executables. We will use Rust's support for custom test frameworks to execute test functions inside our kernel. To report the results out of QEMU, we will use different features of QEMU and the `bootimage` tool.