<?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 Efekan Egeli on Medium]]></title>
        <description><![CDATA[Stories by Efekan Egeli on Medium]]></description>
        <link>https://medium.com/@eegeli?source=rss-aec3abf49986------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*6N7HMbTPI8Q2JrYIG71nUA.jpeg</url>
            <title>Stories by Efekan Egeli on Medium</title>
            <link>https://medium.com/@eegeli?source=rss-aec3abf49986------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 23:14:23 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@eegeli/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[Building an iOS Distribution Pipeline — Creating a Freestyle Jenkins Project (Part 2)]]></title>
            <link>https://medium.com/trendyol-tech/building-an-ios-distribution-pipeline-creating-a-freestyle-jenkins-project-part-2-688497f1a712?source=rss-aec3abf49986------2</link>
            <guid isPermaLink="false">https://medium.com/p/688497f1a712</guid>
            <category><![CDATA[jenkins]]></category>
            <category><![CDATA[automation]]></category>
            <category><![CDATA[continuous-delivery]]></category>
            <category><![CDATA[ios]]></category>
            <category><![CDATA[continuous-integration]]></category>
            <dc:creator><![CDATA[Efekan Egeli]]></dc:creator>
            <pubDate>Fri, 02 Aug 2019 06:45:54 GMT</pubDate>
            <atom:updated>2019-08-09T12:00:02.158Z</atom:updated>
            <content:encoded><![CDATA[<h3>Building an iOS Distribution Pipeline — Creating a Freestyle Jenkins Project (Part 2)</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*XVb9F3fVzY-s3MjS" /><figcaption>Photo by <a href="https://unsplash.com/@samthewam24?utm_source=medium&amp;utm_medium=referral">Samuel Sianipar</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>In the <a href="https://medium.com/trendyol-tech/building-an-ios-distribution-pipeline-local-poc-with-command-line-tools-part-1-d9f443c7dbb5">first part</a> of this guide, we’ve built &amp; uploaded our iOS project locally via command line with the tools that Apple provided. But we don’t want to run these on our local machine and we don’t want to type in commands to terminal each time we want to upload an iOS app to the store. We need to automate every step and uploading an app should be as easy as clicking a button.</p><p>Wel’ll try to achieve that with a jenkins freestyle project. Let’s begin with creating a new freestyle project on jenkins.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fG9woC51Txy_mYsTrfUrLQ.png" /></figure><p>Unless we specify another location, the jenkins project we created will put everything — the repo it pulled, the file it created etc. — under “freestyle-project-demo” folder.</p><p>In the first part, we built the project with specified parameters like our scheme name. We have multiple schemes and want to select one of them when we want to run the jenkins job. So we need to parameterize the job first.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QP5WV0dL7NuxCob7k8hXOQ.png" /></figure><p>We also needed a “branch” parameter as well because we should be able to build &amp; upload from any branch at any given time with the scheme we want. To be able to do that, we added another parameter called “BRANCH” and we needed the jenkins job to connect to our bitbucket server and get the available branch names. So we added a groovy script to the active choices “BRANCH” parameter to achieve that and used a bit of regex to get the branch names with the format we use.</p><pre>def getTags = (&quot;git ls-remote -h -t <a href="https://testjenkins:Passw0rd12*@stash.trendyol.com/scm/tm/ios.git">https://your-user-name:your-password@your-git-path.git</a>&quot;).execute()<br>def branchList = getTags.text.readLines().collect { <br>  it.split()[1].replaceAll(&#39;refs/heads/&#39;, &#39;&#39;).replaceAll(&#39;refs/tags/&#39;, &#39;&#39;).replaceAll(&quot;\\^\\{\\}&quot;, &#39;&#39;)<br>}<br>return branchList</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*R484yGJRUgRctKAFhg_m-g.png" /></figure><p>After you added these two parameters, your jenkins job should look like this when you are at “Build with Parameters” section.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/774/1*KLFSFVH-JTz84sePxYIE6g.png" /></figure><p>Now we’ll add a Source Code Management step and this will clone the branch we wanted each time we press the “Build” button in the “Build with Parameters” section.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jZjyMHm5GBjxOGLj5zLjxQ.png" /></figure><p>As the last step of creating a freestyle jenkins project, we will take all the shell code from <a href="https://medium.com/trendyol-tech/building-an-ios-distribution-pipeline-local-poc-with-command-line-tools-part-1-d9f443c7dbb5">part 1</a> and move it to “execute shell” action of the jenkins “build step”.</p><p>To upload an app from a jenkins server, there are very important 2 steps you have to add.</p><ol><li>Store your app-specific password and username to a file in your jenkins server and add it to your shell script as a source. You can create app specific passwords at <a href="https://appleid.apple.com/">https://appleid.apple.com</a>.</li></ol><pre>#get appstoreconnect username and password from config file<br>. /Users/jenkins/Documents/workspace/ios-distribution-config/credentials.config</pre><p>This config file stores 2 variables which are “username” and “password”. We’ll use these in the upload step.</p><p>2. Unlock keychain on the machine to give the Jenkins access to your keychain.</p><pre>#jenkins needs to access keychain over SSH<br>security unlock-keychain -p your-machine-password ~/Library/Keychains/login.keychain</pre><p>We don’t want to reach the altool with full path, so let’s add its path globally.</p><pre>#access altool globally<br>export PATH=$PATH:/Applications/Xcode.app/Contents/Applications/Application\ Loader.app/Contents/Frameworks/ITunesSoftwareService.framework/Support/</pre><p>Finally, add the xcodebuild and altool commands to the end of your shell script.</p><pre>#archive project<br>xcodebuild -workspace Trendyol.xcworkspace -scheme ${BUILD_SCHEME} -sdk iphoneos -configuration ${BUILD_CONFIGURATION} archive -archivePath /Users/jenkins/Documents/workspace/ios-distribution-config/${BUILD_SCHEME}.xcarchive | /usr/local/bin/xcpretty</pre><pre>#export IPA<br>xcodebuild -exportArchive -archivePath /Users/jenkins/Documents/workspace/ios-distribution-config/${BUILD_SCHEME}.xcarchive -exportOptionsPlist exportOptions.plist -exportPath /Users/jenkins/Documents/workspace/ios-distribution-config -allowProvisioningUpdates | /usr/local/bin/xcpretty</pre><pre>#upload IPA<br>altool --upload-app -f /Users/jenkins/Documents/workspace/ios-distribution-config/${BUILD_SCHEME}.ipa -u $username -p $password</pre><p>That’s all. Now we can upload an app to the app store with the branch and scheme we wanted to upload with just a click of a button.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/338/1*t3fH1ZRkVHkUaRC6BkN34Q.png" /></figure><p><strong>Part 3</strong> of this guide will describe setting a <strong>Jenkins pipeline project</strong> + version management for your app.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=688497f1a712" width="1" height="1" alt=""><hr><p><a href="https://medium.com/trendyol-tech/building-an-ios-distribution-pipeline-creating-a-freestyle-jenkins-project-part-2-688497f1a712">Building an iOS Distribution Pipeline — Creating a Freestyle Jenkins Project (Part 2)</a> was originally published in <a href="https://medium.com/trendyol-tech">Trendyol Tech</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Building an iOS Distribution Pipeline — Local POC with Command Line Tools(Part 1)]]></title>
            <link>https://medium.com/trendyol-tech/building-an-ios-distribution-pipeline-local-poc-with-command-line-tools-part-1-d9f443c7dbb5?source=rss-aec3abf49986------2</link>
            <guid isPermaLink="false">https://medium.com/p/d9f443c7dbb5</guid>
            <category><![CDATA[ios]]></category>
            <category><![CDATA[distribution]]></category>
            <category><![CDATA[continuous-delivery]]></category>
            <category><![CDATA[continuous-integration]]></category>
            <category><![CDATA[jenkins]]></category>
            <dc:creator><![CDATA[Efekan Egeli]]></dc:creator>
            <pubDate>Thu, 18 Jul 2019 08:21:03 GMT</pubDate>
            <atom:updated>2019-08-02T07:05:47.917Z</atom:updated>
            <content:encoded><![CDATA[<h3>Building an iOS Distribution Pipeline — Local POC with Command Line Tools (Part 1)</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*l8hy0vvwr1CqgB6z" /><figcaption>Photo by <a href="https://unsplash.com/@realaxer?utm_source=medium&amp;utm_medium=referral">tian kuan</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>There are a lot of ways of automating your iOS distributions nowadays. CircleCI, TravisCI, Fastlane just to name a few…</p><p>Since we’ve always been a bit of a control freak; we wanted to use 3rd party tools as little as possible. Thus, we’ve only used <strong>Jenkins</strong> as our automation server.</p><p>This will be a step by step guide with parts describing how to build a similar pipeline with the command line tools that Apple provided.</p><p>We always take an iterative approach when we are building something ground up. So the first thing we needed was to build an app for different environments. We already had different schemes for different environments so I’m not going to get into that. I’m not going to get into how to set up a Jenkins server as well because you can already find a lot of information on that.</p><p>Let’s begin with building our app with command line tools on our local machine. The tool Apple provides for this kind of purpose is <strong>xcodebuild</strong>. xcodebuild is a command line tool which lets you build your app with different schemes, build configurations, targets. You can find the full list of it’s capabilities with help command.</p><pre>xcodebuild -help</pre><p>So let’s pick a scheme for our POC and build it with xcodebuild command.</p><pre>xcodebuild build -workspace your_project_workspace -scheme your_project_scheme_name</pre><p>When it builds the project, the console looks like this:</p><pre>CompileC /Users/jenkins/Library/Developer/Xcode/DerivedData/Trendyol-gtkkcwzykuhaycgnaraksmvhkxbr/Build/Intermediates.noindex/Pods.build/Prod-iphoneos/FBSDKCoreKit.build/Objects-normal/arm64/FBSDKAppEvents.o /Users/jenkins/Documents/workspace/ios-distribution/Pods/FBSDKCoreKit/FBSDKCoreKit/FBSDKCoreKit/FBSDKAppEvents.m normal arm64 objective-c com.apple.compilers.llvm.clang.1_0.compiler (in target: FBSDKCoreKit)<br>    cd /Users/jenkins/Documents/workspace/ios-distribution/Pods<br>    export LANG=en_US.US-ASCII<br>    /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang -x objective-c -arch arm64 -fmessage-length=0...</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SxEL1fod8LmOaw60AIxDnQ.png" /></figure><p>Seriously? What is this? It should be more readable.</p><h4>xcpretty to the rescue</h4><p>There is an open source formatter called <a href="https://github.com/xcpretty/xcpretty">xcpretty</a> which formats the xcodebuild outputs. After you install xcpretty, the usage is pretty simple.</p><pre>xcodebuild build -workspace Trendyol.xcworkspace -scheme TY-Prod | xcpretty</pre><p>Here is the result:</p><pre>...<br>▸ Compiling pop-dummy.m<br>▸ Compiling TransformationMatrix.cpp<br>▸ Compiling POPVector.mm<br>▸ Compiling POPSpringAnimation.mm<br>▸ Compiling POPPropertyAnimation.mm<br>▸ Compiling POPMath.mm<br>...</pre><p>The final result of the build was successful but let’s be honest; we need more than just a build. We need to archive &amp; export IPA &amp; upload our app to the store. xcodebuild provides both archive &amp; export options.</p><h4>Next step: Archive</h4><pre>xcodebuild -workspace Trendyol.xcworkspace -scheme TY-Prod -sdk iphoneos -configuration Prod archive -archivePath /Users/jenkins/Documents/workspace/ios-distribution-config/TY-Prod.xcarchive</pre><p>Final result:</p><pre>...<br>▸ Processing Trendyol-Info.plist<br>▸ Generating &#39;Trendyol.app.dSYM&#39;<br>▸ Running script &#39;Run Script&#39;<br>▸ Running script &#39;to do script&#39;<br>▸ Running script &#39;[CP] Copy Pods Resources&#39;<br>▸ Touching Trendyol.app (in target: Trendyol)<br>▸ Archive Succeeded</pre><p>The archive was successful as well.</p><h4>Next step: Exporting an IPA</h4><p>Now before we use xcodebuild’s exportArchive option, first we need to create an exportOptions.plist file. The file looks like this:</p><pre>&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;<br>&lt;!DOCTYPE plist PUBLIC &quot;-//Apple//DTD PLIST 1.0//EN&quot; &quot;<a href="http://www.apple.com/DTDs/PropertyList-1.0.dtd">http://www.apple.com/DTDs/PropertyList-1.0.dtd</a>&quot;&gt;<br>&lt;plist version=&quot;1.0&quot;&gt;<br>&lt;dict&gt;<br>    &lt;key&gt;method&lt;/key&gt;<br>    &lt;string&gt;app-store&lt;/string&gt;<br>    &lt;key&gt;teamID&lt;/key&gt;<br>    &lt;string&gt;your own team id&lt;/string&gt;<br>&lt;/dict&gt;<br>&lt;/plist&gt;</pre><p>Method in the file should be <strong>development</strong>, <strong>app-store</strong>, <strong>enterprise</strong> or <strong>ad-hoc</strong>. The teamID should be your Apple team id. You can find your team’s id from <a href="https://developer.apple.com/">https://developer.apple.com</a> in membership section after you log in.</p><p>After we set our exportOptions.plist up, we use xcodebuild’s exportArchive option. As you can see below, we also put the path of our project’s archive file from the previous step and put another path as exportPath which is the location of the IPA output.</p><pre>xcodebuild -exportArchive -archivePath /Users/jenkins/Documents/workspace/ios-distribution/TY-Prod.xcarchive -exportOptionsPlist exportOptions.plist -exportPath /Users/jenkins/Documents/workspace/ios-distribution -allowProvisioningUpdates</pre><p>And we successfully exported our first IPA.</p><pre>▸ Export Succeeded</pre><h4>Next step: Upload the IPA to the app store</h4><p>For uploading an IPA to the store, Apple provides us another tool called <strong>altool</strong>. First thing you should do is add it’s path to the global path so it would be easier to call altool from anywhere.</p><pre>export PATH=$PATH:/Applications/Xcode.app/Contents/Applications/Application\ Loader.app/Contents/Frameworks/ITunesSoftwareService.framework/Support/</pre><p>Now let’s upload our first package to the store.</p><pre>altool --upload-app -f /Users/jenkins/Documents/workspace/ios-distribution-config/TY-Prod.ipa -u your_user_name -p your_password</pre><p>You should use the username and password of the account which has the right permissions for uploading an app to the app store.</p><p>The result:</p><pre>altool[73409:3603060] No errors uploading &#39;/Users/jenkins/Documents/workspace/ios-distribution-config/TY-Prod.ipa&#39;</pre><p>At this step of the pipeline guide, we have</p><ul><li><strong>Built</strong> the app with the <strong>scheme we picked</strong></li><li><strong>Archived</strong> the app</li><li><strong>Exported</strong> the .ipa file</li><li><strong>Uploaded</strong> the .ipa file to the app store</li></ul><p><strong>on our local machine.</strong></p><p><strong>Part 2</strong> of this guide will describe setting a <strong>Jenkins freestyle project</strong> up with parameters and SCM. <a href="https://medium.com/trendyol-tech/building-an-ios-distribution-pipeline-creating-a-freestyle-jenkins-project-part-2-688497f1a712">Part 2 is available here</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d9f443c7dbb5" width="1" height="1" alt=""><hr><p><a href="https://medium.com/trendyol-tech/building-an-ios-distribution-pipeline-local-poc-with-command-line-tools-part-1-d9f443c7dbb5">Building an iOS Distribution Pipeline — Local POC with Command Line Tools(Part 1)</a> was originally published in <a href="https://medium.com/trendyol-tech">Trendyol Tech</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Automated iOS App Documentation via Quick Unit Tests]]></title>
            <link>https://medium.com/trendyol-tech/automated-ios-app-documentation-via-quick-unit-tests-e8c58fc45f5f?source=rss-aec3abf49986------2</link>
            <guid isPermaLink="false">https://medium.com/p/e8c58fc45f5f</guid>
            <category><![CDATA[unit-testing]]></category>
            <category><![CDATA[testing]]></category>
            <category><![CDATA[ios]]></category>
            <category><![CDATA[quick]]></category>
            <category><![CDATA[documentation]]></category>
            <dc:creator><![CDATA[Efekan Egeli]]></dc:creator>
            <pubDate>Tue, 23 Apr 2019 20:25:57 GMT</pubDate>
            <atom:updated>2019-04-23T20:25:57.343Z</atom:updated>
            <content:encoded><![CDATA[<h3>Why do we need documentation?</h3><p>At <a href="https://www.trendyol.com/hakkimizda">Trendyol</a>, we always try to find different ways and approaches to improve our processes and there are lots of them. As the mobile software development team (both iOS &amp; Android) we do monthly retrospective meetings and discuss the problems we have and how to solve them. One of that meetings, we saw that we were not good enough when it comes to onboarding new members to our team.</p><p>As the mobile team lead, my most important job is coming up with different approaches and solutions to these kind of process problems. But before coming up with the solution, I had to divide the problem into pieces.</p><h4>Android</h4><ul><li>Lack of unit tests / unproper unit tests</li><li>High learning curve because of Rx, there are a lot of developers in Turkey who are unfamiliar with the concept</li><li>Lack of documentation</li></ul><h4>iOS</h4><ul><li>Lack of unit tests</li><li>High learning curve because of VIPER architecture</li><li>Lack of documentation</li></ul><h4>Lack of documentation</h4><p>This one is especially important. The company grows as fast as a rocket, so does our apps. There are always new features to build, new business models to try, new a/b test ideas to integrate. Because of this really fast development process, sometimes even our product managers are having hard time tracking what our apps do. As our app grows, the case count in each screen exponentially grows.</p><blockquote>When I wrote this, only code and I knew what it does, now only code knows.</blockquote><p>Everyone was complaining about the lack of documentation as well. So we needed a way for creating one without too much human resource. Our team also wanted to write unit tests with a good and readable structure. We decided to start with iOS and needed to evaluate our options first.</p><h3>XCTest vs Quick</h3><p>XCTest is the standard framework on the iOS platform when it comes to unit tests. <a href="https://github.com/Quick/Quick">Quick</a> is an open source unit test framework built on top of XCTest which makes tests more readable/understandable. So we had to decide between these and we picked the brand following module of our app where users can follow/unfollow the brands they want to hear news from. It was a relatively small module, so it would be a good start for our POC.</p><h4>XCTest</h4><ul><li>Setup</li></ul><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/e4738a196324861dc34303a44da3c27d/href">https://medium.com/media/e4738a196324861dc34303a44da3c27d/href</a></iframe><ul><li>Example Tests</li></ul><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/32e13a5a680df1d5f0deaf0876e877bc/href">https://medium.com/media/32e13a5a680df1d5f0deaf0876e877bc/href</a></iframe><h4>Quick</h4><ul><li>Setup</li></ul><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/19c7e13b04ed75fc60315fe927046090/href">https://medium.com/media/19c7e13b04ed75fc60315fe927046090/href</a></iframe><ul><li>Example tests</li></ul><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/4630751d185ba6e72860a3f6fb30eb45/href">https://medium.com/media/4630751d185ba6e72860a3f6fb30eb45/href</a></iframe><p>We decided to go with <strong>Quick</strong>. Why?</p><ul><li>Quick comes with a matcher framework called <a href="https://github.com/Quick/Nimble">Nimble</a>. It is more readable than XCTest’s <strong>XCTAssert</strong> and it also provides failure messages for failed tests which comes really handy while debugging. With XCTest, you must write your own failure message.</li><li>If you want to make test names human readable with XCTest, you have to write very long function names and things get really ugly after a while. Quick has <strong>context</strong>, <strong>describe</strong> and <strong>it</strong> where you can just write sentences and make it as readable as possible.</li><li>If you haven’t guessed already, we are kind of a structure freak.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/504/1*1MbGd2Zgn-E8JYfeg2fbBQ.jpeg" /></figure><blockquote>Quick has alphabetical execution system. So for instance, it reads “describes” and executes those alphabetically. We used “1-Listing” for documentation purposes however it helps when you know exact execution order when you write tests.</blockquote><p>Everyone says that tests are your code’s/app’s documentation. Yes, we get it but we “really” want to see that in action. Like in a markdown file or as a pdf export.</p><h3>Shell Script to the Rescue</h3><p>We needed a shell script to do the parsing of our spec files and extract the words from “context”s “describe”s and “it”s and write them to a file with markdown syntax. We named the script <strong>“doq”</strong>.</p><h4>Shell Script Explained</h4><p>What it basically does is it looks for our spec files and it starts with the “describe” scopes and seperate them to get their own “context”s and “it”s. Then it digs in to “context”s and gets the the “it”s within them. You can write a Quick test in different ways but the script expects the curly bracket and parenthesis exactly in the format below.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/84b053920bc4cf07c4e1a61d8c2278ac/href">https://medium.com/media/84b053920bc4cf07c4e1a61d8c2278ac/href</a></iframe><h4>Adding as a Run Script</h4><p>We can also add scripts to Xcode as run scripts. That way, each time we build our code base, the document renews itself. We added the doq in UnitTests root folder and how we added the run script shown below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1022/1*mVidJZkcbQiqsaykdcAwww.png" /></figure><h4>Configurations and Limitations of the Script</h4><p>We wrote <strong>doq</strong> specifically for Quick, so the regexes we use in the script especially searches for “*Spec.swift” files and “context”s, “describe”s and “it”s in them.</p><h3>Result</h3><p><strong>Doq</strong> converted our spec files from <strong>this</strong>:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bDBA_hxiAfvW6ZhzcWFqMw.png" /></figure><p>To <strong>this</strong>:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*trW_Zw5XWNg2DwrHMbZWlw.png" /></figure><h3>What’s Next?</h3><ul><li>We will improve the <strong>markdown</strong> syntax the doq uses.</li><li>Define some annotations for <strong>Android</strong> in doq so our Android team will be able to use it as well.</li><li><strong>PDF export</strong> from markdown within doq</li><li><strong>Connect our unit tests with UI tests</strong> and show the video of connected UI test under unit tests in our documentation, we are very excited about this one.</li></ul><h3>References</h3><ul><li><a href="https://github.com/Quick/Quick">https://github.com/Quick/Quick</a></li><li><a href="https://github.com/Quick/Nimble">https://github.com/Quick/Nimble</a></li></ul><h3>Feedback</h3><p>We are open to all kinds of feedbacks and want to improve the app documentation systems together. You can find the doq <a href="https://github.com/efekanegeli/doq">here</a> and you can open PRs, fork it, edit it however you like.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e8c58fc45f5f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/trendyol-tech/automated-ios-app-documentation-via-quick-unit-tests-e8c58fc45f5f">Automated iOS App Documentation via Quick Unit Tests</a> was originally published in <a href="https://medium.com/trendyol-tech">Trendyol Tech</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>