Cayter Goh’s Post

Anecdotal of TDD Today I found an edge case in a software component that, it turned out after some analysis, was not covered by any test case. First I reexecuted the test cases for that software component to check that nothing had happened to it. By analysing logs etc. I eventually discovered the fault. Then I "corrected" the fault, added a test case, re-executed all the test cases and I got a lot of failures. It turned out that my initial correction was incorrect. Changed it and all tests ran through. Without the test cases that I run frequently, it is less likely that my faulty correction would have been discovered. Also, I would have less chance to check that the component still worked as it was specified earlier. Do I follow TDD strictly? Not entirely, it is more like concurrent test design; sometimes prior or sometimes right after design and implementation. The key issue is that it is done in the near time frame of the design and implementation of functionality. Refactoring is a key issue. #softwaretesting #tdd #components

Testing allows us to make sure our code works, but just as important, it enables "fearless refactoring". Have you ever heard a colleague say "It works, don't touch it"? That's because they fear regression bugs. In case you didn't already know, these are bugs that can occur when a piece of code that was working stops working. In this case, it may be that a refactoring introduced a regression, and without tests you'd only become aware of it in production, if ever. Having a sturdy suite of tests can protect us against regressions and allows us to refactor without fear that our code will break. That's one of the reasons testing is so important.

𝗛𝗼𝘄 𝗱𝗼 𝘆𝗼𝘂 𝗱𝗲𝗯𝘂𝗴 𝗶𝘀𝘀𝘂𝗲𝘀? 𝟭) 𝗗𝗲𝗳𝗶𝗻𝗲 𝘁𝗵𝗲 𝗽𝗿𝗼𝗯𝗹𝗲𝗺 The first step in debugging is defining the problem. This means identifying its symptoms, comparing expected versus actual outcomes, determining its scope, assessing its severity and impact, and noting steps to reproduce it. This clarity streamlines the troubleshooting process. 𝟮) 𝗥𝗲𝗽𝗿𝗼𝗱𝘂𝗰𝗲 𝗶𝘁 Reproducing the bug is often the most effective way to pinpoint its cause. However, if this can't be done try checking the environment where it occurred, searching the error message online, assessing the system's state at the time, noting how often it happens, and identifying any recurring patterns. These steps can offer vital clues. 𝟯) 𝗜𝗱𝗲𝗻𝘁𝗶𝗳𝘆 𝘁𝗵𝗲 𝗰𝗮𝘂𝘀𝗲 Logs are a big help in the debugging process; if they're insufficient, add more logs and reproduce the issue. Some additional strategies are to use debugging tools for insights, test components in smaller chunks, and try commenting out code sections to pinpoint the problem area. 𝟰) 𝗣𝗿𝗼𝘃𝗶𝗱𝗲 𝗮 𝗽𝗼𝘀𝘁𝗺𝗼𝗿𝘁𝗲𝗺 When a bug's cause is identified and resolved, thoroughly document the issue, the fix, and ways to prevent it in the future. Sharing this knowledge with the team is important to ensure everyone is informed and can benefit from the lessons learned, promoting a proactive approach to future challenges. ~~~ 𝗔 𝗯𝗶𝗴 𝘁𝗵𝗮𝗻𝗸 𝘆𝗼𝘂 𝘁𝗼 𝗼𝘂𝗿 𝗽𝗮𝗿𝘁𝗻𝗲𝗿 𝗣𝗼𝘀𝘁𝗺𝗮𝗻 𝘄𝗵𝗼 𝗸𝗲𝗲𝗽𝘀 𝗼𝘂𝗿 𝗰𝗼𝗻𝘁𝗲𝗻𝘁 𝗳𝗿𝗲𝗲 𝘁𝗼 𝘁𝗵𝗲 𝗰𝗼𝗺𝗺𝘂𝗻𝗶𝘁𝘆. Did you know Postman released a feature in recent months that makes API debugging faster and easier? It's called Live Insights. Learn more about it here: https://lnkd.in/gSwpCVyh 🔔 Enjoy my posts? Follow me Nikki Siapno and hit the bell for content daily. If you found this helpful, I write an email every Thursday to help you level up your engineering and system design skills. Sign up here: https://lnkd.in/giQj3Z44

If you keep hearing about #TDD being the best thing since sliced bread and you want to find out what it is and how effective it is, here's an article that dived deep into the topic. #softwaredevelopment #softwareengineering #testdrivendevelopment #testautomation https://lnkd.in/g5jMeNW7

CI/CD A key component of contemporary software development is CI/CD (Continuous Integration/Continuous Deployment). It involves automating software creation, testing, and deployment to speed up development and lower error rates. Docker is a vital piece of CI/CD technology that allows programmers to create portable, lightweight containers for their applications. Other well-known sub-technologies in this field that provide platforms for automating various stages of the software development process include Gitlab, Jenkins, Travis, Circle CI, and Kubernetes. Ficus Technologies has successfully completed projects utilizing CI/CD technologies. In order to speed up the software development process and guarantee top-notch outcomes, our skilled team of developers is well-versed in using these tools. Ficus Technologies can assist businesses in achieving a quicker time-to-market, higher quality code, and increased productivity by utilizing our CI/CD expertise. We recognize the value of automating software development procedures and possess the abilities and expertise required to guarantee that the projects for our clients are completed on schedule, within budget, and to the highest caliber possible. https://lnkd.in/dn32GAZw #CI #CD #Docker #Gitlab #Jenkins #Travis #Kubernetes #CircleCI #software #testing #deployment #technology #development #programm #quality #productivity #skilled #developers #enginers #FicusTeam #FicusDevelopers #FicusDevelopment #FicusTechnologies

𝐃𝐨𝐜𝐤𝐞𝐫 𝐂𝐨𝐦𝐦𝐚𝐧𝐝𝐬 𝐂𝐡𝐞𝐚𝐭 𝐒𝐡𝐞𝐞𝐭 🐳 𝐃𝐞𝐯𝐎𝐩𝐬 𝐅𝐑𝐄𝐄 𝐖𝐞𝐛𝐢𝐧𝐚𝐫 & 𝐑𝐞𝐬𝐨𝐮𝐫𝐜𝐞𝐬 https://lnkd.in/dmB4EgdR As Docker gains traction, mastering essential commands becomes crucial for developers and ops engineers alike. This cheat sheet highlights key Docker commands for efficient management: 𝐈𝐦𝐚𝐠𝐞𝐬: docker build: Create an image from a Dockerfile. docker pull: Fetch an image from a registry. docker push: Upload an image to a registry. 𝐂𝐨𝐧𝐭𝐚𝐢𝐧𝐞𝐫𝐬: docker run: Start a new container based on an image. docker start: Start one or more stopped containers. docker stop: Stop one or more running containers. docker restart: Restart one or more containers. docker logs: View logs from a container. 𝐍𝐞𝐭𝐰𝐨𝐫𝐤𝐬: docker network create: Create a new network. docker network connect: Attach a container to a network. 𝐕𝐨𝐥𝐮𝐦𝐞𝐬: docker volume create: Create a new volume for persisting data. 𝐒𝐞𝐫𝐯𝐢𝐜𝐞𝐬: docker service create: Deploy a new service. docker service logs: Fetch logs of a service. 𝐂𝐥𝐞𝐚𝐧𝐮𝐩: docker system prune: Remove unused resources from the Docker environment. With these commands, you can: Build and share container images effortlessly. Manage running containers with ease. Establish networks and persist data using volumes. Define and scale services across multiple containers seamlessly. Keep your Docker environment clean by removing unused resources efficiently. Post Credit -: Omkar Srivastava

If you are looking to learn about OpenTelemetry instrumentation (Java, Python, Node.js, etc) by playing with code an the OTel language libraries, check out our app Elastiflix (from Elastic ) Check out the blog on how to get it, and use it. https://lnkd.in/g6wzencp) #opentelemetry, #java, #python

If you are looking to learn about OpenTelemetry instrumentation (Java, Python, Node.js, etc) by playing with code an the OTel language libraries, check out our app Elastiflix (from Elastic ) Check out the blog on how to get it, and use it. https://lnkd.in/eMGcvCfg) #opentelemetry, #java, #python

If you are looking to learn about OpenTelemetry instrumentation (Java, Python, Node.js, etc) by playing with code an the OTel language libraries, check out our app Elastiflix (from Elastic ) Check out the blog on how to get it, and use it. https://lnkd.in/grX7hxTa) #opentelemetry, #java, #python

If you are looking to learn about OpenTelemetry instrumentation (Java, Python, Node.js, etc) by playing with code an the OTel language libraries, check out our app Elastiflix (from Elastic ) Check out the blog on how to get it, and use it. https://lnkd.in/dC3Y6dsk) #opentelemetry, #java, #python