Hello internet! This will be my blog for my CS-443 Software Quality Assurance and Testing class. I’ll be writing about things that I find interesting in the world of software testing, and I look forward to writing my first entry.
From the blog Griffin Butler Computer Science Blog by Griffin Butler and used with permission of the author. All other rights reserved by the author.
Hello everyone! My name is Aidan Noone, and I am now a Senior at Worcester State University. I am currently pursuing a bachelor’s degree in computer science with a Homeland Security Minor, and I will be updating this blog often as I continue to progress through this final semester of mine, working on software quality assurance.
From the blog CS@Worcester – CS Blogs with Aidan by anoone234 and used with permission of the author. All other rights reserved by the author.
My name is William Cordor and this is my introductory blog post.
From the blog CS@Worcester – Blog del William by William Cordor and used with permission of the author. All other rights reserved by the author.
Hello this is Debug Ducker again, now here to document my experience and anecdotes relating to software tesitng. I am looking forward to it as I am somewhat familiar with testing from previous computer science class and this looks to go in depth in the process on an industry level.
As a reminder I am a college student and this will hopefully be my final semester. I am a comp sci major and hoping to have a career in software development. So good thing I am taking this class.
Speaking of testing for software here is a funny story relating to computing history. The first computer bug was an actual bug. In September 9, 1947 a team of computer scientist in Cambridge, Massachusetts reported finding a dead moth caught in the computer they were using causing the system to malfunction. Now we refer to software errors/mistakes as computer bugs.
Thank you for your time and have a nice day.
From the blog CS@Worcester – Debug Duck by debugducker and used with permission of the author. All other rights reserved by the author.
Hello everyone,
my name is Sepehr Karkonan, a senior at Worcester State University majoring in Computer Science. I am writing this blog to introduce myself and want to wish everyone a great semester filled with success, valuable lessons and great memories. Looking forward to learning with everyone-happy learning.
From the blog CS@Worcester – The Bits & Bytes Universe by skarkonan and used with permission of the author. All other rights reserved by the author.
Hi everyone, I am Cameron Baron – a senior Computer Science student at Worcester State University. This is an introductory post for my Software Quality Assurance and Testing course to ensure all blog posts will be posted as expected. Upcoming blog posts will be centered around finding useful information and various tutorial overviews related to this topic as I continue to learn.
From the blog CS@Worcester by cameronbaron and used with permission of the author. All other rights reserved by the author.
Hello, and welcome to my blog!
My name is Woubinwou Djouwe Rick Manuel, but most people call me Rick. I am an undergraduate Computer Science student at Worcester State University, and this blog is dedicated to documenting my journey in CS-443: Software Quality Assurance and Testing.
I have a strong passion for software engineering and artificial intelligence, and I enjoy working on projects that solve real-world problems. Throughout my academic journey, I have gained experience in web development, Python, Java, C++, and database management. I also have a background in tutoring and mentoring students in math and computer science.
From the blog Rick’s Software Journal by RickDjouwe1 and used with permission of the author. All other rights reserved by the author.
Hello fellow CS pursuers! I’m Zachary Kimball and this is my blog started for my CS-443 course.
I’m pretty sure I messed up tagging or something about my last post so I created a new domain and hopefully this go around is better!
This blog is mainly focused around my CS class I’m enrolled in with professor Perez at the moment but I hope to continue it in the future!
From the blog CS@Worcester – Zacharys Computer Science Blog by Zachary Kimball and used with permission of the author. All other rights reserved by the author.
I was looking through an article called “What Is JUnit: An Overview of the Best Java Testing Framework”. The link is here: What Is JUnit: An Overview of the Best Java Testing Framework. This article introduces JUnit to its audience. First it defines JUnit which is open sourced unit testing for code in the Java language. Then it defines unit testing which is what JUnit is part of. Unit testing is defined to have the audience better understand JUnit. Although I personally would have put the unit testing definition before the definition of JUnit since it appears in JUnit’s I understand that it was done to get more traffic on the site. The article later list JUnit’s features and its annotations.
I chose this article because it related to what I have been recently learning. Also, I am new to JUnit so it would be interesting to learn more about it. In my most recent class, we were introduced to annotations which I defined as indicators for when a method should execute or is a test. Thanks to the article, I understand that an annotation can be used to ignore statements during test execution, to set some timeout while a test is executed and to handle some exception during test execution. I also learned about JUnit’s use cases. At first, I thought it only verified that the provided code worked. I now know it has a lot more uses. It tests how code behaves will null values and invalid data. It verifies that objects maintain their state throughout their lifecycles. This essentially means that it checks if objects do what they are supposed to do. It tests interactions between the tested code and the external library. It provides a safety net allowing users to not worry about regressions when modifying their code. Also, JUnit code is a cornerstone of TDD, integrate with CI pipelines and can run test legacy code. These lead to bug free and testable code. So JUnit has a lot of uses.
I also liked how the article was structured. It was simple, concise, and provided a lot of useful information as seen on the paragraph above. I only wished it gone over JUnit assertions because I am still a little confused about that. Overall, this was a very newbie friendly article.
To conclude, I this article has improved my understanding of this topic. It has also increased my interest. I look forward to learning more and using this in the future.
From the blog CS@Worcester – My Journey through Comp Sci by Joanna Presume and used with permission of the author. All other rights reserved by the author.
Hello, this is my blog for CS-443 Software Quality Assurance and Testing.
From the blog CS@Worcester – Matchaman10 by tam nguyen and used with permission of the author. All other rights reserved by the author.