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...
Read more

Sprint-1 Retrospective

 I didn't manage to achieve a whole lot in my 1st sprint, I mostly looked at the guest frontend and poked around Thea's pantry. I'm going to make sure next sprint I actively work on the issues my team has in the backlog.  The only change I made to the pantry was a branch in guestinfofrontend named add-linters that I was planning on adding the Alexjs linter to. Unfortunately I never got around to actually adding it, and it seems that the other teams have already handled the adding of linters to the project. https://gitlab.com/LibreFoodPantry/client-solutions/theas-pantry/guestinfosystem/guestinfofrontend/-/tree/add-linters?ref_type=heads Next sprint I plan on focusing on the inventory frontend and actually making and commiting changes. I do not want to let my team members do all the work.
Read more

Git and Game Development

     A subject that has always been near and dear to my heart is video games. Throughout my life I have always been deeply enamored with games and the process of their creation, from the intricacies of 3d modeling to the various game engines in use. Despite that, I would not say I am an expert in modern game development by any means. As my classes have progressed however, I have begun to understand more about the inner workings of software development and how teams are managed. This led me to investigate how game developers use these tools to manage projects and keep everything orderly. After doing some research, I found that many game engines are compatible with git and have no issue being stored on GitHub. Not only that but prominent game engines like Unreal Engine even have their source code up on GitHub , available for anyone to fork and clone . This was done to allow developers to modify the game engine itself, for whatever purposes they need. Godot is...
Read more