The more test, the merrier – Week 3

--Originally published at That Class Blog

2 weeks done, 13 to go!

The more test, the merrier – Week 3 — DSC_6145 by Coldgunner (CC BY-NC-ND). From https://www.flickr.com/photos/coldgunner

We have some functionalities and a basic level working. The testing framework is there, and some functions to test too. Now the actual testing is only missing (Apart from everything else). It’s difficult and new, but I’m very confident I will get it to work.

That will be my main focus. But in general, some basic refactoring is going to be -already- made as well as more gameplay functionality.

Miguel Montoya
Esperanto enthusiast
ʕ•ᴥ•ʔ

The first stage of progress – Week 2

--Originally published at That Class Blog

So this week in the It’s not raining project, a lot of nonplanned progress was done, apart from the individual first-contact with the framework and workspace.

In my case, as I talked about at the start of the week I wanted to get to know p5.js and p5.play. Even though I didn’t make any kind of exercise or example with the last one, I did practice with p5.play and everything I need to remember of Node.js and express to assign the routes of the server. It was fun and interesting to make functions and equations that are really based on physics. To take into account mass, acceleration (gravity) and the drag coefficient certain liquids have. In my case, I tried to simulate water and an oil.

When I finished my practice I was given notice that the truth is that mostly nothing of p5.js was going to be of use to us (except the basics). Now I say goodbye to my little exercise, as I delete it from our git repo.

Talking about GitHub. W started using it in a more complete and professional way. It’s not my first time working with multiple, specific, and useful branches (I know this is not the case for some members), but it’s the first time I start to make more descriptive commits and declaring project issues. That’s nice.

Currently, I took interest in the testing as is something that I haven’t done before.

I assigned myself a GitHub issue and started doing some research and implementing stuff. I found it interesting but difficult, as I really didn’t know what I’m supposed to do to achieve certain tasks. It’s still difficult. But at least I know the testing framework works and I can do some basics asserts, but I’m missing to understand the routing and JSON responses. So that is will be my main focus this last sprint’s week.

Meanwhile, Arturo did the heavy lifting in the game-development area, and the rest of the team members did some research and investigation regarding GitHub and P5.play along with supporting Arturo on many issues.

I think we are doing great, faster than expected. I only hope that my testing issues won’t slow down the overall progress.

Let’s keep it up.

Miguel
Esperanto enthusiast
ʕ•ᴥ•ʔ

Week 2 Objectives: The start of something new

--Originally published at That Class Blog

Hold up just a second. Before doing anything at all, let’s think about where and how are we going to develop the project.

Week 2 Objectives: The start of something new — Original photo by Pal Sol (CC BY-NC-ND). https://www.flickr.com/photos/pal1/22268106872

Let’s select a workspace and a framework before we developt anything.

We firstly need a GitHub repo and implement good practices of version control.
EDIT: The repo is up now!

Arturo did suggest p5.js. A library that has quite some functions for 2D graphics, including physics, liquids and particles. So I guess I will start practicing and getting to know p5.js. I want to play with physics!!!

Miguel Angel Montoya Zaragoza
Esperanto enthusiast
ʕ•ᴥ•ʔ

Is it raining? No! It’s not!

--Originally published at That Class Blog

I have a course team! And a brand new project that will defeat all previous projects!

What is this new project’s name, you ask?

Well…

It’s not raining

The names might be just a working title, it was kind of a joke

Is it raining? No! It’s not! — Original photo from Fabrizio Angius (CC BY-NC-ND) https://www.flickr.com/photos/hippydream/4751762526

And, like in the photo above, our project will not have not a single drop of rain.

What it will have is a fun browser-based game that will not use any kind of plug-in because if Adobe and Oracle don’t even care for the support for their products, why should we? (Well, in fact, even if they did, we wouldn’t use them. Nobody uses them now. Nobody wants to).

The game will, basically, be a platformer with timer and a number of obstacles and maybe enemies. The score will be stored in an online leaderboard. We talked about maybe doing some drag-n-drop technology so we could let the players design their levels, and then compete with their friends and stuff. They could even download a level to text translation and share it with their friends.

My partners for the development for this new project are:

Andrés Barro
Arturo Fornés
Gerardo Juárez

Let’s hope everything goes well.

Miguel A. Montoya
Esperanto Enthusiast
ʕ•ᴥ•ʔ

So… Quality of Software – PreMortem

--Originally published at That Class Blog

YAY! A new course with Ken!
YAY! A new category for this kind of abandoned blog! I’m so bad at writing blogs. Well, at least now I’m using Grammarly, so at least I will write with less orthographic and grammar errors. ¯_(ツ)_/¯
Side-note: I really do recommend installing Grammarly in your browser, especially if you aren’t a native English speaker and are trying to learn. Especially because, at least, I have discovered some little things that could improve my text and I didn’t notice before. Continuing…

So, like in the Security Class, I will try to write what do I think I know about Quality and Software Testing.

I know testing and Quality Assurance are processes, not just a thing that you can check at the end of the project. You have to monitor the development from the start.
I guess QA is more focused on error prevention and testing is involved in the evaluation of the project.
There are concepts for QA such as the bugs log (Or something like that), that is made at the start of the project. It records possible bugs and problems one might encounter and the how-to proceed. That is why I think QA is more focused on prevention.
Testing involves much more than simply checking if the code compiles or if it can run with the expected conditions/inputs. In fact, it’s quite an extensive process. So big that there are masters degrees in software testing.
I know I don’t know the difference between Quality Assurance and Quality Control. I fact, I think QC is more related to testing. But Again, I don’t know.

And that’s it. At least that’s what I think I know. As always, I might discover that I already knew some stuff but I didn’t connect the information with this topic (Didn’t remember).

Now I can write what I expect of this course and what I would like to learn. This is more difficult than what one might think because apart from the things I wrote, I think I really know nothing more.

I hope to learn to produce a project how Alan Turing ‘ol mighty wanted us to. That is, with the proper procedures and steps to make sure I deliver a project with quality. Because, what is the point of working if at the end I deliver crap?

Maybe go trough: What is in fact software “quality”? What is good code? What is good design? And what is the difference between QA, QC, and testing?

And what do I expect of this course?

I know that I’m not a good blogger. I consider myself a quiet dude, craving for knowledge but not good at asking questions (Or answering, even if I know the answer). I’m not the type of person that would usually go to the teacher’s office. I really am a Pavlovian dog, with my classical conditioning, bells and saliva (Iugh) And I’m so afraid of failure that I often forget it’s essential in the process of growing.

So everything that is involved in a Ken course it’ s difficult for me… Except for the part of learning a lot by ourselves. I really like that one. But I hope to learn and improve myself. I really do.

And, that’s it. I think this was a really nice starting blog. I’m kinda proud of it. I will ~~try~~ make sure to continue this way.

Miguel Montoya
Esperanto enthusiast.

ʕ•ᴥ•ʔ