Category Archives: CS-443

About my blog for CS-443

Hi everyone,

This is Tianyuan Wang, you can call me Ty.
Here is the blog I just created, which will be used for me to learn and record knowledge about CS-443 Software Quality Assur & Test.

I will post and share my questions, experiences and learnings here.

First of all, before learning how to test software specifically, I would like to talk about my understanding and expectations for this course. My understanding of software testing is the process of verifying that the software logic is correct, the functions are complete, the system is safe and the quality is reliable. These are necessary for any software, whether old or new. For example, before a brand new software is released or after an old software is upgraded, professionals must operate the software under specified conditions to discover program errors. The process of measuring software quality and evaluating whether it meets design requirements.

That was my first impression of the CS-443, and I was ready to learn more about it.

From the blog CS@Worcester – Ty-Blog by Tianyuan Wang and used with permission of the author. All other rights reserved by the author.

About my blog for CS-443

Hi everyone,

This is Tianyuan Wang, you can call me Ty.
Here is the blog I just created, which will be used for me to learn and record knowledge about CS-443 Software Quality Assur & Test.

I will post and share my questions, experiences and learnings here.

First of all, before learning how to test software specifically, I would like to talk about my understanding and expectations for this course. My understanding of software testing is the process of verifying that the software logic is correct, the functions are complete, the system is safe and the quality is reliable. These are necessary for any software, whether old or new. For example, before a brand new software is released or after an old software is upgraded, professionals must operate the software under specified conditions to discover program errors. The process of measuring software quality and evaluating whether it meets design requirements.

That was my first impression of the CS-443, and I was ready to learn more about it.

From the blog CS@Worcester – Ty-Blog by Tianyuan Wang and used with permission of the author. All other rights reserved by the author.

Exploring the in’s and out’s of Software Quality Assurance.

SQA ( Software Quality Assurance)

This blog is dedicated to exposing the reader to best practices while performing Software Quality Assurance.

Within this blog you will find different types of content regarding;

  • System testing (exploring ways to address defects or errors) 
  • Security testing ( exploring different ways companies can reduce risk) 
  • Code Reviews ( exploring code quality and ways to improve) 
  • Performance Testing ( exploring performance issues and ways to improve) 
  • And more…

This blog post will be closely related to the course taught within most computer science majors at colleges entitled, Software Quality Assurance and Testing, which covers these topics and more. Stay tuned for the latest entry for this blog and how you can be informed on the latest news on SQA Testing practices. 

From the blog CS@Worcester – In's and Out's of Software Testing by Jaylon Brodie and used with permission of the author. All other rights reserved by the author.

Software Quality Assurance and Testing Introduction

Hello, my name is Giovanni and this semester I will be taking CS-443 Software Quality Assurance and Testing. This blog will cover the various topics that will be discussed within the course through finding other blogs and podcasts allowing me to reflect on their findings.

From the blog CS@Worcester – Giovanni Casiano – Software Development by Giovanni Casiano and used with permission of the author. All other rights reserved by the author.

Introduction Blog

Hello, I am Anxhela Sejdi and I am a senior Computer Science student with a concentration on Big Data Analytics. This is my last semester at WSU.

From the blog CS@Worcester – Coding by asejdi and used with permission of the author. All other rights reserved by the author.

Intro Blog

Hi, I am Abraham Passmore. I am a senior here at worcester state and this is my last semester before I graduate. My concentration is in Software design.

From the blog CS@Worcester – Abe's Programming Blog by Abraham Passmore and used with permission of the author. All other rights reserved by the author.

CS443 – Introduction

Hello everyone, we are back and doing it again this semester. Tech Worth Talking About returns with posts about two courses, CS443 – Software Quality Assurance and Testing as well as CS448 – Software Development Capstone.
CS443 will focus more on strategies and tools for automating code testing as well as how testing incorporates into the overall development process. This goes far beyond simply debugging.

Welcome, and stay tuned!

From the blog CS@Worcester – Tech. Worth Talking About by jelbirt and used with permission of the author. All other rights reserved by the author.

introduction: software qa and testing

I will now be writing to this blog for my CS-443 course, which will be categorized and tagged for each post for that course. Not too excited to write 8 posts for this, but it is what it is.

From the blog CS@Worcester – V's CompSCi Blog by V and used with permission of the author. All other rights reserved by the author.

CS-443 Introductory blog

This blog is just a setup for CS@Worcester, CS-443

From the blog CS@Worcester – Kadriu's Blog by Arber Kadriu and used with permission of the author. All other rights reserved by the author.

Testing in Python and Sea

Something that is worth noting is Python’s assert keyword. Python has a built in way to create basic unit tests beyond simply printing and making comparisons. This has me thinking about my Sea programming language.

I think much of the hassle I’ve had with unit testing has come from simply getting the environment set up in the first place. If unit tests could be more like a data structure or design pattern – something you know the design of and you can simply implement – I think that would simplify a lot. So while I could create a Sea library for unit testing similar to numerous other libraries (or wait for someone else to make one in Sea), I’d prefer to create a more internal solution.

Sea is fundamentally C, so that means it doesn’t have a lot of high level features that can make unit testing easier. I mean, Sea isn’t even object oriented. That said, the entire design philosophy behind Sea is based on simple syntax that doesn’t add a runtime performance cost. One way I could achieve this is by adding another “stage” to the language. The current design of Sea involves a preprocessor, a lexer, a parser, and a visitor (interpreter, transpiler, or compiler). What I could do is add a tester that would run before the visitor, to test compile-time things (checking types or any other value known at compile time) and then a runtime tester. These could be modular features of the language itself and could be removed if desired.

Another simple solution is to add a handful of keywords to Sea similar to assert. The problem with that is C doesn’t have runtime exceptions. The design would have to be based on the notion that the program is the unit tests. I’ll continue to think this over. After all, Sea is still in its early stages. I’m currently rewriting it (just on the visiting functions now) and then I’ll add functions, pointers, etc. However, if Sea is to become a real, usable language then there will have to be ways of testing code; the simpler and more convenient, the better. After all, that’s the whole point of Sea.

From the blog CS@Worcester – The Introspective Thinker by David MacDonald and used with permission of the author. All other rights reserved by the author.