<?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[Tilicho Labs - Medium]]></title>
        <description><![CDATA[We are a digital product studio based out of India. We transform product ideas into incredible products. We partner with both startup founders and experienced enterprises to help them take their product ideas to the next level - Medium]]></description>
        <link>https://medium.com/tilicholabs?source=rss----3cc8c50e778b---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>Tilicho Labs - Medium</title>
            <link>https://medium.com/tilicholabs?source=rss----3cc8c50e778b---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 19:11:25 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/tilicholabs" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[User Story = Persona + Need + Purpose]]></title>
            <link>https://medium.com/tilicholabs/user-story-persona-need-purpose-d1c502ff7715?source=rss----3cc8c50e778b---4</link>
            <guid isPermaLink="false">https://medium.com/p/d1c502ff7715</guid>
            <category><![CDATA[requirements-management]]></category>
            <category><![CDATA[user-stories]]></category>
            <category><![CDATA[user-story-card]]></category>
            <category><![CDATA[munnaprawin]]></category>
            <category><![CDATA[agile-development]]></category>
            <dc:creator><![CDATA[MunnaPraWiN]]></dc:creator>
            <pubDate>Tue, 17 May 2022 15:21:39 GMT</pubDate>
            <atom:updated>2022-05-17T15:19:56.422Z</atom:updated>
            <content:encoded><![CDATA[<p>User stories are one of the core components of an agile program. User stories help us fit our user personas into the context of the product we’re designing. While the bio of a user persona describes their life and woes, the user story describes how they use a feature of your product — in layman’s terms!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/0*lr5fJ7MRpA_Pg7AW.gif" /></figure><p>A user story is an informal, general explanation of a software feature written from the perspective of the end user. Its purpose is to articulate how a software feature will provide value to the customer.User stories are probably the most popular agile technique to capture product functionality.</p><p>Working with user stories is easy. But telling effective stories can be hard. It’s tempting to think that user stories are, simply put, software system requirements. But they’re not.</p><p>User stories are simple, yet extremely powerful constructs: they describe pieces of functionality <em>from a user’s point of view</em>, expressed in a solid, compact way. They reflect <em>what</em> a particular class of <em>user needs</em> and the <em>value to be gained</em>. The format is very simple and easy to use.</p><p>The User Story should answer 3 questions:</p><ul><li>Who are we building it for? — <strong><em>As a</em></strong> &lt;type of user&gt;</li><li>What are we building? — <strong><em>I want to </em></strong><em>&lt;be able to perform/do something&gt;</em></li><li>Why are we building it? — <strong><em>so that </em></strong><em>&lt;I get some form of value or benefit&gt;</em></li></ul><p>Consider the following when writing user stories:</p><ul><li>Acceptance Criteria</li><li>Start with Epics</li><li>If possible write user stories collaboratively</li><li>User stories ≠ tasks</li><li>Tag stories, add metadata</li><li>Refine the stories until they are ready</li><li>Outline subtasks or tasks</li><li>User personas</li><li>Include Test Scenarios</li><li>Exclusion Criteria</li><li>Have Technical Description</li><li>How to test (Optional &lt;filled out by developer&gt; )</li><li>UX/UI Designs</li><li>Definition of “done”</li><li>Timelines</li></ul><p>These factors will help you decide if your user story is actually making a conversation or not.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*J-yvXwTeV3Gfm4p_.png" /></figure><p>Generally, Product Owner is responsible for User Stories. But there are often doubts about who can write them — And the answer is “Anybody”. Anybody who has clarity on the requirement can add details in, usually, if there is a Business Analyst in the team, they would document requirements, and in other teams the team member documents them. In the end, the Product owner should, however, review and accept them.</p><p>A good practice to make sure the User Story is of proper quality is to adhere to the criteria of Bill Wake’s INVEST acronym. INVEST also helps to determine whether the User Story is well understood and ready for the development team to start working on it.</p><ul><li>Independent — the User Story should not depend on another User Story, so User Stories can be developed in any sequence.</li><li>Negotiable — details of the User Story are negotiated in a verbal conversation between the Product Owner and the development team.</li><li>Valuable — the User Story should bring needed value to the user/customer.</li><li>Estimable — the User Story should be understood well enough by the development team to estimate it.</li><li>Small — the User Story should be small enough to fit in an iteration.</li><li>Testable — proper acceptance criteria should be written for the User Story, so it can be validated.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/539/0*LTHibq1VvkOEESVW.png" /></figure><p>For practical user story examples please refer the link</p><p><a href="https://www.justinmind.com/blog/user-story-examples/">17 User story examples for when the ink runs dry</a></p><p><em>That’s it!</em></p><p><em>But don’t forget creativity is the key. Find what suits the culture of your team, what you can do to enhance your user stories.</em></p><p><em>Stay tuned to know more! See you later!</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d1c502ff7715" width="1" height="1" alt=""><hr><p><a href="https://medium.com/tilicholabs/user-story-persona-need-purpose-d1c502ff7715">User Story = Persona + Need + Purpose</a> was originally published in <a href="https://medium.com/tilicholabs">Tilicho Labs</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Export data from DynamoDB]]></title>
            <link>https://medium.com/tilicholabs/export-data-from-dynamodb-3f6127aff9bf?source=rss----3cc8c50e778b---4</link>
            <guid isPermaLink="false">https://medium.com/p/3f6127aff9bf</guid>
            <category><![CDATA[dynamodb]]></category>
            <category><![CDATA[json]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[csv-file]]></category>
            <category><![CDATA[lambda]]></category>
            <dc:creator><![CDATA[Ramesh Vantaku]]></dc:creator>
            <pubDate>Mon, 21 Mar 2022 15:02:50 GMT</pubDate>
            <atom:updated>2022-03-21T15:02:46.609Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UTXHLHU43V2OX0fq1f48JQ.jpeg" /><figcaption>Export from DynamoDB to CSV</figcaption></figure><p>In this blog post, I’ll explain the export data from a <a href="https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/workbench.querybuilder.exportcsv.html">DynamoDB</a> table to a CSV file.</p><p><a href="https://aws.amazon.com/dynamodb/">DynamoDB</a> is Amazon AWS’s managed NoSQL database service.</p><p>For really big datasets, running a continuous (and parallel) scan might be time consuming and fragile process (imagine it dying in the middle).</p><p>Fortunately, the easiest way to achieve what you wanted by using below code and run any task/script after generating CSV.</p><p>DynamoDB data is exported in two steps. First, we convert DynamoDB data to JSON, then as second step, export that json to CSV.</p><h3>Step 1: Export <strong>DynamoDB to JSON file</strong></h3><pre>const AWS = require(&quot;aws-sdk&quot;);<br>AWS.config.update({ region: &quot;us-east-1&quot; });<br>const fs = require(&quot;fs&quot;);<br>const TABLE_NAME = &quot;Write your table name&quot;;</pre><pre>const docClient = new AWS.DynamoDB.DocumentClient({<br>  sslEnabled: false,<br>  paramValidation: false,<br>  convertResponseTypes: false,<br>  convertEmptyValues: true,<br>});</pre><pre>let jsonExport = async ()=&gt;{<br>  let queryParams = {<br>    TableName: TABLE_NAME,<br>  };</pre><pre>  let result = [];<br>  let items;</pre><pre>  do {<br>        items = await docClient.scan(queryParams).promise();</pre><pre>        items.Items.forEach((item) =&gt; result.push(item));</pre><pre>        queryParams.ExclusiveStartKey = items.LastEvaluatedKey;</pre><pre>    } while (typeof items.LastEvaluatedKey != &quot;undefined&quot;) {</pre><pre>       await fs.writeFileSync(&quot;prodUser.json&quot;,JSON.stringify(result, null, 4));<br>       console.info(&quot;Available csv records:&quot;, result.length);<br>    }</pre><pre>}</pre><pre>jsonExport()<br>  .then((res) =&gt; {<br>    console.log(res);<br>  })<br>  .catch((err) =&gt; {<br>    console.log(err);<br>  });</pre><p>Reference: <a href="https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/DataExport.html">Exporting DynamoDB table data to Amazon S3 — Amazon DynamoDB</a></p><h3>Step 2: Convert JSON file to CSV</h3><p>Once we have converted JSON data, we need to give specific attributes in the database in the fields array.Otherwise you do not need to give options object if you want all the attributes in the database.</p><pre>let export_data = require(&quot;./prodUser.json&quot;);<br>const { Parser } = require(&quot;json2csv&quot;);<br>let fs = require(&quot;fs&quot;)</pre><pre>const fields = [<br>  &quot;id&quot;,<br>  &quot;full_name&quot;,<br>  &quot;mobile&quot;,<br>  &quot;bank_details&quot;,<br>] //particular attributes coming</pre><pre>const options = {<br>  fields,<br>};</pre><pre>try {<br>  const parser = new Parser(options);//If you want all the attributes in the database, it is enough to remove the name options.<br>  const csv = parser.parse(export_data);</pre><pre>   fs.writeFileSync(&quot;file.csv&quot;, JSON.stringify(csv, null, 4));</pre><pre>   console.info(&quot;Available csv records:&quot;, csv.length);</pre><pre>  } catch (err) {<br>  console.error(err);<br>}</pre><p>Thank you for reading!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3f6127aff9bf" width="1" height="1" alt=""><hr><p><a href="https://medium.com/tilicholabs/export-data-from-dynamodb-3f6127aff9bf">Export data from DynamoDB</a> was originally published in <a href="https://medium.com/tilicholabs">Tilicho Labs</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[DynamoDB Pagination]]></title>
            <link>https://medium.com/tilicholabs/dynamodb-pagination-7b9742d1078a?source=rss----3cc8c50e778b---4</link>
            <guid isPermaLink="false">https://medium.com/p/7b9742d1078a</guid>
            <category><![CDATA[scan]]></category>
            <category><![CDATA[dynamodb]]></category>
            <category><![CDATA[query]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[pagination]]></category>
            <dc:creator><![CDATA[Ramesh Vantaku]]></dc:creator>
            <pubDate>Mon, 21 Mar 2022 15:02:48 GMT</pubDate>
            <atom:updated>2022-03-21T15:02:46.016Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CL16eHv53fKzf_g_n7_6jg.jpeg" /></figure><h4>What is Pagination?</h4><p>Pagination is splitting a database output into manageable chunks or pages. To do this:</p><ol><li>Decide on the maximum number of database rows that can be included in each page. You may hard code this value, or you define it in a variable so that the value may be changed at runtime.</li><li>Inform the user that other ‘pages’ are available and provide a mechanism whereby the user is able to select a different ‘page’ of details. I currently use a set of hyperlinks in a separate pagination area which looks like:</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/950/1*bXPhID6jyg6Yz8u862-M5A.png" /><figcaption>Pagination area</figcaption></figure><h4>What pagination support does DynamoDB provide?</h4><p>Amazon DynamoDB documentation says that DynamoDB <em>paginates</em> the results from scan/query operations. With pagination, the scan results are divided into “pages” of data that are 1 MB in size (or less). An application processes the first page of results, then the second page, and so on.</p><p>A single scan will only return a result set that fits within the 1 MB size limit. To determine whether there are more results, and to retrieve them one page at a time, your application should do the following:</p><ol><li>Examine the Scan result:</li></ol><ul><li>If the result contains a LastEvaluatedKey element, proceed to step 2.</li><li>If there is <em>no</em> LastEvaluatedKey in the results, then you are done. There are no more items to be retrieved.</li></ul><p>2. Construct a new Scan request, with the same parameters as the previous one — but this time, take the LastEvaluatedKey value from step 1 and use it as the ExclusiveStartKey parameter in the new Scan request.</p><p>3. Run the new Scan request.</p><h4>How pagination is done?</h4><p>There are two approaches for the pagination to be done.</p><h3>1st Approach — using scan</h3><ul><li>On the webpage where pagination is supported, the browser sends the LastEvaluatedKey to the server.</li><li>To access the first page, browser sends the LastEvaluatedKey as undefined. With this undefined key, server sends the first page data and also sends the LastEvaluatedKey for the next page.</li><li>To access the next page, the browser sends back the LastEvaluatedKey and the same procedure continues.</li></ul><pre>const async = require(&quot;async&quot;);<br>const _ = require(&quot;underscore&quot;);<br>const AWS = require(&quot;aws-sdk&quot;);<br>AWS.config.update({ region: &#39;us-west-2&#39; });<br><br>const docClient = new AWS.DynamoDB.DocumentClient();<br><br>var startKey = [];<br>var results = [];<br>var pages = 0;<br>async.doWhilst(<br>    //iteratee<br>    (callback)=&gt;{<br>        let params = {<br>            TableName: &#39;td_notes_test&#39;,<br>            Limit: 3<br>        };<br><br>        if(!_.isEmpty(startKey)) {<br>            params.ExclusiveStartKey = startKey;<br>        }<br><br>        docClient.scan(params, (err, data)=&gt;{<br>            if(err) {<br>                console.log(err);<br>                callback(err, {});<br>            } else {<br>                if(typeof data.LastEvaluatedKey !== &#39;undefined&#39;) {<br>                    startKey = data.LastEvaluatedKey;<br>                } else {<br>                    startKey = [];<br>                }<br><br>                if(!_.isEmpty(data.Items)){<br>                    results = _.union(results, data.Items);<br>                }<br><br>                pages++;<br><br>                callback(null, results);<br>            }<br>        });<br>    },<br><br>    //truth test<br>    ()=&gt;{<br>        if(_.isEmpty(startKey)) {<br>            return false;<br>        } else {<br>            return true;<br>        }<br>    },<br><br>    //callback<br>    (err, data) =&gt; {<br>        if(err) {<br>            console.log(err);<br>        } else {<br>            console.log(data);<br>            console.log(&quot;Item Count&quot;, data.length);<br>            console.log(&quot;Pages&quot;, pages);<br>        }<br>    }<br>);</pre><h3><strong>2nd approach — using Query</strong></h3><p>Incase pagination with particular attribute then query with particular Partition key its use the below method.</p><pre>const AWS = require(&quot;aws-sdk&quot;);<br>AWS.config.update({ region: &quot;ap-south-1&quot; });<br>const TABLE_NAME = &quot;write your table name&quot;;<br><br>const docClient = new AWS.DynamoDB.DocumentClient({<br>  sslEnabled: false,<br>  paramValidation: false,<br>  convertResponseTypes: false,<br>  convertEmptyValues: true,<br>});<br><br>let paginationDB = async () =&gt; {<br>  <br>   let queryParams = {<br>     TableName: TABLE_NAME,<br>     KeyConditionExpression: &quot;#PK =  :PK&quot;,//Enter partitionKey <br>     ExpressionAttributeNames: {<br>       &quot;#PK&quot;: &quot;id&quot;,// Enter partitionKey name<br>    },<br>     ExpressionAttributeValues: {<br>       &quot;:PK&quot;: &quot;123456&quot;, // Enter partitionKey value<br>    },<br>  };<br>  let result = [];<br>  let items;<br>  do {<br>    items = await docClient.query(queryParams).promise();<br>    items.Items.forEach((item) =&gt; result.push(item));<br>    queryParams.ExclusiveStartKey = items.LastEvaluatedKey;</pre><pre>  } while (typeof items.LastEvaluatedKey != &quot;undefined&quot;);<br>     console.log(&quot;result&quot;, result);<br>     console.info(&quot;Available count size:&quot;, result.length);<br>};<br><br>paginationDB()<br>  .then((res) =&gt; {<br>    console.log(res);<br>  })<br>  .catch((err) =&gt; {<br>    console.log(err);<br>  });</pre><p>Thank you for reading!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7b9742d1078a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/tilicholabs/dynamodb-pagination-7b9742d1078a">DynamoDB Pagination</a> was originally published in <a href="https://medium.com/tilicholabs">Tilicho Labs</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Addons Installation in TestProject]]></title>
            <link>https://medium.com/tilicholabs/addons-installation-in-testproject-1472c13af178?source=rss----3cc8c50e778b---4</link>
            <guid isPermaLink="false">https://medium.com/p/1472c13af178</guid>
            <category><![CDATA[automation-testing]]></category>
            <category><![CDATA[testproject]]></category>
            <category><![CDATA[testing]]></category>
            <dc:creator><![CDATA[Naidu]]></dc:creator>
            <pubDate>Mon, 21 Mar 2022 15:02:48 GMT</pubDate>
            <atom:updated>2022-03-21T15:02:45.408Z</atom:updated>
            <content:encoded><![CDATA[<h4><strong>Addons installation</strong></h4><p>Let’s see how to install any <strong>Addons</strong> in TestProject.</p><ol><li><a href="https://app.testproject.io/signup/"><strong>Login</strong></a> to your TestProject account.</li><li>Now the dashboard is ready, you can install the <strong>Addons</strong>.</li><li>Click on<strong> </strong>the <strong>Addons </strong>section at the top of the screen user lands on the Addons page.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ZWids_1kBYlnODOx" /></figure><p>You will see the Addons that are available for all the users of TestProject in the <strong>community</strong> section.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*6BycjmAZFttnlSYK" /></figure><p>Click on the <strong>Installed Addons</strong> section, which shows the Addons, that have been installed by you. The “<strong>Installed Addons</strong>” section contains two sub-sections.</p><ol><li>My Addons</li><li>Community Addons</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*NijvvdHTkw6hxhrG" /></figure><h4><strong>My Addons</strong></h4><p>This section shows the installed Addons, which are the <strong>private addons.</strong></p><h4><strong>Community Addons</strong></h4><p>This section shows the installed Addons, which you have installed from the <strong>community addons.</strong></p><p>Search the <strong>Addon name </strong>in the search box that you want to install and press the <strong>ENTER</strong>. Suppose we want to find an add Addon related to<strong> File upload</strong>, then we search for <strong>“File upload</strong>” in the search box and press <strong>ENTER</strong>. We will see all Addons related to file upload, as shown below:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*7E2OnZGxibUZcHm1" /></figure><p>Now, click on the required Addon that you want to add to your TestProject. As soon as a popup will be shown in the below image:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*byGiG1l5mEcpFEUm" /></figure><p>The popup will show some important information about the Addon, such as:</p><ul><li>Name of the Addon.</li><li>The description about an Addon that what we can do with the help of this Addon.</li><li>Different ways through which we can perform the relevant action using this Addon.</li></ul><p>Now click on the <strong>Instal</strong>l button in the popup. After the successful installation, it will give a successful message.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*IQ944Wq1kdMCgI4P" /></figure><p>Now close the popup, and here the installation process for the Addon is completed. Now go to the “<strong>Installed Addons</strong>” section, and you can see the Addon that was recently installed.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*nEnnxI7VU6W8Ardj" /></figure><p>You have successfully installed the Addon, and it is now ready for use in your test cases.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1472c13af178" width="1" height="1" alt=""><hr><p><a href="https://medium.com/tilicholabs/addons-installation-in-testproject-1472c13af178">Addons Installation in TestProject</a> was originally published in <a href="https://medium.com/tilicholabs">Tilicho Labs</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[AWS DynamoDB DocumentClient & Node.js — Complete Table Methods]]></title>
            <link>https://medium.com/tilicholabs/aws-dynamodb-documentclient-node-js-complete-table-methods-afcac4d1fb3?source=rss----3cc8c50e778b---4</link>
            <guid isPermaLink="false">https://medium.com/p/afcac4d1fb3</guid>
            <category><![CDATA[dynamodb]]></category>
            <category><![CDATA[scan]]></category>
            <category><![CDATA[client-document]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[query]]></category>
            <dc:creator><![CDATA[Ramesh Vantaku]]></dc:creator>
            <pubDate>Mon, 21 Mar 2022 15:01:21 GMT</pubDate>
            <atom:updated>2022-03-21T15:01:20.349Z</atom:updated>
            <content:encoded><![CDATA[<h3>AWS DynamoDB DocumentClient &amp; Node.js — Complete Table Methods</h3><p>In this blog post, I’ll take you through how to perform variety of operations starting from simple queries ending with <a href="https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/transactions.html">complex transactions</a> using AWS DynamoDB DocumentClient and Node.js.</p><p>There are two basic ways to interact with DynamoDB tables from Node.js applications:</p><ul><li>Class AWS.DynamoDB from AWS SDK for JavaScript.</li><li>AWS.DynamoDB.DocumentClient which simplifies working with DynamoDB items by abstracting away DynamoDB Types and converting responses to native JS</li></ul><p>This discussion mostly focus on DocumentClient but some of the operations like creating tables must be run using classical DynamoDB service.</p><h3><strong>Setup</strong></h3><p>Node.js application to work with DynamoDB is first make sure that <strong>aws-sdk</strong> is installed by using this command <strong>npm i aws-sdk — save. </strong>Once installed then copy the below code.</p><pre>const AWS = require(&quot;aws-sdk&quot;) // Or use `import` syntax for newer ES versions<br><br>const dynamoDB = new AWS.DynamoDB({<br>  region: &quot;us-east-1&quot;, // If not set, will get from ~/.aws directory or environment variable<br>  // and rest of properties<br>})<br><br>// Or<br><br>const documentClient = new AWS.DynamoDB.DocumentClient({<br>  region: &quot;us-east-1&quot;,<br>  // and rest of properties<br>})</pre><h3><strong>Create table</strong></h3><p>Database Structures data in tables, so if you want to save data to DynamoDB, first you need to create a table. You can do that using AWS-SDK for Javascript, like this</p><pre>const AWS = require(&quot;aws-sdk&quot;)<br>const dynamoDB = new AWS.DynamoDB({ region: &quot;us-east-1&quot; })<br><br>dynamoDB<br>  .createTable({<br>    AttributeDefinitions: [<br>      {<br>        AttributeName: &quot;id&quot;,<br>        AttributeType: &quot;S&quot;,<br>      },<br>    ],<br>    KeySchema: [<br>      {<br>        AttributeName: &quot;id&quot;,<br>        KeyType: &quot;HASH&quot;,<br>      },<br>    ],<br>    BillingMode: &quot;PAY_PER_REQUEST&quot;,<br>    TableName: &quot;Enter your table name&quot;,<br>  })<br>  .promise()<br>  .then(data =&gt; console.log(&quot;Success!&quot;, data))<br>  .catch(console.error)</pre><p>After this call resolves, it does not necessarily mean that table status is ACTIVE and it&#39;s is ready for read and write operations. Before start manipulating items in it, we should check if it&#39;s in ACTIVE state first using describeTable function ran every 5 seconds until it is ready:</p><pre>const backoffInterval = 5000 // 5 seconds<br><br>const waitForTable = TableName =&gt;<br>  dynamoDB<br>    .describeTable({ TableName })<br>    .promise()<br>    .then(data =&gt; {<br>      if (data.Table.TableStatus !== &quot;ACTIVE&quot;) {<br>        console.log(<br>          `Table status: ${data.Table.TableStatus}, retrying in ${backoffInterval}ms...`<br>        )<br>        return new Promise(resolve =&gt; {<br>          setTimeout(() =&gt; waitForTable().then(resolve), backoffInterval)<br>        })<br>      } else {<br>        return<br>      }<br>    })<br>    .catch(error =&gt; {<br>      console.warn(<br>        `Table not found! Error below. Retrying in ${backoffInterval} ms...`,<br>        error<br>      )<br><br>      return new Promise(resolve =&gt; {<br>        setTimeout(() =&gt; waitForTable().then(resolve), backoffInterval)<br>      })<br>    })<br><br>waitForTable(&quot;my-table&quot;).then(() =&gt; console.log(`my-table is ready!`))</pre><h3>Get All Items / Scan in DynamoDB</h3><p>After our table is provisioned and it’s in ACTIVE state, first thing that we probably would like to do is get all items. If you want to narrow your search results, use FilterExpressions combined with ExpressionAttributeNames object like so:</p><pre>const AWS = require(&quot;aws-sdk&quot;)<br>const dynamoDB = new AWS.DynamoDB.DocumentClient({ region: &quot;us-east-1&quot; })<br><br>dynamoDB<br>  .scan({<br>    TableName: &quot;my-table&quot;,<br>    FilterExpression:<br>      &quot;attribute_not_exists(deletedAt) AND contains(firstName, :firstName)&quot;,<br>    ExpressionAttributeValues: {<br>      &quot;:firstName&quot;: &quot;John&quot;,<br>    },<br>  })<br>  .promise()<br>  .then(data =&gt; console.log(data.Items))<br>  .catch(console.error)</pre><p>You will in fact return all the items in the table under one condition. you have less than 1MB of data inside it.</p><h3>Get Item</h3><p>If you know the exact Partition Key (and Sort Key if using composite key) of the item that you want to retrieve from the DynamoDB table, you can use get operation:</p><pre>const AWS = require(&quot;aws-sdk&quot;)<br>AWS.config.update({ region: &quot;us-east-1&quot; })<br>const dynamoDB = new AWS.DynamoDB.DocumentClient()<br><br>dynamoDB<br>  .get({<br>    TableName: &quot;my-table&quot;,<br>    Key: {<br>      id: &quot;123&quot;, // id is the Partition Key, &#39;123&#39; is the value of it<br>    },<br>  })<br>  .promise()<br>  .then(data =&gt; console.log(data.Item))<br>  .catch(console.error)</pre><h3>Batch Get Item</h3><p>The BatchGetItem operation returns the attributes of one or more items from one or more tables. You identify requested items by primary key.</p><p>A single operation can retrieve up to 16 MB of data, which can contain as many as 100 items. BatchGetItem returns a partial result if the response size limit is exceeded, the table&#39;s provisioned throughput is exceeded, or an internal processing failure occurs. If a partial result is returned, the operation returns a value for UnprocessedKeys. You can use this value to retry the operation starting with the next item to get.</p><pre>const AWS = require(&quot;aws-sdk&quot;)<br>AWS.config.update({ region: &quot;us-east-1&quot; })<br>const dynamoDB = new AWS.DynamoDB.DocumentClient()<br><br>dynamoDB<br>  .batchGet({<br>    RequestItems: {<br>      &quot;my-table&quot;: {<br>        Keys: [<br>          {<br>            id: &quot;123&quot;,<br>          },<br>          {<br>            id: &quot;124&quot;,<br>          },<br>        ],<br>      },<br>      &quot;other-table&quot;: {<br>        Keys: [<br>          {<br>            id: &quot;abc&quot;,<br>          },<br>          {<br>            id: &quot;abd&quot;,<br>          },<br>        ],<br>      },<br>    },<br>  })<br>  .promise()<br>  .then(data =&gt; console.log(data.Responses))<br>  .catch(console.error)</pre><h4><a href="https://docs.aws.amazon.com/amazondynamodb/latest/APIReference/API_PutItem.html">Put Item</a></h4><p>put operation creates a new item, or replaces an old item with a new item if it&#39;s using the same key(s)</p><pre>const AWS = require(&quot;aws-sdk&quot;);<br>const dynamoDB = new AWS.DynamoDB.DocumentClient({ region: &quot;us-east-1&quot; });<br><br>dynamoDB<br>  .put({<br>    Item: {<br>      id: &quot;156788&quot;,<br>      name: &quot;skoda&quot;,<br>      email: &quot;skoda@do.io&quot;,<br>    },<br>    TableName: &quot;my-table&quot;,<br>  })<br>  .promise()<br>  .then((data) =&gt; console.log(data.Attributes))<br>  .catch(console.error);</pre><h4><a href="https://docs.aws.amazon.com/amazondynamodb/latest/APIReference/API_BatchWriteItem.html">Batch Write / Put Item</a></h4><p>The BatchWriteItem operation puts or deletes multiple items in one or more tables. A single call to BatchWriteItem can transmit up to 16MB of data over the network, consisting of up to 25 item put or delete operations. While individual items can be up to 400 KB once stored</p><p>BatchWriteItem cannot update items. To update items, use the UpdateItem action.</p><pre>const AWS = require(&quot;aws-sdk&quot;)<br>const dynamoDB = new AWS.DynamoDB.DocumentClient({ region: &quot;ap-south-1&quot; })<br><br>dynamoDB<br>  .batchWrite({<br>    RequestItems: {<br>      MyTable: [<br>        {<br>          DeleteRequest: {<br>            Key: { id: &quot;13456&quot; },<br>          },<br>        },<br>        {<br>          PutRequest: {<br>            Item: {<br>              id: &quot;456&quot;,<br>              name: &quot;skoda&quot;,<br>              email: &quot;tdanesh@dynamodb.in&quot;,<br>              description: &quot;Professional DynamoDB Client&quot;,<br>            },<br>          },<br>        },<br>      ],<br>    },<br>  })<br>  .promise()<br>  .then(data =&gt; console.log(data.Attributes))<br>  .catch(console.error)</pre><h4><a href="https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/GettingStarted.NodeJs.04.html">Query for a Set of Items</a></h4><p>You can use the query method to retrieve data from a table. You must specify a partition key value; the sort key is optional.It also allows to use multiple operators for SortKey such as begins_with or mathematical ones like &gt;, =, &gt;= and so on.</p><pre>const AWS = require(&#39;aws-sdk&#39;);<br>const dynamoDB = new AWS.DynamoDB.DocumentClient({region:&#39;us-east-1&#39;});<br><br>dynamoDB<br>  .query({<br>    TableName: &#39;your-table name&#39;,<br>    KeyConditionExpression: &#39;id = :hashKey and date &gt; :rangeKey&#39;<br>    ExpressionAttributeValues: {<br>      &#39;:hashKey&#39;: &#39;12345&#39;,<br>      &#39;:rangeKey&#39;: 2015010112<br>    }<br>  })<br>  .promise()<br>  .then(data =&gt; console.log(data.Items))<br>  .catch(console.error);</pre><h4><a href="https://dev.to/rafalwilinski/aws-dynamodb-documentclient-node-js-complete-cheat-sheet-551m">Simple Transaction</a></h4><p>DynamoDB also support <a href="https://dynobase.dev/dynamodb-transactions/">transactions</a> — they allow to run multiple write operations atomically meaning that either all of operations are executed successfully or none of them. It is especially useful when dealing with applications where data integrity is essential, e.g. in e-commerce — adding an item to a cart and decrementing count of items still available to buy.</p><p>Such flow should:</p><ul><li>Should happen atomically — these two operations should be treated as one, we don’t want to have a single moment in time where there’s a discrepancy in items count</li><li>Should succeed only if count of items available to buy is greater than zero</li></ul><p>Described flow can be modelled in Javascript &amp; DocumentClient like this:</p><pre>const AWS = require(&quot;aws-sdk&quot;)<br>const dynamoDB = new AWS.DynamoDB.DocumentClient({ region:&#39;us-east-1&#39; })<br><br>await dynamoDB.transactWrite({<br>  TransactItems: [<br>    {<br>      Put: { // Add item to cart<br>        Item: {<br>          id: &#39;1&#39;,<br>          count: &#39;1&#39;<br>        }<br>        TableName: &quot;CartTable&quot;,<br>      },<br>    },<br>    {<br>      Update: { <br>// decrement count of items available to buy only if the count is greater than zero<br>        ConditionExpression: &quot;#count &gt; 0&quot;,<br>        ExpressionAttributeNames: { &quot;#count&quot;: &quot;count&quot; },<br>        ExpressionAttributeValues: {<br>          &quot;:value&quot;: 1,<br>        },<br>        Key: {<br>          id: &#39;12345&#39;,<br>        }<br>        TableName: &quot;ItemsTable&quot;,<br>        UpdateExpression: &quot;SET #count = :count - :value&quot;,<br>      },<br>    },<br>  ],<br>}).promise();</pre><h3>Read Transaction</h3><p>Transaction can be also used for reading data atomically. Like in <a href="https://dev.to/rafalwilinski/aws-dynamodb-documentclient-node-js-complete-cheat-sheet-551m#batch-get">batchGet</a>, you can retrieve the data from multiple tables in a single call:</p><pre>const AWS = require(&quot;aws-sdk&quot;)<br>const dynamoDB = new AWS.DynamoDB.DocumentClient({ region: &quot;us-east-1&quot; })<br><br>await dynamoDB<br>  .transactGet({<br>    TransactItems: [<br>      {<br>        Get: {<br>          TableName: &quot;TableOne&quot;,<br>          Key: {<br>            HashKey: &quot;abcd&quot;,<br>          },<br>        },<br>      },<br>      {<br>        Get: {<br>          TableName: &quot;TableTwo&quot;,<br>          Key: {<br>            HashKey: &quot;1234&quot;,<br>          },<br>        },<br>      },<br>    ],<br>  })<br>  .promise()</pre><h3>Query with Sorting</h3><p>You can use the sort-key and apply the ScanIndexForward parameter in a <a href="http://docs.aws.amazon.com/amazondynamodb/latest/developerguide/QueryAndScan.html?shortFooter=true#QueryAndScan.Query">query</a> to sort in either ascending or descending order. Here I limit items returned to 1.However, if you need to sort DynamoDB results on sort key descending or ascending, you can use following syntax:</p><pre>const AWS = require(&#39;aws-sdk&#39;);<br>const dynamoDB = new AWS.DynamoDB.DocumentClient({ region: &#39;ap-south-1&#39; });<br><br>dynamoDB<br>  .query({<br>    TableName: &#39;my-table&#39;,<br>    IndexName: &#39;Index&#39;, // Main one<br>    KeyConditionExpression: &#39;id = :hashKey and date &gt; :rangeKey&#39;<br>    ExpressionAttributeValues: {<br>      &#39;:hashKey&#39;: &#39;12345&#39;,<br>      &#39;:rangeKey&#39;: 2015010112<br>    },<br>    ScanIndexForward: true // true or false to sort by &quot;date&quot; Sort/Range key ascending or descending<br>  })<br>  .promise()<br>  .then(data =&gt; console.log(data.Items))<br>  .catch(console.error);</pre><p>Thank you for reading!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=afcac4d1fb3" width="1" height="1" alt=""><hr><p><a href="https://medium.com/tilicholabs/aws-dynamodb-documentclient-node-js-complete-table-methods-afcac4d1fb3">AWS DynamoDB DocumentClient &amp; Node.js — Complete Table Methods</a> was originally published in <a href="https://medium.com/tilicholabs">Tilicho Labs</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Kotlin Coroutines [Part-2]]]></title>
            <link>https://medium.com/tilicholabs/kotlin-coroutines-part-2-be7c650ad684?source=rss----3cc8c50e778b---4</link>
            <guid isPermaLink="false">https://medium.com/p/be7c650ad684</guid>
            <category><![CDATA[kotlin-coroutines]]></category>
            <category><![CDATA[mobile-app-development]]></category>
            <category><![CDATA[kotlin]]></category>
            <category><![CDATA[android-app-development]]></category>
            <category><![CDATA[android]]></category>
            <dc:creator><![CDATA[Bharath Kandula]]></dc:creator>
            <pubDate>Fri, 18 Feb 2022 03:31:12 GMT</pubDate>
            <atom:updated>2022-02-18T03:31:11.004Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*90_MxRZD3GakfnQRxQ6o7g.jpeg" /></figure><p>This blog is a part of <strong>Kotlin Coroutines</strong> series. If you want to check <strong>Part-1</strong>:</p><p><a href="https://medium.com/tilicholabs/kotlin-coroutines-part-1-641f849e7b59">Kotlin Coroutines [Part-1]</a></p><p>Continuing…</p><blockquote>Cancellation and timeouts</blockquote><h3>Cancellation</h3><p>When launching multiple coroutines, it can be a pain to keep track of them or cancel each individually. Rather, we can rely on canceling the entire scope coroutines are launched into as this will cancel all of the child coroutines created:</p><pre>// assume we have a scope defined for this layer of the app<br>val job1 = scope.launch { … }<br>val job2 = scope.launch { … }<br>scope.cancel()</pre><blockquote>Canceling the scope cancels its children</blockquote><p>Sometimes you might need to cancel only one coroutine.<br>Calling <strong>job1.cancel</strong> ensures that only that specific coroutine gets canceled and all the other siblings are not affected:</p><pre>// assume we have a scope defined for this layer of the app<br>val job1 = scope.launch { … }<br>val job2 = scope.launch { … }<br>// First coroutine will be cancelled and the other one won’t be affected<br>job1.cancel()</pre><blockquote>A canceled child doesn’t affect other siblings</blockquote><p>Coroutines handle cancellation by throwing a special exception: CancellationException. If you want to provide more details on the cancellation reason you can provide an instance of CancellationException when calling .cancel as this is the full method signature:</p><pre>fun cancel(cause: CancellationException? = null)</pre><p>If you don’t provide your own CancellationException instance, a default CancellationException will be created</p><pre>public override fun cancel(cause: CancellationException?) {<br>    cancelInternal(cause ?: defaultCancellationException())<br>}</pre><p>Once you cancel a scope, you won’t be able to launch new coroutines in the canceled scope.</p><blockquote>If we just call cancel, it doesn’t mean that the coroutine work will just stop. If you’re performing some relatively heavy computation, like reading from multiple files, there’s nothing that automatically stops your code from running.</blockquote><p>Let’s take a more simple example and see what happens. Let’s say that we need to <strong>print “Hello” twice a second using coroutines</strong>. We’re going to let the coroutine run for a second and then cancel it. One version of the implementation can look like this:</p><pre>import kotlinx.coroutines.*<br> <br>fun main(args: Array&lt;String&gt;) = runBlocking&lt;Unit&gt; {<br>   val startTime = System.currentTimeMillis()<br>    val job = launch (Dispatchers.Default) {<br>        var nextPrintTime = startTime<br>        var i = 0<br>        while (i &lt; 5) {<br>            // print a message twice a second<br>            if (System.currentTimeMillis() &gt;= nextPrintTime) {<br>                println(&quot;Hello ${i++}&quot;)<br>                nextPrintTime += 500L<br>            }<br>        }<br>    }<br>    delay(1000L)<br>    println(&quot;Cancel!&quot;)<br>    job.cancel()<br>    println(&quot;Done!&quot;)<br>}</pre><p><strong>Output:</strong><br>Hello 0<br>Hello 1<br>Hello 2<br>Cancel!<br>Done!<br>Hello 3<br>Hello 4</p><h4><strong><em>Let’s see what happens step by step:</em></strong></h4><p>When calling launch, we’re creating a new coroutine in the <strong>active</strong> state. We’re letting the coroutine run for 1000ms. So now we see printed:</p><p><strong>Output:</strong><br>Hello 0<br>Hello 1<br>Hello 2</p><p>Once job.cancel is called, our coroutine moves to <em>Cancelling</em> state. But then, we see that Hello 3 and Hello 4 are printed to the terminal. Only after the work is done, the coroutine moves to a <em>Cancelled</em> state.</p><blockquote>The coroutine work doesn’t just stop when cancel is called.</blockquote><p><strong>Checking for job’s active state (</strong> job.isActive or ensureActive() <strong>)</strong></p><p>One option is in our while(i&lt;5) to add another check for the coroutine state:</p><pre>// Since we&#39;re in the launch block, we have access to job.isActive<br>while (i &lt; 5 &amp;&amp; isActive)</pre><p>This means that our work should only be executed while the coroutine is active.</p><p>The Coroutines library provides another helpful method — ensureActive(). Its implementation is:</p><pre>fun Job.ensureActive(): Unit {<br>    if (!isActive) {<br>         throw getCancellationException()<br>    }<br>}</pre><p>Because this method instantaneously throws if the job is not active, we can make this the first thing we do in our while loop:</p><pre>while (i &lt; 5) {<br>    ensureActive()<br>    …<br>}</pre><p>By using ensureActive, you avoid implementing the if statement required by isActive yourself, decreasing the amount of boilerplate code you need to write.</p><h3>Timeout</h3><p>The TimeoutCancellationException that is thrown by <a href="https://kotlin.github.io/kotlinx.coroutines/kotlinx-coroutines-core/kotlinx.coroutines/with-timeout.html">withTimeout</a> is a subclass of <a href="https://kotlin.github.io/kotlinx.coroutines/kotlinx-coroutines-core/kotlinx.coroutines/-cancellation-exception/index.html">CancellationException</a>.</p><pre>withTimeout(1300L) {<br>    repeat(1000) { i -&gt;<br>        println(&quot;I&#39;m sleeping $i ...&quot;)<br>        delay(500L)<br>    }<br>}</pre><p><strong>Output:</strong></p><pre>I&#39;m sleeping 0 ...<br>I&#39;m sleeping 1 ...<br>I&#39;m sleeping 2 ...<br>Exception in thread &quot;main&quot; kotlinx.coroutines.TimeoutCancellationException: Timed out waiting for 1300 ms</pre><p>Cancellation is just an exception, all resources are closed in the usual way. You can wrap the code with timeout in a try {...} catch (e: TimeoutCancellationException) {...} block if you need to do some additional action specifically on any kind of timeout or use the <a href="https://kotlin.github.io/kotlinx.coroutines/kotlinx-coroutines-core/kotlinx.coroutines/with-timeout-or-null.html">withTimeoutOrNull</a> function that is similar to <a href="https://kotlin.github.io/kotlinx.coroutines/kotlinx-coroutines-core/kotlinx.coroutines/with-timeout.html">withTimeout</a> but returns null on timeout instead of throwing an exception:</p><pre>val result = withTimeoutOrNull(1300L) {<br>    repeat(1000) { i -&gt;<br>        println(&quot;I&#39;m sleeping $i ...&quot;)<br>        delay(500L)<br>    }<br>    &quot;Done&quot; // will get cancelled before it produces this result<br>}<br>println(&quot;Result is $result&quot;)</pre><blockquote>There is no longer an exception when running this code</blockquote><p><strong>Output:<br></strong>I&#39;m sleeping 0 ... <br>I&#39;m sleeping 1... <br>I&#39;m sleeping 2... <br>Result is null</p><h3>References</h3><ul><li><a href="https://kotlinlang.org/docs/coroutines-guide.html">https://kotlinlang.org/docs/coroutines-guide.html</a></li><li><a href="https://blog.mindorks.com/mastering-kotlin-coroutines-in-android-step-by-step-guide">https://blog.mindorks.com/mastering-kotlin-coroutines-in-android-step-by-step-guide</a></li><li><a href="https://medium.com/androiddevelopers/cancellation-in-coroutines-aa6b90163629">https://medium.com/androiddevelopers/cancellation-in-coroutines-aa6b90163629</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=be7c650ad684" width="1" height="1" alt=""><hr><p><a href="https://medium.com/tilicholabs/kotlin-coroutines-part-2-be7c650ad684">Kotlin Coroutines [Part-2]</a> was originally published in <a href="https://medium.com/tilicholabs">Tilicho Labs</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What is a RecyclerView and How it works internally?]]></title>
            <link>https://medium.com/tilicholabs/what-is-a-recyclerview-and-how-it-works-internally-2a1fa60399a3?source=rss----3cc8c50e778b---4</link>
            <guid isPermaLink="false">https://medium.com/p/2a1fa60399a3</guid>
            <category><![CDATA[android]]></category>
            <category><![CDATA[recyclerview]]></category>
            <category><![CDATA[recyclerview-in-android]]></category>
            <category><![CDATA[android-app-development]]></category>
            <dc:creator><![CDATA[Ajay]]></dc:creator>
            <pubDate>Fri, 18 Feb 2022 03:31:11 GMT</pubDate>
            <atom:updated>2022-02-21T04:24:54.967Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/500/0*P1ubv05jBhr0nNi9.png" /></figure><p>Wonder how identical horizontal/vertical list views populate in Android like how WhatsApp shows the chats/contacts list? Well, it can all be done using RecyclerView. <strong>RecyclerView is the </strong><strong>ViewGroup that contains the views corresponding to your data</strong>.</p><p>RecyclerView itself is a view added to the parent layout that holds another(card/item) layout using an adapter. Each element in the list is defined by a ViewHolder object.</p><p>RecyclerView is made by improving the efficiency of <a href="https://developer.android.com/reference/android/widget/GridView">GridView</a> and <a href="https://developer.android.com/reference/android/widget/ListView">ListView</a>. As from the name <strong>RecyclerView,</strong> it recycles the views which are out of visibility.</p><h3>Components of RecyclerView</h3><h4>Adapter</h4><p>An Adapter acts as a bridge between an AdapterView and the underlying data for that view. <strong>The adapter provides access to the data items</strong>. The Adapter is also responsible for making a View for each item in the data set.<br>Our Adapter class should extend <a href="https://developer.android.com/reference/androidx/recyclerview/widget/RecyclerView.Adapter"><strong><em>Recycler.Adapter</em></strong></a> class and override below methods for the recycler view to work</p><ul><li>onCreateViewHolder<em> </em>method prepares appropriate views for the individual data in the list.</li><li>onBindViewHolder<em> </em>method takes individual item position and holder as parameters and every visible item is filled with correct values.</li><li><em>getItemCount </em>method returns the size of the input array</li></ul><p>Every time when the user scrolls a recycler view, <em>onBindViewHolder </em>is called with the visible position and fills the layout accordingly.</p><h4>ViewHolder</h4><p>ViewHolder is a helper class for drawing the UI for individual items in the list.<br>It extends <em>RecyclerView.ViewHolder </em>class. All the UI bindings happen in this class.</p><h4>LayoutManager</h4><p>A <em>LayoutManager</em> is responsible for measuring and positioning item views within a <em>RecyclerView</em> as well as determining the policy for when to recycle item views that are no longer visible to the user.</p><p>Generally, LinearLayoutManger is used as LayoutManager for RecyclerView. We can determine the horizontal/vertical scrolling by assigning the specific LinearLayoutManager constants like LinearLayoutManager.HORIZONTAL ,LinearLayoutManager.VERTICAL , etc.</p><h3>How it works internally?</h3><p>As from the name “RecyclerView”, we know that this view recycles the views attached to it. But how does the recycling of views work? Let’s see.</p><p>Let’s say we have a list of 50 objects which are needed to be populated through RecyclerView. We will be giving all the 50 objects to the Adapter and it prepares the view based on the object. But, we can see only 5 cards at one time from a normal screen device.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/392/1*sATTGbP7UNL4RoQntJY3Uw.png" /></figure><p>Here, I<strong>tem-1</strong> to<strong> Item-5</strong> are the ones that are visible on the screen. Item 6is the one that will be loaded next on the screen when we scroll up.</p><p>All the items here have their own instance of ViewHolder and the ViewHolder here is helpful for caching the specific item’s view.</p><p>So, how recycling works here?</p><ul><li><strong>Item 1</strong> to <strong>Item 5</strong> are initially loaded on the screen and <strong>Item 6</strong> is which needs to be visible when the user scrolls up which is called as <strong>Waiting view</strong>.</li><li>When the user scrolls up <strong>Item 6 </strong>is visible and <strong>Item 1</strong> goes under the top of the screen, disappears and flushes out. <strong>Item 1</strong> is now called <strong>Dirty View</strong>. <br>These steps are executed simultaneously.</li><li>When the user again scrolls down <strong>Item 6</strong> gets out of visibility and flushes out and <strong>Item 1 </strong>is loaded gets onto the screen.</li></ul><p>This happens on every scroll by the user and the view visibility changes based on the currently visible items on the screen.</p><blockquote><em>ScrapView is the view in RecyclerView which was once visible and now is not visible on the phone’s screen to the user.</em></blockquote><blockquote><em>The views which we take from scrap view collection and then after re-bound happens by the recyclerView adapter before it is drawn to the screen are called dirty views.</em></blockquote><h3>Reuse issues with RecyclerView</h3><p>There will be few reuse issue when we are dealing with RecyclerView as it reuses the other view. So, make sure that we need to clean the views on <em>onBindViewHolder </em>method.</p><p><strong>Example:</strong> Let’s take a ImageView which we need to load an image from URL using <a href="https://github.com/bumptech/glide">Glide</a>. As Glide is a image loading and caching library. <br>When same ImageView is used by two or three elements, previously loaded image is populated(due to caching) on the newly loaded ImageView. This raises an reuse issue.</p><p>To avoid this set ImageView to null or set any default image in onBindViewHolder method and then populate the image from URL once it is ready.</p><h3><strong>Conclusion</strong></h3><p>RecyclerView got improved using ViewHolder and recycling of views. We can have multiple ViewHolders for the same RecyclerView. We can specify the respective ViewHolder based on the element type.</p><h3>References</h3><ul><li><a href="https://blog.mindorks.com/how-does-recyclerview-work-internally">https://blog.mindorks.com/how-does-recyclerview-work-internally</a></li><li>Image- <a href="https://www.raywenderlich.com/">https://www.raywenderlich.com/</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2a1fa60399a3" width="1" height="1" alt=""><hr><p><a href="https://medium.com/tilicholabs/what-is-a-recyclerview-and-how-it-works-internally-2a1fa60399a3">What is a RecyclerView and How it works internally?</a> was originally published in <a href="https://medium.com/tilicholabs">Tilicho Labs</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Backend Server Hosting Services [Part-1]]]></title>
            <link>https://medium.com/tilicholabs/backend-server-hosting-services-part-1-47bebccf289f?source=rss----3cc8c50e778b---4</link>
            <guid isPermaLink="false">https://medium.com/p/47bebccf289f</guid>
            <category><![CDATA[backend]]></category>
            <category><![CDATA[firebase]]></category>
            <category><![CDATA[heroku]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[netlify]]></category>
            <dc:creator><![CDATA[Ramesh Vantaku]]></dc:creator>
            <pubDate>Fri, 18 Feb 2022 03:31:10 GMT</pubDate>
            <atom:updated>2022-02-18T03:31:09.837Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qEayzTpETWxE3pJqjfvaqg.png" /></figure><p>Many people are afraid of publishing their site, they don’t know where to publish it, and how to.</p><p>Here are a few free hosting services you should consider 🎉</p><h3><strong>Firebase</strong></h3><p>Firebase Hosting provides fast and secure hosting for your web app, static and dynamic content, and micro services.Firebase is a PaaS (Platform as a Service) Google service. It also allows you to host static websites for free. Firebase is very easy to use and provides a CLI to manage yours apps . They also support hosting cloud functions.</p><ul><li><strong>Realtime Database</strong>: Term real time is little confusing but indeed Firebase is very different from normal databases. There are two main differences. First is the way it stores data and another is the way we access it. In normal database when data at backend get updated we need to refresh our browser or android app in order to get updated data, on other hand in firebase we don’t even need to refresh the page. Changes done from any other client browser will reflected to all connected clients without making any explicit server side call.</li><li><strong>JSON support</strong>: database is <strong>a type of non-relational database</strong> that is designed to store and query data as JSON documents, rather than normalizing data across multiple tables, each with a unique and fixed structure.</li><li><strong>Google support</strong>: <a href="https://firebase.google.com/support">Google Support</a> is a useful documentation before we implement any feature in Firebase.</li><li><strong>Real-time synchronization</strong>: Real Time Synchronization will monitor folders for changes and copy new or modified files with a very short delay after the change has occurred. Real Time Synchronization can be very convenient and speeds up the synchronization process considerably. However, it will only copy new and modified files and it may not be appropriate in all situations.</li><li><strong>Rapid prototyping</strong>: Rapid Prototyping is an approach to software development that emphasizes quick, iterative development cycles and minimal feature sets. The goal in rapid prototyping is not to develop a product. The goal is to, as quickly as possible, build something that utilizes a technology or platform to the point that you can understand the strengths and weaknesses of that technology or platform.</li><li><strong>Highly secured</strong>: It’s the development team’s responsibility to correctly secure the database prior to it storing real data. In Google Firebase, this is done by requiring authentication and implementing rule-based authorization for each database table.</li><li><strong>Automatic scaling</strong>: Firebase scales <strong>up automatically</strong>, with no downtime. This scaling mechanism lets Firebase serve thousands of requests per second and millions of concurrent connections. You pay only for your actual usage based on storage size and the number of operations</li><li><strong>Firebase hosting</strong>: Firebase Hosting is production-grade web content hosting for developers. With a single command, you can quickly deploy web apps and serve both static and dynamic content to a global CDN (content delivery network). You can also <a href="https://firebase.google.com/docs/hosting/serverless-overview">pair Firebase Hosting with Cloud Functions or Cloud Run</a> to build and host microservices on Firebase</li><li>Easy and simple operation process</li></ul><p>Link: <a href="https://firebase.google.com/docs/hosting">https://firebase.google.com/docs/hosting</a>.</p><blockquote><strong><em>Note</em></strong>: I’m only going over the other services below with bird’s eye view keeping the length of blog post in mind. Please check my space for more updates which discuss each service at length.</blockquote><h3><strong>AWS</strong></h3><p>AWS Amplify Hosting is a fully managed CI/CD and hosting service for fast, secure, and reliable static and server-side rendered apps that scale with your business. Supports modern web frameworks such as React, Angular, Vue, Next.js, Gatsby, Hugo, Jekyll, and more.</p><ul><li>Highly secured</li><li>Perfectly adaptable</li><li>Comprehensive documentation</li><li>Improvised productivity factor</li><li>Economical pricing structure</li><li>Totally innovative solutions</li></ul><h3><strong>InfinityFree</strong></h3><p>Free Unlimited Web Hosting for Both frontend and backend<br>Completely free website hosting with unlimited disk space and bandwidth. Its very good option to free hosting but some limitations like <strong>50,000 hits in a day </strong>and<strong> Limited CPU.</strong></p><ul><li>99.9% uptime</li><li>Free subdomain</li><li>Totally free web hosting.</li><li>Free SSL</li><li>Unlimited storage</li></ul><p>Link: <a href="https://infinityfree.net/">https://infinityfree.net</a></p><h3><strong>Netlify</strong></h3><p>Netlify is everything you need to build fast, modern websites: continuous deployment, serverless functions, and so much more. But like the definition says, Netlify offers you cloud hosting services as well as present you with the ability to handle backend operations with its serverless backend service.</p><ul><li>Built-in CI/CD</li><li>Domains &amp; DNS management</li><li>Automated previews of every commit</li><li>Automated builds from Git</li><li>Deploy to global Edge network</li><li>Site previews for every push</li><li>Instant rollbacks to any version</li><li>Deploy static assets &amp; dynamic serverless functions</li></ul><p>Link : <a href="http://netlify.com/">http://netlify.com</a></p><h3><strong>Hostman</strong></h3><p>Hostman is a very good platform for deploying your apps from gitHub. Its free upto 10 websites. Hostman is a cloud application platform for developers and startups. Build and run web apps and websites without managing servers and not spending days on setups or hiring a whole engineering team. This is Static websites only, you need to pay for dynamic sites.</p><p>Auto-deploy for any repository</p><ul><li>Built-in CI/CD</li><li>SSL-first cloud platform</li><li>7 days trial, 3 static sites forever free</li></ul><p>Link: <a href="https://hostman.com/">https://hostman.com</a></p><h3><strong>Heroku</strong></h3><p>Heroku allows you to deploy quickly, forget about the infrastructure, and just focus on improving your app. Heroku is also <strong>great for beginners</strong> since its free tier of service covers everything newbies need. Heroku is <strong>a container-based cloud Platform as a Service (PaaS)</strong>. Developers use Heroku to deploy, manage, and scale modern apps. Heroku is fully managed, giving developers the freedom to focus on their core product without the distraction of maintaining servers, hardware, or infrastructure.</p><ul><li>Easy to deploy</li><li>Simple and fast processing saves a lot of time</li><li>Free for side projects</li><li>The scaling process is simple</li><li>Minimal skill sets required for developers</li><li>Setup and installation is simple</li><li>Add-ons available</li><li>Perfect for startups</li><li>Minimal learning curve</li><li>Easy and simple integration</li><li>Excellent User Interface</li><li>Detailed documentation</li><li>Postgres hosting</li><li>Adding collaborators is simple and easy</li><li>The rollback process is simple</li><li>GitHub integration</li><li>MySQL integration</li></ul><p>Please watch this space in future for more elaborate explanations of the services mentioned above.</p><p>Thank you for reading !</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=47bebccf289f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/tilicholabs/backend-server-hosting-services-part-1-47bebccf289f">Backend Server Hosting Services [Part-1]</a> was originally published in <a href="https://medium.com/tilicholabs">Tilicho Labs</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What makes Hermes engine (React Native) fast?]]></title>
            <link>https://medium.com/tilicholabs/what-makes-hermes-engine-react-native-fast-ac6fa5e3ad2e?source=rss----3cc8c50e778b---4</link>
            <guid isPermaLink="false">https://medium.com/p/ac6fa5e3ad2e</guid>
            <category><![CDATA[hermes]]></category>
            <category><![CDATA[react-native]]></category>
            <dc:creator><![CDATA[Nagasai Kollipara]]></dc:creator>
            <pubDate>Fri, 18 Feb 2022 03:31:10 GMT</pubDate>
            <atom:updated>2022-02-19T13:57:07.943Z</atom:updated>
            <content:encoded><![CDATA[<h3>Brief about Hermes</h3><p>Hermes is a new javascript engine optimised for react-native — introduced in 2020 by Facebook.</p><p>Historically, React Native was using <strong>JavaScriptCore</strong> (JS engine) as default for running Javascript code.</p><blockquote>In near future, we will see Hermes as the default JS engine for react-native.</blockquote><p>If you have already heard about Hermes — it speeds up app launch, reduces app size, and many more. In this blog, we will see how Hermes achieves all of the above and some of the other interesting features it provides.</p><p>Before we delve into the actual mechanism, we have to be familiar with the few basic terms.</p><h3>Basic terms</h3><ol><li><strong>Babel</strong>: Babel is a free and open-source JavaScript trans-compiler. React Native uses Babel to <strong>convert React syntax</strong> and the newer ES5+ syntax into code, that can be run in a JavaScript environment that doesn’t support those features. This step is called <strong>transpilation</strong>.</li><li><strong>Minification</strong>: In addition to above, for production, the React Native server reduces the size of your JavaScript file by removing unnecessary whitespace, shortening variable names, removing unused code, and performing other optimizations.</li><li><strong>Parse</strong>: Converts the source code into compilers known code. eg: Javascript is function-oriented, but it will also support classes, in the background classes are converted into functions</li><li><strong>Compile</strong> Converts JS code into byte-code.</li><li><strong>Execute</strong>: Executing the byte-code, means</li><li><strong>Build time: </strong>also called compiled time, it converts source code into executable code, which is byte code.</li><li><strong>Run time: </strong>Executes the code.</li></ol><h3>Mechanism without and with Hermes</h3><h4>Without Hermes</h4><p>The build time process has only Babel and Minify steps, and Runtime has Parse, compile and execution.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4TplIZXksZCK3pgPN2Gh5w.png" /><figcaption>Without Hermes</figcaption></figure><h4>With Hermes</h4><p>The only Execution process was there in the Run-time process, remaining all were brought to build time.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UqTvTjhwcirmjH0zyfZBMA.png" /><figcaption>With Hermes</figcaption></figure><p>In summary, Hermes will send a precompiled optimised byte code instead of plain javascript source so it reduces startup time, decrease TTI by nearly half, and does much more!</p><p>In addition, Hermes will also well manage Garbage collection<br> — A regular JS engine has “Stop the world” to perform Garbage collection</p><p>Generally, it uses <a href="http://google.com/"><strong>GenGC</strong></a>. Generational Garbage collector, was the previous default GC for Hermes and single-threaded, having long GC pauses because it works in the Main JS thread. Some observations from Facebook, it has a pause of 200ms average or 1.4sec at P99, some times 7sec. The old generation uses a <a href="http://google.com/">mark-compact strategy</a>. The new generation uses a typical <a href="http://google.com/">semi-space copying strategy</a> to make it good at aggressively returning memory to OS.</p><p>To Overcome these shortcomings in GenGC, they implemented Concurrent GC named <a href="http://google.com/">Hades</a>.</p><p>To Overcome these shortcomings in GenGC, they implemented Concurrent GC named <a href="http://google.com/">Hades</a>.</p><p><a href="http://google.com/"><strong>Hades GC</strong></a><strong> — </strong>it is default Hermes GC, is to overcome problems in GenGC. It works in the background thread concurrently with the interpreter running JS code. Its main principle is to achieve those low pause times. It uses the Mark-Sweep Collector strategy.</p><p>You can check which Garbage collector is enabled — <strong>HermesInternal.getRuntimeProperties().GC</strong></p><p>Incase you don’t have this, No problem use following snippet to get Hades</p><ul><li><strong>-DHERMESVM_GCKIND = HADES </strong>to request <strong>Hades</strong></li><li>And<strong> NONCONTIG_GENERATIONAL</strong> to request <strong>GenGC</strong></li></ul><p>These are one of the main reasons to achieve benefits with Hermes. Also there are many other improvements in Hermes, we try to add them early</p><h3><strong>Enable Hermes in your React Native app</strong></h3><blockquote>Official documentation is available at: <a href="https://reactnative.dev/docs/hermes"><em>https://reactnative.dev/docs/hermes</em></a></blockquote><h4>Android</h4><p>Edit your android/app/build.gradle file and make the change illustrated below:</p><pre>project.ext.react = [<br> entryFile: &quot;index.js&quot;,<br>- enableHermes: false // clean and rebuild if changing<br>+ enableHermes: true // clean and rebuild if changing<br> ]</pre><p>Also, if you’re using ProGuard, you will need to add these rules in proguard-rules.pro</p><pre>-keep class com.facebook.hermes.unicode.** { *; }<br>-keep class com.facebook.jni.** { *; }</pre><p>Next, if you’ve already built your app at least once, clean the build:</p><pre>$ cd android &amp;&amp; ./gradlew clean</pre><p>That’s it! You should now be able to develop and deploy your app as usual:</p><pre>$ npx react-native run-android</pre><h4>iOS</h4><p>Since React Native 0.64, Hermes also runs on iOS. To enable Hermes for iOS, edit your ios/Podfile file and make the change illustrated below:</p><pre>use_react_native!(<br>     :path =&gt; config[:reactNativePath],<br>     # to enable hermes on iOS, change `false` to `true` and then install pods<br>-    :hermes_enabled =&gt; false<br>+    :hermes_enabled =&gt; true<br>   )</pre><p>Next, install the Hermes pods:</p><pre>$ cd ios &amp;&amp; pod install</pre><p>That’s it! You should now be able to develop and deploy your app as usual:</p><pre>$ npx react-native run-ios</pre><h4>Facing issues while setting up Hermes?</h4><p>Refer to this url: <a href="https://github.com/facebook/hermes/issues">https://github.com/facebook/hermes/issues</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ac6fa5e3ad2e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/tilicholabs/what-makes-hermes-engine-react-native-fast-ac6fa5e3ad2e">What makes Hermes engine (React Native) fast?</a> was originally published in <a href="https://medium.com/tilicholabs">Tilicho Labs</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Basics of Software Testing & STLC [Part-1]]]></title>
            <link>https://medium.com/tilicholabs/basics-of-software-testing-stlc-part-1-63771ce2bd9d?source=rss----3cc8c50e778b---4</link>
            <guid isPermaLink="false">https://medium.com/p/63771ce2bd9d</guid>
            <category><![CDATA[software-testing]]></category>
            <category><![CDATA[stlc]]></category>
            <category><![CDATA[qa]]></category>
            <category><![CDATA[qa-testing]]></category>
            <dc:creator><![CDATA[Praveen Mekala]]></dc:creator>
            <pubDate>Fri, 18 Feb 2022 03:31:10 GMT</pubDate>
            <atom:updated>2022-02-18T03:31:09.492Z</atom:updated>
            <content:encoded><![CDATA[<h4>All you need to know about software testing and Software Testing Life Cycle</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/832/1*1qIwX1uxUqp_rsrrqq-H4Q.jpeg" /></figure><p>In this post, I’m going to cover some software testing basics that you need to know. Here are some of the topics you’ll read about:</p><ul><li>Software testing definition</li><li>The importance of software testing</li><li>The types of software testing</li><li>What is STLC?</li></ul><p>Software testing is the process of verifying and validating the functionality of an application to find whether it satisfies the requirements or not.</p><p>OR</p><p>It’s the process of finding the defect in an application by making sure that the developed application meets the end-user requirement</p><h3>Why testing?</h3><p>Testing is important because software bugs could be expensive or even dangerous. The goal of software testing is to find errors, gaps, or missing requirements in comparison to the actual requirements.</p><p>A properly tested software product ensures dependability, security, and high performance, which leads to time savings, cost-effectiveness, and customer satisfaction.</p><h3>Why software testing is vital to good software development?</h3><h4><strong>Enhances product quality</strong></h4><p>Any business can bring value to their customers is only when the product is ideal. Businesses have to make sure that users don&#39;t face any issues while using their product, this can be achieved by making the product bug-free.</p><h4><strong>Improves/establishes cost-effectiveness</strong></h4><p>Testing our project on time can save money in the long run. Software development consists of many stages and if bugs are caught in the earlier stage it costs much less to fix them.</p><h4><strong>Improves application security</strong></h4><p>While using an application customer is bound to reveal some personal information, so to prevent any sought of hacking of the application security testing is just before the software is released. This can make customers feel safe while using the application.</p><p>For instance, banking applications or e-commerce stores need payment information. If the developers don’t fix security-related bugs, it can cause massive financial loss.</p><p>The other part of security is not losing your data. It’s common today for people to store data in cloud storage. You also probably have your photos and files stored on iCloud or Google drive. So the security of a product not only protects information from hackers but also makes sure it’s not lost or gets corrupted.</p><h4><strong>Improves customer satisfaction</strong></h4><p>The ultimate goal for a product owner is to give the best customer satisfaction. Software should be tested in order to bring the best user experience possible.</p><h4><strong>Fixes/establishes compatibility with different devices and platforms</strong></h4><p>For example, An organization has developed an application and the tester must check whether the application runs on different devices and platforms.</p><p>And sometimes an application that works fine on one browser doesn’t work on another. So there is a need for testing in multiple browsers.</p><h3>Types of Testing</h3><h4><strong>Manual Testing</strong></h4><p>It’s a process in which the tester compares the developed code against the requirements manually.</p><h4><strong>Automation Testing</strong></h4><p>It’s a process in which the tester compares the developed code against the requirements by writing test scripts and executing them.</p><h4><strong>White-box Testing</strong></h4><p>This testing is mostly done by developers. In this, the developers test the code by writing unit tests. This type of testing is done when the internal structure of the software is known.</p><p><strong>Black box testing: </strong>This testing is mostly done by testers. This testing is done without knowing the internal structure of the application.</p><p><strong>Module / Unit testing: </strong>In this testing, the whole application is divided into modules and then each and every module is tested individually.</p><p>Ex: Consider a banking application that has a login, check balance, transfer money, and logout functionalities. Now the whole app is divided into 4 modules login, check balance, transfer money, and logout modules, and each module is separately tested.</p><p><strong>Integration Testing: </strong>In this testing, the modules are integrated with one another and tested.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/452/0*u3lNSI2s77WwLWZj" /></figure><p><strong>Smoke testing: </strong>In this testing, the basic functionalities of the app are tested. This type of testing is done mostly on unstable builds or the initial builds.</p><p><strong>Sanity testing: </strong>In this testing, the new functionalities and bug fixes of the app are tested. This type of testing is done mostly on stable builds.</p><p><strong>Regression testing: </strong>This type of testing is done to make sure that the old functionality of the app is not affected due to new implementations in the application.</p><p><strong>System testing: </strong>This testing is also known as end-to-end testing, in this whole app is treated as a single entity and all the test cases are executed.</p><h3>Software Testing Life Cycle (STLC)</h3><p>This is a sequence of different activities performed during the software testing process.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*3TseV88t3dXblm5o.png" /></figure><h3><strong>Requirement Analysis</strong></h3><h4><strong>What is a requirement?</strong></h4><p>The requirement is a thing or flow which is needed by the client.</p><h4><strong>What is a requirement analysis?</strong></h4><p>It’s the process of gathering the requirements by reading or listening. This is a very important phase in testing. In this phase quality assurance team understands the requirements like what is to be tested.</p><p><strong>Entry Criteria:</strong> You must have the requirements from the client to start requirement analysis.</p><p><strong>Exit Criteria:</strong> A document of understanding is prepared and get confirmed by the client.</p><h3><strong>Test Planning</strong></h3><p>Following tasks are performed in this stage</p><ul><li>Confirm the scope of the testing phase</li><li>Conduct review of requirements with the Business, Design team.</li><li>Identify resource requirements including any training.</li><li>Identify test environments to support the test phase.</li><li>Create a Test plan/approach.</li></ul><p><strong>Entry Criteria:</strong> Document of Understanding is prepared and confirmed by the client.</p><p><strong>Exit Criteria:</strong> A Test Plan document is prepared and approved by the project manager.</p><h3><strong>Test Cases Development &amp; Environment Setup</strong></h3><p>The test case development phase gets started once the test planning phase is completed. In this phase testing team note down the detailed test cases. The testing team also prepares the required test data for the testing. When the test cases are prepared then they are reviewed by the quality assurance team.</p><p>Basically, the test environment decides the conditions on which software is tested. This is independent activity and can be started along with test case development. In this process, the testing team is not involved. either the developer or the customer creates the testing environment.</p><p><strong>Entry Criteria:</strong> A Test Plan document is prepared and approved by the Project Manager.</p><p><strong>Exit Criteria:</strong> The environments setup is done and the written test cases are approved by the Test Manager.</p><h3><strong>Test Execution</strong></h3><p>In this phase testing team start executing test cases based on prepared test cases in the earlier step.</p><p><strong>Entry Criteria:</strong> The environments setup is done and the written test cases are approved by the Test Manager.</p><p><strong>Exit Criteria:</strong> All the test cases are executed in the Testing environment and bugs are tracked.</p><h3><strong>Test Closure</strong></h3><p>This is the last stage of STLC in which the process of testing is closed by submitting a closure report that gives a summary of all the tests conducted during the testing process. It also gives a detailed analysis of the bugs removed and errors found.</p><p><strong>Entry Criteria:</strong> All types of testing are done and test metric’s are ready</p><p><strong>Exit Criteria:</strong> Test closure report is prepared and is shared with other stakeholders in the project.</p><h3>Where to go from here?</h3><p>In the subsequent blog posts, let’s see how all this looks in reality with a practical/live example.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=63771ce2bd9d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/tilicholabs/basics-of-software-testing-stlc-part-1-63771ce2bd9d">Basics of Software Testing &amp; STLC [Part-1]</a> was originally published in <a href="https://medium.com/tilicholabs">Tilicho Labs</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>