Unofin is a healthcare specialist fintech player which aims to plug credit gap across healthcare value chain through strong interplay of technology and healthcare data

Unofin

Imagine the situation: You return home after a long day at work, but your mind is still filled with the unfinished tasks that await you the next day. You try to relax, but these thoughts won’t let you go. Rather than helping you recharge your batteries for a new day, your mind is spinning and ruining your evening! If you’ve ever been in this situation, you’ve experienced the Zeigarnik effect. the tendency to remember an interrupted task better than a completed task. Zeigarnik Effect: This discovery was made by , who gave her name to the phenomenon. She came up with the theory while observing the behavior of waiters in a restaurant. the Russian psychologist Bluma Zeigarnik When the bill had not yet been paid, the waiters always remembered all the customers’ orders in detail. But once payment had been received, they instantly forgot what the customer had ordered. The young psychologist hypothesized that it’s easier to remember the details of an incomplete task than a completed one. The 1927 Experiment To verify her intuition, Bluma Zeigarnik set up an experiment, the results of which were published in 1927. , she asked participants to solve cognitive problems such as puzzles and brainteasers. In this study She interrupted half the group in the middle of their thinking and let the others complete their exercises. She then asked participants in both subgroups a series of questions to measure the details they could remember. The result was surprising: the interrupted subgroup remembered 90% more details than those who had completed the tests, thus proving Zeigarnik’s theory on the memorization of interrupted tasks. Although the Zeigarnik effect has been criticized by other researchers who have been unable to reproduce the same results, its effects can still be seen in everyday life. Have you ever felt like you’d forgotten everything you’d learned after passing an exam? The Zeigarnik effect is to blame. As Bluma Zeigarnik has shown in another study, this effect can also be helpful. For instance, students can use it to retain better what they have learned (by introducing voluntary interruptions). However, its negative effects are more commonplace, particularly in the workplace. The influence of the Zeigarnik effect on our work-life balance Our brain is a problem-solving machine. When we leave a task incomplete or are interrupted in its completion, a cognitive tension forms in our mind. This tension will help our brain to memorize the details needed to solve the task later. Whether we like it or not, this task will inhabit a part of our subconscious, a part of the brain we have no control over. And most often, the subconscious is most active when relaxing, meaning after work. Then, the classic pattern sets in: You think about the task that needs to be done, which creates stress and the need to do something about it. Feeling useless, you start working in the evening when your energy reserves are at their lowest. But this doesn’t work because, without energy, you can’t really do quality work. So, you fall back on low-value tasks, such as going through your emails. New problems arise, increasing your stress and wasting time that should have been spent resting. The next day starts off badly because you’re not fully rested. In the end, the task remains unfinished and even ruins your evening! Yet this vicious circle can easily be avoided, and researchers have even proved it. Overcoming the Zeigarnik effect with planning , researchers Roy Baumeister and E. J. Masicampo examined the Zeigarnik effect. They began by replicating the 1927 experiment by asking a group to complete a list of tasks. In a paper published in 2011 As you might guess, they interrupted some of the participants in order to generate the Zeigarnik effect. They then discovered a simple solution to reduce the effect: asking the interrupted participants to create an action plan to complete the remaining tasks. Planning the next steps allowed participants to free up more cognitive space to focus on other problems. The researchers also observed that, for these people, the feeling of having achieved their goal increased. What this experiment shows is particularly interesting for those who want to completely disconnect from their work to regain mental energy for the next day. It suggests that it is possible to trick our brains into a sense of completion through planning. To benefit from this method, the best is to establish a daily ritual at the end of your working day. The Anti-Zeigarnik Ritual In his book , author Cal Newport describes a daily practice he uses to effectively combat the Zeigarnik effect. He calls it the “Shutdown Ritual.” Deep Work To begin, you need to establish a routine lasting around 15 minutes at the end of your day. During these 15 minutes, you’ll take the following four steps: Review the tasks that couldn’t be completed today. For each task, create an action plan. The plan doesn’t need to be massively detailed. The important thing is to define the following steps to be taken for each task. Capture this plan in your organizational system (your “to-do list,” for example). Say a ritual phrase like “Workday successfully completed.” This little trick may sound a bit cheesy, but believe me, it does relieve the mental pressure you can feel at the end of the day and helps you switch off completely. Once you’ve completed this ritual, don’t spend a single second on work-related subjects - it’s now time to recuperate your mental energy! The Zeigarnik effect is omnipresent in our lives and, if left unchecked, can lead to burnout. Like an addiction to completed tasks, this effect prevents us from resting and enjoying better mental capacities during working hours. Yet a simple 15-minute ritual can free us from this effect and allow us to enjoy our evenings to the fullest. To say goodbye to the Zeigarnik effect, all you have to do is plan ahead! Also published . here

The Zeigarnik Effect: How Those Unfinished Tasks At Work Ruin Your Evenings and How to Beat Them

THE UNFINISHED BOOK

My side project game is at its all time low. Maybe I am using unhealthy comparison with myself during college years when I did not need to care about grownup stuff. But only shipping a tiny, two page app per year is sad. Strange part is that I am still constantly hacking on side projects, nothing has changed there. Where are those projects now? Oh, right, they have been abandoned before reaching “shippable” state. After some retrospective on previously successful and failed projects I think I have found why this is happening. Stuck in analysis paralysis Spending too much time thinking about the best technical solution. There is no need to think how the solution will scale when there is only one user — me. Facebook was built with PHP and plenty of companies started with Ruby on Rails. What was my reason for using Go on Google App Engine when Python had superior support and prototyping took half the time? Geeking out on new language, I guess. The best technical stack is the one which gets You from zero to production the fastest. Raison d’être Creating projects that have no clear reason why they should exist. There is nothing wrong with creating one more JavaScript web framework. But as a bare minimum the new framework should have at least one novel feature. And that feature should be the first thing implemented and shipped (think Minimum Viable Product). If the feature does not bring anticipated value, then there is no reason to build the rest. I somehow have forgotten about goals. S.M.A.R.T Context switching Juggling too many projects at the same time. Switching between projects is mentally demanding and turns out to be counter productive in the end. If I am stuck on a project, I am way better off going for a run than stuffing my brain with a different problem. Action plan Following my short retrospective I have devised an action plan for 2017. Start projects with one clear use-case or hypothesis to test. Define what MVP should look like Pick the most straight forward way to implement the project If MVP isn’t done, don’t start a new project. Get in into habit of following though from start to finish I have already made some good progress following my plan, so stay tuned for more posts about my projects.

Walking through the death valley of unfinished side projects

3 Lessons I Learned from Van Gogh’s Unfinished Work Look what I stumbled upon during a free afternoon in New York City: So here are three lessons I learned that I want to share with you: The power of the process. Experiencing Van Gogh’s stroke, original stroke, what he used to create the framework, the skeleton of his work, gave me a first row seat to his process of creation. In my mind, I could recreate his process of creating magical pieces of art which reminded me that our greatest creations are a result of simple, consistent and at times challenging steps that come together to create something where there was nothing before. Co Creating; Andy Warhol’s piece, intentionally unfinished, was designed for the art viewer to co-create the artwork with the original artist. Warhol invited the viewer to work with him in creating a unique experience of his art. I wonder, what would we create, if we designed more room for co-creating? At home, in the office, with our teams, our clients in the boardroom? The beauty in being human. I have to say, some of the pieces I saw at the Met Breuer Museum, these unfinished pieces, moved me more than some great art I’ve seen in other museums, some from the same artist. Why is that? I felt moved by the human side of the artist. The stories behind each piece and why they remained unfinished. It allowed me to see the artist not just as someone who creates great art, but as someone who is human and is using art to express their experience of life. I wonder, what would happen if we shared our human, imperfect, vulnerable side more often than we share what we do or who we are. Think of it, what if we showed our human side in facebook or other social media, instead of sharing ONLY our best side? How much more would we relate and connect with others? If you happen to stop in NY, please, do not miss this exhibit. In the meantime, come share YOUR humanity with us. I’m hosting a monthly planning session next week to help YOU plan your month of MAY. This is a FREE virtual, 60 minute video call where we come together as a group to help each other set and strategize our 30 day goals. Register Now! Feel free to share this opportunity with your network. You can copy and paste the text below in social media or in an email to your colleagues & friends: “Looking for some Clarity & Planning time? Dolores Hirschmann, Coach & Strategist is hosting a FREE & Virtual Monthly Planning Session to map out your next 30 days of reaching your goals. Register Now!” It’s Travel time! Let’s Meet Up. If you are in one of these places let’s connect. Here are my where & when for the next few weeks. Email me: Miami, FL; 4/21 to 4/24 Ft. Lauderdale, FL; 4/25 to 4/27 Buenos Aires; 5/2 to 5/9 New York; 5/10 Until next time, have a great week, Dolores Dolores Hirschmann is an internationally-recognized strategist, coach, TEDxOrganizer, speaker and author. She has over 20 years experience helping entrepreneurs, companies and organizations realize their potential — by guiding them with CLARITY — to refine their vision, message and market perspective needed to leverage their next level of growth. If you would like to learn more, book a FREE CLARITY SESSION.

3 Lessons I Learned from Van Gogh’s Unfinished Work

Scaling Bitcoin On-Chain with Omnity

Omnity সহ বিটকয়েন অন-চেইন স্কেলিং

Bitcoin On-Chain skalieren mit Omnity

Escalando Bitcoin On-Chain con Omnity

Faire évoluer Bitcoin en chaîne avec Omnity

ओम्निटी के साथ बिटकॉइन को ऑन-चेन स्केल करना

Omnity によるオンチェーンでのビットコインのスケーリング

Omnity로 비트코인 온체인 확장

Escalando Bitcoin On-Chain com Omnity

Масштабирование биткойнов в цепочке с помощью Omnity

Omnity ile Bitcoin'i Zincir Üzerinde Ölçeklendirmek

Mở rộng quy mô Bitcoin trên chuỗi với Omnity

使用 Omnity 在链上扩展比特币

Tools like ChatGPT have been a big help for programmers, offering code suggestions in chat and even directly within their coding environment. But these helpers have limitations. They can’t do everything a programmer can, like checking for errors or running the code to see if it works. This is where AutoDev steps in to make a difference. It’s like a super-powered coding assistant that can take action directly within your code files. AutoDev can edit files, search for information within the code, build and run the code, test it for errors, and even use command-line tools. This means it can help you complete complex coding tasks without you having to do everything manually. In essence, AutoDev takes existing coding helper tools to the next level by giving them the ability to directly work on your code and automate more steps in the coding process. Key Features: Conversation Manager Customizable Tools Agent Scheduler Evaluation Environment A novel framework that empowers AI agents to manage complex software development workflows. We demonstrate its effectiveness through evaluations using established datasets and showcase its ability to handle diverse software engineering objectives. The results highlight AutoDev’s potential to significantly automate software development tasks while maintaining a secure and user-controlled development environment. How It Works Behind the Scenes Imagine a team of AI helpers for your coding projects. That’s what AutoDev is! It lets these AI agents work together to tackle complex software development tasks without needing you to look over their shoulders constantly. Here’s a breakdown of how it works: First, you tell AutoDev what the AI helpers can and can’t do. You can choose from a list of pre-built commands, like editing files, running tests, or checking for bugs. You can even fine-tune these permissions to fit your specific needs. Think of it as giving your AI helpers a rulebook to follow. Setting the Rules: Once the rules are set, you tell AutoDev what you want to achieve. For example, you might ask it to create test cases for your code, making sure they work properly and catch any errors. This is like giving your AI helpers a specific task to complete. Giving Instructions: This part acts as the project manager for your AI helpers. It keeps track of everything that’s said and done, making sure everyone is on the same page. It also decides when to pause things and check in with you, just in case. The Conversation Manager: The AI helpers might suggest actions, but the Conversation Manager needs to make sure they’re following the rules and using the right commands. It also translates their responses into clear messages for you to understand. Understanding the Helpers: After the AI helpers take action (like running a test), the Conversation Manager gathers the results and puts them in a clear report for you. This way, you can see what the AI helpers did and what the outcome was. Keeping You Informed: Imagine AutoDev as a team manager for AI helpers in coding. This is like the team leader who assigns tasks to different AI helpers based on their strengths. Some helpers are better at understanding code (like OpenAI GPT-4), while others are better at creating code (like smaller language models). The leader decides who does what and in what order, using different methods like taking turns (round robin), letting someone work until finished (token-based), or prioritizing tasks based on importance. The Scheduler: These are like the coding assistants. They can’t directly write code, but they can follow instructions and use tools to help with various coding tasks. They communicate with each other and the team leader using plain English. The AI Helpers: This is like a toolbox with different functions for the helpers. There are tools for editing files (like code, instructions, or notes), searching for specific information within the code, building and running the code to see if it works, checking for errors, and even communicating with the team leader or you (the user) if they need help. The Tool Library: This is a secure environment where the helpers use the tools to work on the code. It keeps everything safe and makes sure no mistakes are accidentally made to the original code. The Safe Zone: How it works: You tell AutoDev what you want the code to do (the objective). It assigns different parts of the task to different AI helpers based on their skills. The helpers use the tools and communicate with each other to achieve the objective. Everything happens in the safe zone to avoid messing up the original code. This process keeps going back and forth until the code is finished, you ask AutoDev to stop, or there have been too many attempts without success. Overall, It helps automate complex coding tasks by using a team of AI helpers with different skills and a safe environment for them to work in. Testing AutoDev’s Skills Imagine you want to see how good AutoDev is at different coding tasks. That’s what the researchers did here. They set up some experiments to answer three main questions: Can AutoDev write code? Can AutoDev create tests for existing code? How efficient is AutoDev at doing these tasks? Write Code The researchers gave some unfinished code snippets and asked them to complete them. They compared AutoDev’s performance to other approaches, including directly using a powerful AI model like GPT-4. It did a very good job (almost as good as the best) at writing code, even without any extra training! They measured success by checking if the code AutoDev generated passed all the existing tests for that code snippet. Creating Test This test flipped things around. The researchers gave AutoDev complete code and asked it to create new tests for that code. They compared AutoDev’s tests to tests written by humans. Here’s the key finding: While AutoDev wasn’t perfect, it created tests that were almost as good as human-written tests in terms of how well they covered the code. The Efficiency Test This test looked at how many steps and resources AutoDev used to complete the tasks. They looked at things like how many times it had to call on the helper AI model and how many words it used in its conversations. This is important because you wouldn’t want AutoDev to take too long or use too much power to do its job. Overall, these tests show that AutoDev is a promising tool that can both write code and create tests for existing code. It’s still under development, but it has the potential to be a valuable helper for programmers. The Results: How Well Does AutoDev Do? The researchers looked at how well AutoDev performed on different tasks: They found that it did a great job (almost the best) at writing missing parts of code, even without any extra training! This is better than directly using a powerful AI model like GPT-4 on its own. Writing Code: AutoDev was also good at creating tests for existing code. Its tests were almost as good as human-written tests in terms of how well they covered the code. Creating Tests: AutoDev takes a few more steps than some other approaches, but that’s because it does more than just write code. It also checks the code it writes to make sure it works properly, which is an important step programmers normally do themselves. How Many Steps Does It Take? AutoDev is a promising tool that can both write code and create tests for existing code. It achieves good results without needing extra training data. It takes a bit more effort (steps) than some other approaches, but that’s because it does more thorough work. Technical Details (can be skipped by most readers): The researchers compared AutoDev to other methods and found it performed well. They measured success by looking at how many times it completed the task correctly on the first try (Pass@1). It uses more “tokens” (words) than some other approaches, but that’s because it takes extra steps, like testing the code it writes. It uses a secure environment to run the code it creates. AutoDev in Action We tell AutoDev to generate a Pytest test with specific assertions for a function in . Here's the Python code for the function: human_answer.py def is_bored(S):
  """
  You'll be given a string of words, and your task is to count the number of boredoms. 
  A boredom is a sentence that starts with the word "I". Sentences are delimited by '.', '?' or '!'.
  For example:
  >>> is_bored("Hello world") 0
  >>> is_bored("The sky is blue. The sun is shining. I love this weather") 1
  """
  import re
  sentences = re.split(r'[.?!]\s*', S)
  return sum(sentence[0:2] == 'I ' for sentence in sentences) We tell AutoDev to write the test to a new file named with a specific format. test_HumanEval_91.py It creates a new test file ( ) with the following code: test_HumanEval_91.py from .human_answer import *
import pytest
def test_is_bored():
  assert is_bored('Hello world') == 0
  assert is_bored('I am bored. This is boring!') == 2
  assert is_bored('The sky is blue. The sun is shining. I love this weather.') == 1
  assert is_bored('I think, therefore I am. I am bored?') == 2
  assert is_bored('') == 0 It discovers an error. One of the assertions fails. AutoDev Detects and Fixes the Error It identifies that the test for fails because it expects the function to return 2, but according to the function's logic, it should only return 1. 'I am bored. This is boring!' It corrects the failing test by updating the assertion statement in (line 5) to: test_HumanEval_91.py assert is_bored('I am bored. This is boring!') == 1 AutoDev runs the tests again, and this time, all tests pass. It successfully creates a test suite that covers all the functionalities of the function. This example highlights two key features : is_bored It can identify errors in its generated code and fix them. Self-evaluation: It keeps the user informed about its actions throughout the process. User Transparency: Conclusion Imagine them as little code-writing helpers. Instead of developers doing all the work, they become supervisors. And don’t worry, this won’t happen overnight. It’s a gradual shift, and developers will still play a crucial part in shaping the software world. So, while AutoDev is exciting, it won’t replace human developers in the long term. They’ll continue to be essential making sure the robots stay in line! 🤖👩‍💻👨‍💻 C# Programming🚀 Thank you for being a part of the C# community! Before you leave: If you’ve made it this far, please show your appreciation with a clap and follow the author! 👏️️ Follow us: | ** | | | | X LinkedIn Dev.to Hashnode Newsletter Tumblr Visit our other platforms: | | | | ** GitHub Instagram Tiktok Quora Daily.dev More content at C# Programming Also published . here

From Davin to Microsoft Autodev: Elevating AI Coding Assistants to Super-Powered Code Editors

Despite the woo-woo-seeming presentation of ideas in this and his most popular book , I think Napoleon Hill was onto something, even if it was expressed in a delulu way. Think and Grow Rich The following is the summary of the main concepts of a lesser-known Napoleon Hill book: . First things first - Hill didn’t think he was talking to the devil. He wrote it as a parable about human nature and how we sabotage ourselves. Outwitting the Devil actual What you’ll learn: What happens to the mind when it has no purpose? Mental habits and behaviors for success. How to use human nature to your advantage. The key concept of the book - drifting. Drifting refers to a state of mind that lacks aim or purpose - essentially going through the motions. 9 thought habits that lead to drifting: Fear Superstition Avarice Greed Lust Revenge Anger Vanity Laziness Success - drifter vs non-drifter In Hill’s terms, the difference between a successful and an unsuccessful person is a set of habits. If you’re not successful, it’s because you’re unwilling to train your mind. Drifting ≠ Success. Non-Drifting = Success. Successful people carefully choose the people they surround themselves with because we download the thought habits of the people we interact the most with. Drifter always complains that the world has run out of opportunity and there's nothing to do while the non-drifters will create opportunity no matter the circumstances. Non-drifters provide a service that's useful to as many people as possible; the attitude is to give before you get. How to protect yourself against drifting Value time as your greatest asset. Recognize that the emotion of fear is self-sabotage. Resist it. Decide what you want from life and create a plan to achieve it. Form the habit of being decisive. Don’t leave things unfinished. If temporarily defeated or failed, analyze it to extract the knowledge and advantage it has given you. Your thoughts guide your actions. Be wary of what/how you think. Human nature Hypnotic rhythm - the unconscious part of your mind that tends to solidify your habits and behaviors. These automated behaviours can be good or bad: brushing your teeth, compulsively checking social media, exercising, eating poorly etc. But hypnotic rhythm refers to thinking patterns, too. Do we ruminate or gossip? Are we grateful and forgiving? Do we look for opportunities or focus on what work? These mental habits usually form early on and then become solidified beliefs that produce the illusion that . doesn’t that’s what the world is How to stop drifting You need to develop: DEFINITENESS OF PURPOSE Definite aims, goals, and purpose. Have a plan for how you're gonna achieve them. Plans can change, but the definiteness of purpose doesn’t. If a plan fails don't be discouraged, devise a new plan. MASTERY OVER SELF Master your desire for 1) food 2) sex 3) desire to express loosely organised opinions. The person who talks less has the opportunity to learn more by listening to and observing others. Expressing loosely organized opinions is a destructive habit; don't give opinions unless you’re asked. CONTROLLING ENVIRONMENTAL INFLUENCE (ASSOCIATIONS) Your environment feeds your thought habits. We unconsciously adopt the habits of those we associate with closely. Association through romantic relationships has very strong powers because the minds are connected spiritually. TIME Time converts thought habits into outcomes and either penalizes or rewards you depending on them. Time allows human beings to cultivate wisdom, but wisdom only comes to non-drifters who proactively use their minds for positive thought habits. HARMONY Like attracts like - nature seeks things of a similar nature. Successful people 1) make sure to have harmony among their business associates 2) require their associates to have definiteness of purpose. CAUTION - THINKING THROUGH YOUR PLAN BEFORE YOU ACT Think first act second. A drifter reacts before thinking. Has a plan if things go wrong to avoid unnecessary stress. How the mind works, according to Hill We receive thoughts from the collective consciousness and the Infinite Intelligence (God, Universe, Consciousness - whatever it means to you). All negative desires are nothing but frustrations of positive desires. Thoughts tend to invoke similar thoughts so if you're thinking positively, more positive thoughts will come up and vice versa. The thoughts that we keep having become a part of the hypnotic rhythm law. That's why it's so important to choose your thoughts. Wrap up Would I recommend you read the book? Yes, if you’re not bothered by spiritual-speak. offers a deep dive into the psychology of success through a dialogue with the sabotaging part of ourselves. Outwitting the Devil Key takeaways: Have purpose and vision for your life and guide your actions accordingly. Master self-discipline, both through thought habits and curating the people/information you surround yourself with. Value your time and use it to your advantage by creating positive mental habits that compound over time and bring you ‘luck.’ Also published . here

A Key to Success: Defeat Drifting

In this blog post, I want to discuss the importance of starting with a red test. The red-green-refactor cycle is a well-known mantra in test-driven development. To recap: Red - write a piece of test code for the functionality you want to implement. It must be red since the functionality is not there yet. One of the main ideas is that the tests should guide the development process. Green - write a piece of code for the test to pass. Refactor - eliminate code duplicates, enhance readability, improve aesthetics, possibly extract some methods or create new classes, and optimize. Don't forget to refactor both the production code and the test code. Why red? I very rarely do post-code testing (perhaps there is a better-known expression for writing tests after writing production code). I do that when I encounter a piece of code not covered with tests that I need to put my hands on. And I'm happy when the test is green, making me feel the code works as expected. Test-driven development is not only about writing tests to make sure the production code works as expected, but it is rather (as the name suggests) a process of development. A couple of things pop into my head when I think about Red in . First is demand; I produce the production code when it is needed (red test), and I need to meet the demand. Second - YAGNI (You Aren’t Gonna Need It), I do not produce the code that is not needed, I do not code too much, because it might not be needed. TDD I'm just a human after all I'm only human, and I make mistakes. I make mistakes in production code and test code alike. The idea for this blog post came last week when I encountered situations where the test was not red, and it was very tempting to leave it as is because it was GREEN. This was especially true when there were already several tests, leading me to think that I might have already covered the case. It may sound like an oxymoron, but a GREEN test in the first step of TDD is a RED flag. In the following sections, I will provide cases that I encountered last week where I made a mistake in the test, causing it to be green, but it was incorrect. it vs if I'm a backend developer and use TDD a lot. However, sometimes I have to work with front-end and do . I do my best to practice TDD while doing JavaScript development as well. JavaScript development For JavaScript testing, I use as a test runner and as a test framework. In , the function sets a test case, and the function defines an individual test. I want to share how I mistyped as multiple times, leading to a false impression of all passing tests. karma jasmine jasmine describe it it if it('Seat map is selected when person of the seat map is selected', 
    function () {
        let seatMaps = result.Seating.SeatMaps;
        expect(seatMaps[0].Selected).toBeTrue();
        seatMaps[2].Passengers[1].select();
        expect(seatMaps[2].Selected).toBeTrue();
    }
); and if('Seat map is selected when person of the seat map is selected', 
    function () {
        let seatMaps = result.Seating.SeatMaps;
        expect(seatMaps[0].Selected).toBeTrue();    
        seatMaps[2].Passengers[1].select();
        expect(seatMaps[2].Selected).toBeTrue();
    }
); In all modern development environments and text editors for developers, is usually highlighted in a different color. I'm not colorblind, but it is still easy for me to miss it. Additionally, I find that my finger muscle memory is used to typing a two-letter word starting with as . It just happens automatically. As a result, there are no errors, and it is a valid sentence. All tests appear green when I run them. It is easy to notice when it is the first test because it will show that 0 tests have been run. However, it is more difficult when there are more tests. In this particular situation, my initial thought was, Fortunately, my experience with treating green tests as a red flag saved me. if i if "aha, I already covered this functionality.". Missing the attribute This example is in C#. While it's not taken from production code, it captures the essence: [DataRow(1, 2, 3)]
[DataRow(2, 3, 5)]
public void SomeFakeTest(int a, int b, int c)
{
    Assert.AreEqual(c, a + b);
} In the MsTest test framework, the attribute alone is insufficient to mark a method as a test. The or attribute is required for the method to be recognized as a test. I have found myself forgetting this attribute a few times, which resulted in tests not being run and creating a false impression of all tests passing. DataRow TestMethod DataTestMethod Missing assertion The following example, which I adapted from my previous blog post, demonstrates the situation. I recall the instances when I write a test - I think of a test case, a test name, arrange it, then act, and then - get distracted. When I return to see where I left off, I usually run the tests to see the red ones and continue from there. But in this particular case, all are green. This case is tricky; it's easy to forget that I left the test unfinished, and it's green because it doesn't have an assertion.ertions. [TestCaseSource(typeof(UnexpectedPaymentMessageIsSentWhenInvoiceIsOverpaidOrUnknownCases))]
public async Task UnexpectedPaymentMessageIsSentWhenInvoiceIsOverpaidOrUnknown(
    Invoice invoice,
    string message)
{
    _invoiceRepositoryResult = invoice;

    await CallCallback();
} Misread Recently, I needed to modify the functionality of a DTO converter to return passengers in order by , rather than in a somewhat random manner. I'm using , which allows passing configuration in the method. I simply typed , and Visual Studio's IntelliSense suggested a list of options. I chose the first one that started with and ended with . sequenceNumber FluentAssertions BeEquivalentTo config.With With Ordering seatMapDto
    .Passengers
    .Select(x => x.FirstName)
    .Should()
    .BeEquivalentTo(
        new[]
        {
            "GUDMARIN",
            "GUDMARIANA",
            "TOM"
        },
        config => config.WithoutStrictOrdering(),
        "should be ordered by sequenceNumber"
    ); I ran the test, and it was green. Since I expected the test to be red, I began by making sure that the input data was unordered in the arrange part to create a nonsequential order for the test to be red. Only later did I realize that I had chosen the configuration instead of . WithoutStrictOrdering WithStrictOrdering Wrapping it up Being human and making mistakes is not easy :). In this blog post, I wanted to showcase how sometimes silly mistakes can give the impression that tests are green, and emphasize the importance of starting with a red test first. Have you encountered similar situations where a mistake in a test led you to believe that production was working as expected? Please share your experiences in the comments. If you enjoyed this post, please click "like" and "follow". Feel free to explore my other blog posts, where I write about test-driven development and my pet project EasyTdd, a Visual Studio extension that makes test-driven development simpler. Also published here.

UNOFIN

unofinance.in

-- employees

Since n.d.

COMPANY RANKING

UNOFIN

EVERGREEN INDEX #11394

Representing this company? Click here to claim and customize this page!

Unofin WIKI

Apply to get your Tech Company News Page live on HackerNoon.com today!

UNOFIN

unofinance.in

-- employees

Since n.d.

COMPANY RANKING

UNOFIN

EVERGREEN INDEX #11394

RELATED COMPANIESRANK

STORIES ABOUT UNOFIN

Representing this company? Click here to claim and customize this page!

Unofin WIKI

Apply to get your Tech Company News Page live on HackerNoon.com today!