Author: carlosmartell97

Clock is Ticking

--Originally published at TC3045 Software Quality and Testing

Continuing on from my previous post… we must now prepare everything for Expo Ingenierías. There’s
even a possibility that some of us will have to be present more than 1 project, so there’s that.


For our class, the final delivery for each of our projects will be a presentation of our project, in video
format. A short, dynamic video where the means and end of our project are all clearly exposed. So, by
this Friday we must have this ready. I’ll share it with all of you here as soon as this happens. Looking
forward to it.


Here’s a cookie for you, for reading this whole tiny post! yes... I bit it. Sorry.

Little Tweaks, Tiny Fixes

--Originally published at TC3045 Software Quality and Testing

Hey, you.


So, as you may have noticed from my previous posts, these past few weeks have been way calmer than
usual for this project. We’re all still busy with all our other projects (that are not quite as done as this
one), so out priorities have gotten in the way. That, and the fact that assistance to these past few
classes has been optional. And, what did we do? Well, I know one of my teammates has been
researching for ways to shelter our Raspberry so that it can properly work in a living plant settlement.
Why? We’ve decided we want to present this project at Expo Ingenieras, an event where student
projects of various areas of engineering are showcased for the general public.


So we must now prepare everything for this event. Consider it Berry House’s first look at the world
outside our classroom.



The Sequel to the Trilogy

--Originally published at TC3045 Software Quality and Testing

Hey, you. Hola. Hallo. Bonjour.


Do you want to know what our plans for this week are? Awesome, that’s what I was just going to talk
about! Otherwise, no reason for you to keep reading (please do).


As I mentioned in my previous post, there’s not much left to do. But that certainly doesn’t make the
things we still have left to do less important. What’s on MY plate, you say? Well, I’ll look at ways for
dealing with SSL certificates like the one we have right now, so that our Raspberry can continue to send
data to our infrastructure without any issues. I’ll also continue to look out for issues with the current
graphs we’re now showing to the user in the web client, as well as updating our tests and
documentation. That is, until something else comes up during the week that might also need to be done.
We’ll see.


That’s all I got for you right now. You may go outside and enjoy some sun now. Or just go to bed if it’s
dark. You’ll thank me later.


And of course, here’s a joke for you as a reward for reading through this tiny post:

1, 2, 3… Another 100m Sprint

--Originally published at TC3045 Software Quality and Testing

So… last week. What happened? Our 3rd sprint review. And, everything turned out well. As we get close
to wrapping up our project, we continue having less and less things left to do, other than better
implementations, bugs and general improvements. But the main structure and purpose of it all is mostly
done at this point.


In this sprint retrospective, we talked about our latest updates on the web client, with graphs shown to
the user for each of the parameters measured through time. Also, the data sent from the Raspberry Pi
to our sensors platform can now be done through HTTPS, so security is looking a little better now. We
still have to make some adjustments, given that for now we are signing this SSL certificate ourselves.


And that’s mostly it. The waters are mostly calm now, and we’ll have to continue dialoguing about what
we still need to do from here on and and what’s really just a “nice to have”.


So yeah. Watch out for more posts. There aren’t that many left, I promise to stop the bad jokes soon
(maybe) (maybe not) (ok bye).



Third Time’s a Charm

--Originally published at TC3045 Software Quality and Testing

As you may have (hopefully) read in my previous post, last week’s sprint review was postponed for this
coming week. So that’s the first thing that’s going to happen now. With this, we’ll hopefully get some
valuable feedback from Ken and our classmates for proposals and possible improvements to it all.

Other than that, and by judging at how our web platform is looking so far, I would like to add to my
“Doing” list the task of showing the data of plants to the user in helpful charts, statistics to let the user
easily know the conditions of a plant through time. This will finally get us to one of the key objectives of
our project: help prevent/warn the user of unwanted conditions for the plant’s health and wellbeing.

That’s all. Bye now.



Third Time’s a Charm

--Originally published at TC3045 Software Quality and Testing

As you may have (hopefully) read in my previous post, last week’s sprint review was postponed for this
coming week. So that’s the first thing that’s going to happen now. With this, we’ll hopefully get some
valuable feedback from Ken and our classmates for proposals and possible improvements to it all.

Other than that, and by judging at how our web platform is looking so far, I would like to add to my
“Doing” list the task of showing the data of plants to the user in helpful charts, statistics to let the user
easily know the conditions of a plant through time. This will finally get us to one of the key objectives of
our project: help prevent/warn the user of unwanted conditions for the plant’s health and wellbeing.

That’s all. Bye now.



Full Stack

--Originally published at TC3045 Software Quality and Testing

As hard as it may be to believe, it’s not Semana Santa yet… even though this past long weekend almost
made it feel that way. Though in my particular case, not so much. We led the organization for the
CodeGDL hackathon, which happened from Saturday to Sunday. So as you may imagine, my time was
mostly consumed by it. And don’t get me wrong, it was an awesome experience, it all turned out great.


Aaand before that, we had a full week for working on this project. What did we accomplish? Well, our
whole pipeline was fully tested to handle the 3 values from our sensors platform: temperature, humidity
and light. This, as well as the components for registering a new plant from our web platform. Also, some
little changes were also made so that the automatic tweets from our sensors platform are a bit more
human-sounding.


And that was mostly it. Our 3rd sprint review was postponed until next class because the room(s) we
usually have class in were not available.


Stay put for more updates on this project and anything else going on.


Commitments > Promises

--Originally published at TC3045 Software Quality and Testing

Aaand what’s in our agenda for this week? Well, once again we all have to talk to one another about
what’s left to merge from our individual tasks. This week we’ll have our third Sprint Review, and we
have a few new things to showcase.


We’ll see how it all goes.
Until then, I guess that’s all.
Bye.



Back at it Again

--Originally published at TC3045 Software Quality and Testing

So, last week. And with that, I mean 2 weeks ago. This past week with Taller Vertical we put away this
and all other classes, so we could focus on our virtual reality project delivery. Everything turned out well
in the end with my team.


...A complete flow through our pipeline is now visible! Our dashboard was fully deployed publicly. There’s
still a lot to improve, but it now shows the temperature registres stored in our database.


Also, we now have automatic tweets! As soon as our sensors platform activates, it starts averaging all
values so that, after a determinate amount of time, it sends an automatic tweet informing of its condition.
Here’s the proof.


So yeah, we keep making progress. The whole thing growing more and more.
Stay put for further updates.



Year 2038 Problem

--Originally published at TC3045 Software Quality and Testing

Previous week was a bit slow, we lost a bit of the energy that had us so pumped up at the beginning
of the semester, but we still want to see this project through. We still believe in it. Personally, I did
some research into the “Epoch” time, an universal reference to know the current time… the amount
of seconds that have elapsed since January 1, 1970 (midnight UTC/GMT), without counting leap
seconds. And, interesting fact, many Unix systems store epoch dates as a signed 32-bit integer,
which might cause problems on January 19, 2038 (known as the Year 2038 problem or Y2038).
Beware, world. You can read more into this here https://www.epochconverter.com/


Anyways, we decided to use this system as a timestamp for every temperature reading in our
project, so I found out how to obtain this value in Python. It’s actually pretty easy. We also decided
to move forward with our initial idea of having the plant “tweet by itself” updates on its current
condition.


Next post coming soon.