Junit Testing and its basic

 

The article “JUnit Testing: The Basics and a Quick Tutorial” explains the fundamentals of Junit and how it works in testing environment. The author begins by describing unit testing as the process of verifying small pieces of code independently, ensuring each component behaves correctly before integrating it into a full application. JUnit supports this by allowing developers to write automated tests using annotations and assertions that compare expected and actual results. The article highlights that testing early improves code quality, helps detect bugs quickly, and supports continuous integration workflows. It also introduces major features such as annotations, assertions, parameterized tests, and exception testing. Finally, the tutorial demonstrates how to install JUnit, write a simple test class, and run tests from an IDE or command line.

I selected this resource because I am currently learning software testing and writing unit tests myself. This article is short but sums up all the important pieces in the Junit testing and areas that was not touched on during class. understanding the “why” and “how” together was particularly useful and the reasons why I use that before without thinking I should have done this came back to mind in comments like @Beforeall and how to download junit test and run it in our own environment without relying on the already installed docker environment. This continued if I did not use ide and started use commands to run the test, as I at least need to know how to run things if I decide to use different ide or try stuff with command line with increased integration of the terminal. Not only that, but I also need to keep in mind how structured testing improves long-term maintainability. The article emphasizes that running tests after refactoring ensure functionality remains intact.

In future practice, I expect to apply this by writing unit tests alongside my code rather than afterward just to make sure I coded things right. Because as I write things in mind, I only checked the codes based on if the codes were running or not or seems like they were not thoroughly enough after seeing these test tools and testing methods for future uses. I plan to create small test cases for each method, so changes do not break other parts of the program. More importantly, I now see testing not as extra work but as a tool that saves time and reduces frustration. Over time, adopting this habit should improve both code reliability and confidence when making changes.

 

https://brightsec.com/blog/junit-testing-the-basics-and-a-quick-tutorial/

Comments

Post a Comment

Popular posts from this blog

Waterfall 2.0

  When looking around the internet, I found that there was waterfall 2.0 version of the waterfall software development methodology that we learned at start of class. After I saw the article, I found out that even the most established practices can transform to meet the demands of new era. Therefore, I chose this article as it provides basic summarization of waterfall 2.0 and the difference between traditional waterfall model. As we talked about why waterfall method was being replaced by agile and scrum, I thought there will be some people who will try to improve and use the old working method so using this article showed me how waterfall transformed to adopt need of current workflow. Therefore, I decided to look into it as a background for finding out about the improved version as it revives the dying method into a new form.              This article uses baking as an example to illustrate the principles of waterfall 2...
Read more

Is Agile going to fail?

  This article by Jeff Gothelf asks the question “Is Agile finally over?” after 20+ years of implementation to tech field. He argues that even though Agile’s widespread adaptation hasn’t got the result that Agile was intended for. Many companies claimed to be “Agile” as they copy each other, but the implementation of it was shallow or almost non-existent to make changes according to it. Therefore, he says that agile does not seems working as companies try to make employee follow set of rules instead of working in following the basic principles of Agile. He concluded that organizations need to focus on true organizational agility rather than rigid framework adoption. This article caught my attention while searching through the internet as it criticizes Agile’s current status in the business world as ideal of agile does not really fit in reality in organization experience. The vague promises and core ideas are often overlooked to the ‘wants’ of either customer or the organization...
Read more

Docker and it basics

     Since I use different computers from home, class, and work, after learning from class about docker and setting up the same environment for all the devices, I thought it was time to look into docker more. The article is about what is docker, why it became popular and comparing it with other tools. That is why I choose this article because “Docker overview” by Marsdev gives comprehensive introduction about docker, comparing to virtual machine, use cases and advantage over other tools over the internet. It clearly explains these things easily and detailed make it ideal choice to learn how docker works and its benefits.      The article covers essential components of Docker including Docker Engine, Images, Dockerfiles, Docker Hub, Volumes, Compose, and Desktop and how they work. For example, Docker Engine serves as the backbone of the platform, enabling the creation and management of containers, while Docker Compose allows developers to manage multiple...
Read more