Regression Testing

  While looking for something that I could use for my 5th homework, I started looking into other software testing styles that we have not covered in class. There are tons of different styles that are implemented to introduce quality testing to software development. One such style I found this time is called regression testing, a testing style created to combat resurfacing bugs. Basically, regression testing is about implementing test cases every update, and maintaining them throughout future iterations. This is done to prevent old bugs from resurfacing and to check for any new bugs from being introduced in every update. Test cases should be created and implemented after every iteration to prevent bugs from piling up within your software.

https://www.browserstack.com/guide/regression-testing


 While this may sound a lot like retesting , the main difference is that regression testing looks for unknown bugs rather than known. How this may look is the test cases are not for any specific bug but rather more general to catch any problems that came about during the last change. Other differences include the fact that regression testing can be automated, while Retesting cannot. In order to remain vigilant, one should implement both of these styles in order to avoid any problems from implementing new changes.

https://www.browserstack.com/guide/retesting-vs-regression-testing

Some examples that I saw listed of regression testing tools include Cypress, Playwright, and Puppeteer. These tools typically ensure that your software and test cases work across different platforms and operating systems. Last post I talked about how I found a website that uses A.I. to write test cases, and considering how regression is already inclined to be automated, I can’t help but wonder how long we have until we see an entirely automated software development pipeline using regression testing. I think it’s not too far in our futures.

In the article I linked above they give some examples of some regression test cases. They use the classic shopping cart program and the test cases are things like making sure the back end fetches the correct number of items in the cart, or checking if the elements on the front end are still visible despite scrolling down. These cases are general enough to catch both new and old bugs on subsequent updates. For the Mars Rover kata we did in class an example I could use would be updating the grid to be 100 squares big in each direction, and then creating a new test case to check if it still wraps around at the 99 mark.

 

Comments

Post a Comment

Popular posts from this blog

Open Source Software in Education

     In recent times I have started a job as a computer teacher for a private school, and as such I have had to become familiar with a variety of educational software. As an educator, it is important for there to be a plethora of accessible software to teach children digital literacy , as computers have become increasingly incorpor ated into more facets of modern society .  Open-source software is one avenue that allows young students a ccess to important tools to learn and create, without incurring a hefty price tag for their school. This is especially true for those learning how to code since it is not exactly a subject that comes naturally to everyone. While there are certainly many free IDEs out there for any aspiring adult programmer to use, I am more concerned with young children who may not be able to understand all the complex operations of standard IDEs.  The best answer I have found is the  educational coding software Scratch, created by MIT. Licensed under the "
Read more

Remote Work

     Ever since the pandemic, the modern workplace has gone through many shifts. The realization that workers can still be effective members of the company from their home has changed a lot of people's perspective on the corporate work environment. Many workers have pushed for remote work to become a staple of the modern job market. It is easy to see the appeal of remote work: No commute, stuffy office, or even stuffier dress code sounds very appealing to me. I personally enjoy the ease of access to one's job right in their own home. All of that said, the infrastructure for remote work has been in the works for longer than we realized that there was a need for it. In the modern era, cloud computing has become a necessity for almost any job regardless of whether it is remote or not. Services such as AWS, Azure, and Git hub/lab has supplemented developers with the tools to contribute to their workplace from anywhere on the globe. Now teams can be comprised of any developer withi
Read more

Code Etiquette Across Languages

     In the past weeks we learned about proper code etiquette when structuring your code. Most of our focus was on java methods and classes, and how to name and structure them so that other developers could better understand our code. Re-establishing the basics of clean code was an essential part of our studies in programming, but it got me thinking about other languages. How do the rules of clean code manifest in different coding languages, and what quirks do other languages have that force them to follow different rules ? For the most part, when it comes to object-oriented programming   the rules are consistent across languages and do not really need any modification . ‘ Keep It Simple Stupid ’ and ‘ Don’t Repeat Yourself ’ are principles that hold merit regardless of if you are using Java or C++. Keep code separated by whitespace and indented to create sectio ns of code unified in their purpose , name variables and functions with their purpose clearly displayed, and
Read more