<?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 Ana Cupic on Medium]]></title>
        <description><![CDATA[Stories by Ana Cupic on Medium]]></description>
        <link>https://medium.com/@ana.cupic?source=rss-d60a6a454494------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*bXNHKBYQuCRGpEEc.jpg</url>
            <title>Stories by Ana Cupic on Medium</title>
            <link>https://medium.com/@ana.cupic?source=rss-d60a6a454494------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 02:42:51 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@ana.cupic/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[When you think about exploratory testing, do you imagine a tester clicking through the app or a…]]></title>
            <link>https://medium.com/q-software/when-you-think-about-exploratory-testing-do-you-imagine-a-tester-clicking-through-the-app-or-a-ba36baaf7f6?source=rss-d60a6a454494------2</link>
            <guid isPermaLink="false">https://medium.com/p/ba36baaf7f6</guid>
            <category><![CDATA[exploratory-testing]]></category>
            <dc:creator><![CDATA[Ana Cupic]]></dc:creator>
            <pubDate>Fri, 01 Jul 2022 12:34:09 GMT</pubDate>
            <atom:updated>2022-07-01T12:34:09.340Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*La4Wl1ondX4CD0Qsp3aetA.jpeg" /></figure><p>When you think about exploratory testing, do you imagine a tester clicking through the app or a tester analyzing requirements? I bet the answer is a tester clicking through the app!</p><p>Both answers are correct, but in this blog post, you’ll read more about exploratory testing in requirement analysis. Don’t worry if you’re not a tester, <em>anyone</em> included in the requirement analysis will benefit from this blog.</p><p>Requirements can be explored in a requirement discussion or later when requirements are already defined and written. Exploring requirements is actually a ‘thinking’ activity. In this blog, you’ll learn <em>how</em> to explore requirements and <em>why</em> it’s important.</p><h3>But first — what is exploratory testing?</h3><p>This question deserves (at least) its own blog post! However, take a look at this simple example to understand what exploratory testing is. Let’s say that you are looking into a requirement like this: ‘As a user, I want to be able to log in with my username and password.’</p><p>If you enter your credentials in a username and password field and click on the Login button, you are not exploring. But, if you click on the Login button without entering credentials, you are exploring. Furthermore, you can check what happens when you click multiple times on the Login button after entering valid credentials or observe what happens when you enter an invalid email or password.</p><p>In short, <em>everything</em> you test that is not specified in the requirements or test cases can be considered exploratory testing. If you want to know more about exploratory testing, I recommend an excellent book that describes exploratory testing in detail — <a href="https://www.goodreads.com/book/show/15980494-explore-it">Explore it! by Elisabeth Hendrickson</a>. This book offers great examples and tips for exploratory testing. And how does exploratory testing fit into the requirement analysis? Let’s find out!</p><h3>Exploring requirements during requirement discussion</h3><p>I would say that this is the perfect start for testing. Well yeah, you don’t have a product you can test, but you can save a lot of time (and nerves) if your testing starts here.</p><p>During the requirement discussion, the main focus is to define what a system should do. First, so-called <em>happy paths</em> are discussed. After defining and understanding what those happy paths are, other scenarios should be discussed — and that is the moment where exploratory testing should start.</p><h3>What can go wrong?</h3><p>Each happy path is likely to have scenarios that can go wrong. Let’s stick to the mentioned login example — what will happen if the user enters invalid credentials? If there are no warning messages saying that the username or password is incorrect, the user can be confused. Raise a question about scenarios that could go wrong following the defined happy paths.</p><h3>What should always work?</h3><p>This is a happy-path question, but it’ll help you understand where to put a great effort into breaking that thing. Ask stakeholders to define the most important use case(s). For example, imagine that your team is building a webshop and you’re discussing a payment flow in a webshop — one of the most important use cases is to always show correct prices and a correct total price.</p><p>You can discuss with stakeholders anything you think will affect the correct prices (reducing the number of the same products in the chart, removing products, discounts, promotion codes)</p><h3>What should never happen?</h3><p>Discuss with stakeholders what should <em>never</em> happen. For example, products from the wishlist should never disappear. Try to cover scenarios in which products may disappear from the wishlist and how to handle those scenarios.</p><p>One of those scenarios is that the product is out of stock. The end-user wants to see all products he ever saved on the wishlist, although the product is out of stock. The product can be grayed out, or the ‘out of stock’ warning may appear under the product, but the product should remain on the wishlist, and the user should be informed that the product is out of stock.</p><h3>Are there any variables affecting other functionalities?</h3><p>This question is very important because it helps prevent defects in <em>multiple functionalities</em>. Let’s continue with the webshop example — one of the requirements is ‘As a seller, I want to be able to remove my products’. Now think about what functionalities depend on products:</p><ul><li>chart — should the product be removed from the chart? Do I need to notify a buyer about the removed product? Should the product be disabled and greyed out or completely removed?</li><li>product list — when the seller removes his product, can the buyer see his product in the product list?</li><li>search — can the buyer find the removed product by search option?</li><li>filter — can the buyer find the removed product by filter option?</li><li>payment — what should happen if the seller removes the product at the moment when the buyer is paying for the product?</li><li>bought items — if the buyer bought the product before the product was removed, can the buyer still see the product in his bought items list after the product is removed?</li></ul><p>Once you start doing exploratory testing in the requirement analysis following these questions, you’ll reduce many discussions that occur during the development — doesn’t it sound perfect?</p><h3>Exploratory testing in defined requirements</h3><p>I’m sure that you already know that any defined and written requirement can be changed. So don’t take for granted defined requirements, <em>analyze</em> them and raise your concerns.</p><p>When you understand what the requirements ask for, you can analyze them with the questions mentioned above:</p><ul><li>What can go wrong?</li><li>What should always work?</li><li>What should never happen?</li><li>Are there any variables affecting other functionalities?</li></ul><p>And questions not mentioned above:</p><ul><li>Does the end-user need the functionality as described?</li><li>Is it going to be too complicated for the end-user?</li><li>Are there any scenarios that are not described within the requirements?</li></ul><p>As in the previous examples, these questions will lead you to other questions. And sometimes, defined requirements won’t give you answers.</p><p>However, stakeholders will. You can <em>forward</em> your questions or concerns to a business analyst, project manager, project owner, or your clients — this depends on the organization within the project you work on. Just make sure to contact a person <em>responsible</em> for defining business logic and/or requirements.</p><p>If you have any suggestions on how to handle your questions, don’t hesitate to raise them with your questions — moreover, it’ll help stakeholders to make a decision, and your <em>previous experience</em> will probably generate some great ideas.</p><h3>Benefits of Exploratory testing in requirement analysis</h3><p>Exploratory testing in the requirement analysis doesn’t make sense if there are no <em>benefits</em> to it, right? Great benefits can be brought to both product quality and teamwork.</p><p>Let’s start with some benefits of exploratory testing during requirement discussion, where questions are raised before development starts:</p><ul><li>The time for discussing requirements is saved — you’re already brainstorming and discussing requirements with stakeholders so it’s faster and easier to discuss any new questions at this moment than discussing them later and waiting for answers</li><li>Preventing bugs — while exploring requirements, you’ll detect questions and scenarios that probably wouldn’t be detected without exploring requirements, which means that potential bugs are prevented</li><li>Reducing the number of change requests — anything discussed in the requirement discussion will not be discussed later, causing change requests. But not just that, it’ll save unnecessary work that could be made in the development</li><li>Better planning — clear requirements that cover most of the scenarios lead to more accurate estimation and prioritization, which leads to better planning</li><li>Better communication — anything discussed in the early phase will prevent misunderstandings between the client and the team or between team members</li><li>The time is saved — everything stated 1–5 is saving the time: time is not spent to discuss requirements again or to discuss change requests or misunderstandings, unnecessary work is avoided, the work is better planned</li><li>The money is saved — time is money. Now read everything 1–6 again</li></ul><p>If requirements are already defined, your team still can benefit from exploring them:</p><ul><li>Better Quality — discussing missed scenarios or something that can be done better than it is, and implementing it, provides better product quality</li><li>Better UX — end-users probably won’t praise your dedication and great work, but be sure that you will prevent user complaints caused by poor user experience. Besides that, satisfied users are likely to bring to your product more users and to continue to use your product</li><li>More satisfied clients — clients will recognize team dedication to deliver a high-quality product, and they will appreciate it</li></ul><h3>Conclusion</h3><p>Although exploratory testing is about simultaneously learning, designing, and executing tests, exploratory testing can be done in requirement analysis. You need to think outside the box and let your results bring great benefits!</p><p>Blog written by Jelena Scevic.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ba36baaf7f6" width="1" height="1" alt=""><hr><p><a href="https://medium.com/q-software/when-you-think-about-exploratory-testing-do-you-imagine-a-tester-clicking-through-the-app-or-a-ba36baaf7f6">When you think about exploratory testing, do you imagine a tester clicking through the app or a…</a> was originally published in <a href="https://medium.com/q-software">Q agency</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Flutter Chat — Proof of Concept]]></title>
            <link>https://medium.com/q-software/flutter-chat-proof-of-concept-c696637427dd?source=rss-d60a6a454494------2</link>
            <guid isPermaLink="false">https://medium.com/p/c696637427dd</guid>
            <category><![CDATA[flutter-for-beginner]]></category>
            <category><![CDATA[flutter-widget]]></category>
            <category><![CDATA[flutter-app-development]]></category>
            <category><![CDATA[flutter]]></category>
            <category><![CDATA[flutter-ui]]></category>
            <dc:creator><![CDATA[Ana Cupic]]></dc:creator>
            <pubDate>Mon, 28 Feb 2022 17:43:29 GMT</pubDate>
            <atom:updated>2022-02-28T18:13:29.398Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*INtKXPjkGqsQnHV36oIp6w.png" /></figure><h3>Flutter Chat — Proof of Concept</h3><p>Clients often can’t understand why it takes so much time to implement things that exist in almost every application? If it’s in every app, then it must be easy?</p><p>In Flutter, you are trying to accelerate development by using one of the offered packages in the <strong>pub.dev official </strong>package repository.</p><p>The first step is to choose a package that would be suitable for implementation. The choice of the <strong>package</strong> depends on the features that the package has.</p><p>For example, customization of UI, prebuilt components that manage most operations like data fetching, pagination, sending a message, image and file upload, and more. Finally, I will analyze the most popular chat UI package, flutter_chat_ui.</p><h3>Flutter Chat UI — Flyer Chat</h3><p><a href="https://docs.flyer.chat/flutter/chat-ui/">Flyer Chat</a> is a platform for creating in-app chat experiences using <strong>Flutter</strong>. For installation add flutter_chat_ui to your package’s pubspec.yaml.</p><h3>Usage</h3><p>You start with a <strong>Chat widget</strong> that will render a chat. In my example Chat widget is rendered like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/786/1*zlRh65hG4tDTvQI6yq8ioA.png" /></figure><p>It has 3 required properties:</p><ul><li>messages — an array of messages to be rendered</li><li>onSendPressed — a function that will have a partial text message as a parameter</li><li>user — a User class</li></ul><p><a href="https://gitlab.com/-/snippets/2210134">chat_widget ($2210134) · Snippets · Snippets</a></p><h3>Other properties</h3><ul><li>bubbleBuilder — Customize the default bubble using this function</li></ul><p><a href="https://gitlab.com/-/snippets/2210131">bubble_builder ($2210131) · Snippets · Snippets</a></p><ul><li>customBottomWidget — [Widget] Allows you to replace the default Input widget</li><li>customDateHeaderText — [String] If [dateFormat], [dateLocale] and/or [timeFormat] is not enough to customize date headers in your case, use this to return an arbitrary string based on a [DateTime] of a particular message</li><li>customMessageBuilder — Build a custom message inside the predefined bubble</li><li>dateFormat — This allows you to customize the date format</li><li>dateHeaderThreshold — Time (in ms) between two messages while rendering a date header</li><li>dateLocale — Locale will be passed to the `Intl` package</li><li>disableImageGallery — Disable automatic image preview on tap</li><li>emojiEnlargementBehavior — Controls the enlargement behavior of the emojis in the TextMessage</li><li>emptyState — [Widget] Allows you to change what the user sees when there are no messages</li><li>fileMessageBuilder — Build a file message inside predefined bubble</li><li>groupMessagesThreshold — [int] Time (in ms) between two messages while visually grouping them</li><li>hideBackgroundOnEmojiMessages — [bool] Hide background for messages containing only emojis</li><li>imageMessageBuilder — [Widget] Build an image message inside predefined bubble</li><li>isAttachmentUploading — [bool] Whether attachment is uploading. Will replace attachment button with a [CircularProgressIndicator]</li><li>isLastPage — [bool] Used for pagination (infinite scroll) together with [onEndReached]. When true, it indicates that there are no more pages to load, and pagination will not be triggered</li><li>l10n — [ChatL10n] Localized copy</li><li>onAttachmentPressed — [Function()] Callback for attachment button tap event</li><li>onBackgroundTap — [Function()] Called when user taps on background</li><li>onEndReached — [Function()] Used for pagination (infinite scroll). Called when user scrolls to the very end of the list</li><li>onEndReachedThreshold — [double] Used for pagination (infinite scroll) together with [onEndReached]. It can be anything from 0 to 1, where 0 is the immediate load of the next page as soon as the scroll starts, and 1 is the load of the next page only if scrolled to the very end of the list. The default value is 0.75, e.g., start loading the next page when scrolled through about 3/4 of the available content</li><li>onMessageLongPress — [Function()] Called when user makes a long press on any message</li><li>onMessageTap — [Function()] Called when user taps on any message</li><li>onSendPressed — [Function()] Will be called on [SendButton] tap</li><li>onTextChanged — [Function()] Will be called whenever the text inside [TextField] changes</li><li>onTextFieldTap — [Function()] Will be called on [TextField] tap</li><li>sendButtonVisibilityMode — Controls the visibility behavior of the [SendButton] based on the [TextField] state inside the [Input] widget.</li></ul><h3>Upload media</h3><p>You can use the image picker package to select an image and send it as a message. For example:</p><p><a href="https://gitlab.com/-/snippets/2210129">handle_image_selection ($2210129) · Snippets · Snippets</a></p><p>Similar to the text message, you will need to create an image message using data from the image picker. In this example, you can use a local path just for demo purposes, but you will upload the image first for the backend service and then send the received URL using the uri property.</p><p>The image message renders in two different ways to keep the <strong>UI clean</strong>. First, if the aspect ratio is too low or too high, it renders like a file message, so you don’t see a narrow line on the UI.</p><p>The second way is a classic image in the chat. Give it a try. On tap, photos will be previewed inside an interactive image gallery. To disable the image gallery, pass disableImageGallery property to the <strong>Chat widget.</strong></p><h3>Files</h3><p>You can use the file_picker package to select a file and send it as a message.</p><p>Example:</p><p><a href="https://gitlab.com/-/snippets/2210136">handle_file_selection ($2210136) · Snippets · Snippets</a></p><p>Like the text message, you will need to create a file message using data from the document picker. In this example, uri will point to the local file system just for demo purposes, but you will upload the file first for the backend service and then send the received URL using the uri property.</p><h3>Opening file</h3><p>Right now, nothing will happen when a user taps on a file message, so I will need to add another dependency. I will use an open file package. Now, you can open a file:</p><p><a href="https://gitlab.com/-/snippets/2210245">handle_message_tap ($2210245) · Snippets · Snippets</a></p><h3>Link preview</h3><p>Link preview works automatically, and it can be disabled by setting <strong>usePreviewData </strong>to false. Usually, however, you’ll want to save the preview data so it stays the same. You can do that using <strong>onPreviewDataFetched</strong>.</p><h3>Q Chat App (Flyer Chat) with Firebase as backend</h3><p>Using the chat UI, I made a simple chat application using the Flutter chat UI package. The application uses firebase as the backend.</p><p>By registering the user, I can chat with other ones. I have a contacts dialog with a list of all contacts, and to start chatting, all I have to do is on the user.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mFB59FZ3Um2pg-AuMZ8PwQ.png" /></figure><p>In addition to messages, you can send pictures and files. I just have to pick what I will be sending, a photo or file.</p><h3>Flutter chat with custom backend</h3><p>All solutions for chats can be split into two categories:</p><p><strong>1. </strong>Ready-made chat platforms (SendBird, GetStream.io)</p><p>They have prepared functionality for main chat options. The developer needs to put a small effort and time into adding a chat into an app. But the behavior of functionality has strict borders by the platform creator, and possibilities for customization are limited.</p><p><strong>2.</strong> Technologies for exchanging data between client and server, such as Firebase Cloud Messaging, Socket.io.</p><p>They allow building a very flexible chat solution upon them. Those technologies take time to implement but offer unlimited possibilities for customization.</p><h3>Firebase</h3><p>For implementing Firebase only for the chat functionality and using your custom backend, you can register/login users using a custom JWT token and save the received uid to the users’ table. Then you can have a screen with all users from your user’s table where each of them will have an assigned uid that will be used to start a chat.</p><p>When you have access to that uid, create a room (channel) or group room and start chatting.</p><p><em>Advantages</em></p><p>Free for products with up to 100 simultaneous users. With comprehensive documentation and high popularity, developers can quickly find answers, which saves time and money. No need to buy an additional server. You can do everything on the Firebase server.</p><p><em>Disadvantages</em></p><p>The developer needs experience working with NoSQL to build a convenient and effective database structure.</p><p>Complex search inquiries still pose a bigger problem than those in SQL databases or <strong>NoSQL databases</strong> like <strong>MongoDB</strong>. Some are impossible, and others will take much more time to develop.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/704/1*14vW3QvzrDyTaVrWXZmXwA.png" /></figure><h3>Socket.IO</h3><p><strong><em>Advantages</em></strong></p><p>Server platform Node.js, going with the real-time data exchange library <strong>Socket.io</strong> helps build a chat with unlimited customization possibilities.</p><p>The developer has complete control over all components: interface, logic, and server data. An endpoint can be whatever is needed. In the future product, you will see many complex search inquiries, and you can choose the <strong>SQL database</strong> instead of using <strong>Firestore</strong>.</p><p>Client and server exchange messages directly, resulting in fast work. When you use <strong>Firebase Cloud Messaging</strong>, the message goes from your server to the Firebase server, and only from there will it travel further to the device.</p><p>It’s important to mention that if there is a 0,5s delay, it’s not critical for a text chat. But, again, open-source, free solution — you don’t have to pay monthly for this technology.</p><p><strong><em>Disadvantages</em></strong></p><p>The only disadvantage is that it requires more time and money, as the developer creates all functions from scratch.</p><p>Links: <a href="https://socket.io/">socket.io</a> <a href="https://pub.dev/packages/socket_io_client">packages</a></p><h3>Sendbird</h3><p><strong><em>Advantages</em></strong></p><p><strong>Sendbird</strong> is a ready-made chat platform. It offers many prepared features, including an indication of the number of unread messages, blocking users, and admin dashboard.</p><p>Many features are already realized and work right away: message or file exchange, invitations, users blocking, typing indication, editing messages, automatic translation, admin dashboard, group chats for up to 100 users.</p><p><strong><em>Disadvantages</em></strong></p><p>Chat and functionality behaviors are strictly set. A user logs in and gets access to a list of channels. They can choose an existing channel or create their own. Tracks are either public or private. Users can exchange messages in either one.</p><p>This is the standard structure for the majority of chats. If you need something more exotic for your product, it will be problematic to realize that with SendBird. Not as popular as <strong>Firebase</strong> and <strong>Socket.io</strong>. The price depends on the number of users. The base package costs $400 monthly for 5k active users. With 100k active monthly users, the price will increase to $5000.</p><p>Links: <a href="https://pub.dev/packages/sendbird_sdk">sendbird</a> <a href="https://pub.dev/packages/sendbird_sdk">packages</a></p><h3>GetStream.io</h3><p>The<strong> Flutter SDK</strong> lets you build any chat or messaging experience for Android, iOS, Web, and Desktop.</p><p>It consists of 4 packages:</p><ul><li>stream_chat: A pure <strong>Dart package</strong> that can be used on any Dart project. It provides a low-level client to access the Stream Chat service.</li><li>stream_chat_flutter_core: Provides business logic to fetch everyday things required for integrating <strong>Stream Chat</strong> into your application. The core package allows more customization and provides business logic but no UI components.</li><li>stream_chat_flutter: This library includes a low-level chat SDK and a set of reusable and customizable UI components.</li><li>stream_chat_persistence: Provides a persistence client for fetching and saving chat data locally.</li></ul><p><em>Advantages</em></p><p>Integrated reply in their SDK:</p><ul><li>Giphy, emoticons and file attachments</li><li>Threads links</li><li>Search in messages and conversations</li><li>Video playback</li><li>Online statuses</li></ul><p><em>Disadvantages</em></p><p>Although it has almost all the functionality for chat, same as Sendbird, there may be a problem if you need something specific. Also, high price (499 USD/month).</p><p>Links: <a href="https://getstream.io/chat/docs/flutter-dart/?language=dart">Getstream </a><a href="https://pub.dev/packages/stream_chat_flutter">packages</a></p><h3>Conclusion</h3><p>Before I conclude, I need to consider which solution is the best. For example, does my chat require minimal functionality, or do I need something more advanced?</p><p>Ready-made solutions, which I analyzed, offer a wide range of functionality, and with them, you can do almost anything a chat should have. But the most significant disadvantage is that these platforms are <strong>not free</strong>. Also, if you have some specific functionality that the platform does not offer, you still have to opt for some custom solutions like Socket.io.</p><p>With Socket.io you have complete freedom to achieve full customization, but you will have to develop from zero, and it takes time.</p><p>The conclusion is that if your chat requires a minimum base functionality and you don’t have a high level of requirements to it, <strong>Firebase Cloud Messaging-based solution </strong>is the way to go. On the other hand, if you need a quick implementation and money is not an issue, <strong>Sendbird</strong> or <strong>GetStream.io</strong> is a perfect solution.</p><p>But if there are a lot of requirements for a chat or you need lots of customized options,<strong> Socket.io</strong> is your friend.</p><p>See Links:<a href="https://hackernoon.com/firebase-sendbird-or-socketio-whats-best-to-build-a-chat-app-yb1035sm"> hackernoon</a> ; flyer chat</p><p>Many thanks to <a href="https://medium.com/u/3a1c2edd1228">Mario Otmacic</a> for writing this blog!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c696637427dd" width="1" height="1" alt=""><hr><p><a href="https://medium.com/q-software/flutter-chat-proof-of-concept-c696637427dd">Flutter Chat — Proof of Concept</a> was originally published in <a href="https://medium.com/q-software">Q agency</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>