<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Rie Ota on Medium]]></title>
        <description><![CDATA[Stories by Rie Ota on Medium]]></description>
        <link>https://medium.com/@rie.ota?source=rss-d0b51afd11f0------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*TNKvAZ8OnyFbrS7L</url>
            <title>Stories by Rie Ota on Medium</title>
            <link>https://medium.com/@rie.ota?source=rss-d0b51afd11f0------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 22:00:24 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@rie.ota/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[87th Monthly Technical Session]]></title>
            <link>https://medium.com/henngeblog/87th-monthly-technical-session-5504eb29123e?source=rss-d0b51afd11f0------2</link>
            <guid isPermaLink="false">https://medium.com/p/5504eb29123e</guid>
            <category><![CDATA[monthly-technical-session]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[hennge]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[pycon]]></category>
            <dc:creator><![CDATA[Rie Ota]]></dc:creator>
            <pubDate>Thu, 02 Dec 2021 02:13:17 GMT</pubDate>
            <atom:updated>2022-01-26T02:23:01.206Z</atom:updated>
            <content:encoded><![CDATA[<p>MTS is Monthly Technical Session held at HENNGE. The speaker will give a short speech about what they are interested in at the time (technical or non-technical).</p><p>The following is an introduction to the session held on October 22, 2021.</p><h3>“AWS AppSync 101 ~ A case study~” by Doi</h3><p>Doi -san introduced how their products take advantage of AWS AppSync. He said that they’re trying to use it to speed up the development process and give the front-end developers full control.</p><p>He presented a case where there was a requirement that heavily depended on the front-end, and AppSync was used to simplify the schema definition. He explained the logic behind combining APP Sync with the existing UI and backend.</p><p>They also discovered that AppSync had the potential to be used in new B2B SaaS products.</p><h3>“AWS Resource Provisioning with Ansible” by Hans</h3><p>He was inspired to make the presentation after an intern asked him, “Why does HENNGE use Terraform?”</p><p>Now we use Terraform to manage cloud resources (e.g. EC2 instances in AWS) and use version control to manage the configuration. He said we can do similar things with Ansible and explained how to do it.</p><p>He talked about how Ansible is flexible and useful when you also need to configure the remote host. But he also mentioned that Terraform is still useful the part of using ECS.</p><p>Ansible is also able to run shell script, build and push docker images, and can create a kind of CI/CD which also can be run locally.</p><p>The compilation of Ansible and Terraform will be very powerful, he summarized.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kfr4Q7VITUIUi-VUNjpVjg.png" /></figure><h3>“How to Survive Childcare Leave” by Matsuura-san</h3><p>He talked about his experience of childcare leave (November 2019 — April 2020). The reason why he uses “Survive” is because we will not be paid during our absence.</p><p>He explained the costs of prenatal and postnatal care and the systems in place to deal with them.</p><p>He also mentioned that there is a point to note about the monthly income, the “Maternity allowance/Childcare subsidy (育児休業給付金)”. That is, it takes two months from the start of the childcare leave until the actual payment starts.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JqTdzow9o9au4-XOZjXZ7Q.png" /></figure><p>He also introduced several support systems, albeit with some limitations(Day-care fee / Child Allowance System).</p><p>He concluded by saying that it is a good idea to simulate the financial situation during maternity leave and consult with HR in advance.</p><h3><strong>“Lip-Syncing Videos” by Bagus</strong></h3><p>He said that he likes to immerse himself in video games. (Yes, me too!)</p><p>He shared a short video explaining how he was immersed in the game’s music and scenarios but lost immersion when the character&#39;s mouth movements did not match the character’s speaking voice.</p><p>He introduced a tool called “Wav2Lip” to match the character’s mouth movements with the audio. It uses a pre-trained lip-sync discriminator and a visual quality discriminator.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GwfCkuTuYXBJk0LDSTxw7A.png" /></figure><p>Since it was unable to detect the faces of animations, he shared a successful example where he was able to lip-sync using a video of a real person.</p><p>Finally, he gave several examples of applications, for example, lip-syncing translations, generating missing video call segments, and talking memes, stickers, GIFs, etc</p><h3>“Deep dive into lessons becoming intrapreneur” by Sai</h3><p>First, she explained the difference between an entrepreneur and an intrapreneur. Entrepreneurs have more freedom but are riskier. Intrapreneurs have internal resources and are less risky. But both need to take on the role of leader.</p><p>Next, she outlined a new business to create. First, come up with an idea and validate the pain. Then clear the product’s goals. And the other important thing is team forming.</p><p>After those, she said, is user research, and listed the things that need to be done for that.</p><p>She said that the next step is to plan for MVP. Provide minimal functionality to trial testers, get feedback, small successes, and discussion.</p><p>The last step is to recruit β trial users and monitor them and get the product market.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eJ81W94Sy2zcx5sDWoktCQ.png" /></figure><p>Finally, she shared some summaries about the Wakaba project: it is a project to launch a new project.</p><h3>“PyCon JP 2021” by Jonas</h3><p>The last speaker was Jonas, who gave his report on PyCon JP 2021.</p><p>He gave introductions to some of the lectures he was excited about.<br>One was the second day’s “match/casein Python3.10” by Brandt Bucher. He said that it’s really interesting if you are interested in how match cases work and how features are learned in python.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*a0vx6HcMOHxFmCB2BKkfXA.png" /></figure><p>He then said that he had things to do and couldn’t introduce any other great talks. So he explained his role at Pycon. He said that since everything was done in Japanese, he did his best to translate the opening, closing, etc. into English.</p><p>Usually, PyCon is held in a large venue, but this time it was held in a hybrid format: day one was on-site and online, and day two was fully online.</p><p>For the on-site part, due to COVID-19, there were some restrictions such as mask and social distance. And for the online part, there was a slight change this year and they used Discord. It worked well, he said. He also said that what was interesting was the nesting of Zoom.</p><p>He concluded by saying that he was happy to be a part of PyCon as a member of HENNGE!</p><p>Looks like there was a beer bash as usual after all the sessions!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FjU55pbSgyxI5gijNJoNfQ.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5504eb29123e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/henngeblog/87th-monthly-technical-session-5504eb29123e">87th Monthly Technical Session</a> was originally published in <a href="https://medium.com/henngeblog">henngeblog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Thoughts After Participating in JaSST]]></title>
            <link>https://medium.com/henngeblog/thoughts-after-participating-in-jasst-fa67a83dc32d?source=rss-d0b51afd11f0------2</link>
            <guid isPermaLink="false">https://medium.com/p/fa67a83dc32d</guid>
            <category><![CDATA[hennge]]></category>
            <category><![CDATA[qa]]></category>
            <category><![CDATA[software-test-automation]]></category>
            <category><![CDATA[jasst]]></category>
            <category><![CDATA[software-engineering]]></category>
            <dc:creator><![CDATA[Rie Ota]]></dc:creator>
            <pubDate>Mon, 12 Jul 2021 05:32:18 GMT</pubDate>
            <atom:updated>2021-07-12T05:32:18.089Z</atom:updated>
            <content:encoded><![CDATA[<p><a href="http://www.jasst.jp/">The Japan Symposium on Software Testing </a>(JaSST) is a symposium on software testing held in Japan.</p><p>Hi, I am Rie Ota! I work as a test engineer at HENNGE K.K. and I have been interested in this symposium for a long time. In the past, it was difficult for me to participate in it for personal reasons, but now since it is held online due to COVID-19, I was finally able to attend.</p><p>In this article, I would like to summarize the two most memorable lectures during the event.</p><p>— —</p><p><strong>From JaSST’20 Niigata, I would like to introduce the keynote speech by Takuto Wada(和田卓人 / タワーズ・クエスト).</strong></p><p>Wada talked about “組織にテストを書く文化を根付かせる戦略と戦術 / Strategies and tactics to instill a culture of test writing in your organization.</p><p>He mentioned:</p><blockquote>The sooner the lead time (development speed) and deployment frequency, the better. The shorter the lead time, the more frequent the verification demonstration process. And, the most important thing is how few defects there are and how quickly it takes to fix them after they occur (MTTR = Mean Time To Repair). The purpose of test automation is to achieve a short MTTR. In addition, he also said that there is no trade-off between development speed and quality.</blockquote><p>The words that stuck in my mind were, “It’s not that I don’t have time to write tests, it’s that I don’t have time because I don’t write tests.” It certainly takes time to write test code, but in the long run, automating tests that used to be done manually for each release will create efficiency.</p><p>Incidentally, he said that after running tests four times, the cost of manual and automated testing will reverse.</p><p>I was convinced that test automation is now a must to improve the efficiency of development and release.</p><p>— —</p><p><strong>From Jasst’21 Tokyo, I’d like to introduce “ AIの力でリリースサイクルを加速する / DevOps Testing: Accelerating the Release Cycle with the Power of AI”.</strong></p><p>When writing tests, it is quite common to find that the existing tests no longer work due to UI changes. Furthermore, I nodded my head greatly when he said that he sometimes puts a “mysterious 1500ms wait” into the test to wait for the object to appear.</p><p>Automation of testing by AI was introduced as a means to solve these various problems. I was largely ignorant of the relationship between testing and AI. Autify, which he introduced in this talk, had the following three points:</p><ol><li>Automatically script operations</li><li>AI maintains the code</li><li>Plenty of browsers and actual devices in the cloud</li></ol><p>Personally, I found 2 to be particularly novel. I found it very interesting because test code is not finished after it is created, but maintenance is a big part of it.</p><p>“Need to write test code -&gt; but don’t have time to write it due to manpower issues” — It was very interesting to hear that test automation by AI could solve this dilemma.</p><p>— —</p><figure><img alt="Woman with white long sleeve shirt with back turned and facing a monitor screen" src="https://cdn-images-1.medium.com/max/1024/1*PBiXKNzU5HRjGdwgGS8nrA.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@sigmund">Sigmund</a> on <a href="https://unsplash.com/">Unsplash</a>.</figcaption></figure><p><strong>My final thoughts</strong></p><p>What was emphasized in both talks was the importance of a fast release cycle in today’s world. I came out of the talk, with the reinforced belief that not only is testing essential for this cycle, it is no longer a separate “test” but an integral part of the development phase.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fa67a83dc32d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/henngeblog/thoughts-after-participating-in-jasst-fa67a83dc32d">Thoughts After Participating in JaSST</a> was originally published in <a href="https://medium.com/henngeblog">henngeblog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Test plan of Azure DevOps]]></title>
            <link>https://medium.com/henngeblog/test-plan-of-azure-devops-c6ba114623b9?source=rss-d0b51afd11f0------2</link>
            <guid isPermaLink="false">https://medium.com/p/c6ba114623b9</guid>
            <category><![CDATA[hdetech]]></category>
            <category><![CDATA[hdeknow]]></category>
            <category><![CDATA[testing]]></category>
            <dc:creator><![CDATA[Rie Ota]]></dc:creator>
            <pubDate>Mon, 12 Nov 2018 04:49:13 GMT</pubDate>
            <atom:updated>2018-11-12T04:49:13.836Z</atom:updated>
            <content:encoded><![CDATA[<p>We have been using Testlink as main test management tools to test our products. We are planning to change it to Azure DevOps. I’ll introduce how to use Azure DevOps as manual test management tool.</p><p><a href="https://docs.microsoft.com/en-us/azure/devops/test/?view=vsts">Exploratory and Manual Testing - TestTools</a></p><h4>Preparation</h4><ul><li><strong>Required</strong> : Visual studio Enterprise (It maybe work only with “Azure Test Plans”.)</li><li><strong>Convenient tool</strong> : <a href="https://marketplace.visualstudio.com/items?itemName=ms.vss-exploratorytesting-web#supportedbrowsers">Test &amp; Feedback</a> (add-on of Chrome or FireFox)</li></ul><h4>Create a project</h4><ol><li>Login <a href="https://dev.azure.com/">dev.azure.com</a> as azure account.</li><li>Click “Start Free”.</li><li>Your resource is shown, so create a project.</li></ol><h4>New Test Plan</h4><p>Fill all items.</p><h4>Create test cases</h4><ol><li>Add test suites and tests</li><li>You can use following features when creates test case<br>* Add tag : It is can be queried by this tag.<br>* Add Priority : 1(High important) — 4(Low important)<br>* Add Attachments<br>* Add link (relate to another test case, bug, build etc…)</li></ol><p><strong>Query-Based suite / Requirement-Based suite</strong><br>You can put existing test cases into one suite by above 2 ways.</p><h4>Run test</h4><ol><li>Select the test suite and click “show tests from child suites”</li><li>Select “Assign testers to run all tests” from menu of the test suite.</li><li>Assign tester. Multiple testers can be set.</li><li>Click Run test from menu of the test suite.(If you select “Run with option”, you can associate the test to build.)</li><li>Test runner opens. Let’s test it fun!</li><li>Save and close the test runner when you finish the test. It can also be interrupted and restarted. (Pause test &gt; Resume test)</li></ol><h4>Confirm results</h4><p>You can check the latest result from test plan &gt; charts. Add charts as you like.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*i0wyrAFFDqoTrMr_NEtY-g.png" /></figure><p>You can also check past output from “Runs”.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*k_rJLyBa8NarBX7pQuDpTA.png" /></figure><p>You can also confirm the past runs.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lwjYGpy1HkHeTSq6AC-J_A.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*k_rJLyBa8NarBX7pQuDpTA.png" /><figcaption>Outcome is automatically graphed.</figcaption></figure><h4>My thoughts</h4><p>I think it is good the outcomes can be graphed more easily than test links. And I think DevOps is convenient to be able to relate to another service. (e.g. Slack, GitHub)</p><p>However, retention of results seems to be unimportant in DevOps. Past results retain only 1 year in default. (It can be changed to &quot;Never delete&quot;.) Be careful when you want to hold and check past test results for a long time.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c6ba114623b9" width="1" height="1" alt=""><hr><p><a href="https://medium.com/henngeblog/test-plan-of-azure-devops-c6ba114623b9">Test plan of Azure DevOps</a> was originally published in <a href="https://medium.com/henngeblog">henngeblog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>