End of week 8 (Vacations)

--Originally published at That Class Blog

As I was talking about the week before last, we decided to take that week lightly and so the week after that (Because it was our Taller Vertical).

 

End of week 8 (Vacations)
“Change” by Mark Deckers (CC BY-NC-ND). From https://www.flickr.com/photos/27454036@N03/5994875062

The summary of the last to weeks is the following:

  1. I made some bugfixes regarding the code I was working the past weeks. Some of the scripts were heavily bugged, especially the ones regarding level setting and getting to and from the database.
  2. Realize that I have to update part of the documentation. That I didn’t do.
  3. Realize as a team that we need more objectives to our project. Because, as it is, we kinda have done everything. So that is what we are going to do this week.

That is all for now. Thanks for tunning in.

Miguel Montoya
Esperanto enthusiast
ʕ•ᴥ•ʔ

I did something different: Week 7 Recapitulation

--Originally published at That Class Blog

This week I worked in getting a level development aid. And I think I did a nice work.

Basically it’s a mocha/chai script, that connects to the testing database and uploads the json file of the level, and if any modification it’s required, it reuploads it. If you refresh the level.

Peek-2018-02-20-20-39(1).gif

I worked also in the development of a third level using this aid. I think I did a nice level, it’s only missing approval of the rest of my partners before uploading it.

P.D: Sorry for the weird visuals in the GIF.

I did something different: Week 7 Recapitulation
“Nano Titans” by Pascal (CC0). From https://www.flickr.com/photos/pasukaru76/9667850610/

Something different: TO-DO Week 7

--Originally published at That Class Blog

This week I’ll be working with two issues that aren’t quite as similar as the previous work I’ve done.

Something different: TO-DO Week 7
“Dare to be Different” by Tamás Éberhardt (CC BY-NC-ND). From https://www.flickr.com/photos/tomtata/8060928920

First (GitHub issue):

I’m going to be working in the design of a third level. I’m so bad when I play the game that I hope I won’t make anything very difficult or very easy, because it’s possible I won’t be able to pass it alright.

Second (GitHub issue):

This is the responsibility this week that I’m excited for. I’m going to develop an enviroment where the level designer can test its level without needing to upload the level to the server, and the removing it and so.

Sprint 2 it’s over: End of week 6

--Originally published at That Class Blog

Sorry for uploading this week’s blog one day later. But I’ve been sick and yesterday was the worst of it. PLEASE, DON’T VACCINATE WHILE YOU HAVE THE FLU, EVEN IF THE MEDICS TELL YOU IT WONT AGGRAVATE YOUR CONDITION.


Last week we finalized the second sprint. It was a hevier sprint, for all of us. But progress and effort is getting reflected in the project. we are happy.

Sprint 2 it’s over: End of week 6
“Sprint” by Denis De Mesmaeker (CC BY-NC-ND). From https://www.flickr.com/photos/2ni/223990159

This last week, as I mentioned in the previous week, I mainly worked regarding two new issues. First, to create a database dummy for testing and applying hooks during testing. Second, to develop new tests applying the new features, such as hooks, for the new features (And more extensive tests for previuous done tests).

GitHub Issues:
1.- Hooks and Dummy DB
2.- Testing

Regarding the first issue:

I was reading a tutorial on Mocha/Chai testing (link below) and in a step, the guy talks about creating a different database to stop the pullution and unnecesary requests to the main DB. And that was the first part of this issue. I made a new cluster in Atlas for testing purposes, and implemented new enviroment variables and .ENV files for the connection (Which was in fact, the complicated part).

Then, I started reading in the same tutorial about hooks, and how weel those functions integrate with with database testing. The hooks available are: before(), after(), beforeEach() and afterEach(). The names basically describe everything those function do. The important thing to know is that these functions are written inside the describe() function. before() and after() esecute one time during each describe() and, if it’s an “each” function, it executes before or after each it().

Regarding the second issue:

This issue was quite simpler. Now that I uderstand hooks, I can start making more useful but simpler tests.

To summarize everything up, I made tests for the POST at /getLevel, a POST and GET at /score and the delivery of the static files.

We are almost at the middle of the available weeks! But not really…

Miguel Montoya
Esperanto enthusiast
ʕ•ᴥ•ʔ

I really did stuff

--Originally published at That Class Blog

So in my previous blog, I wrote that I didn’t have a lot of stuff to do. But I talked to my partners and discussed some self-assignments for this week (And next).

So, basically, I made 4 new issues, of which I completed 2 and left 2 for next week. We were given notice that we are going fast regarding the project development. So, these new issues don’t implement new stuff (Well, kinda of…), but most of them implement new and more efficient ways of doing what we already did.

I really did stuff
“Canada goose” by Yi-Lian (Lucas) Liu (CC BY-NC-ND). From https://www.flickr.com/photos/yiliangliu/13982774079/

The first new issue was to implement Mongoose as interface to connect to mLab. This would provide a more stable connection to the DB and schemes and models for document creation and finding. These new models have steps for verifying the content of the documents too. The only problem with this was that the campus’ network has proxies that wouldn’t let the connection to begin with mLab and Mongoose. This problem cause my second issue.

Move our database from mLab to MongoDB Atlas. This wouldn’t have been as complicated if Atlas provided a free interface to the database’s collections and documents. So instead, some scripts were necessary to create to feed the database and check the data that is already uploaded.

Everything was successful at the end. There were 1 or 2 hard complications (Like identifying the problem with mLab and the network). Now two more issues are pending. You can read about them in the next blog.

Miguel Montoya
Esperanto enthusiast
ʕ•ᴥ•ʔ

404, level 2 not found.

--Originally published at That Class Blog

404, level 2 not found.
“404_madness” by Oliver Tacke (CC0). From https://www.flickr.com/photos/otacke/13990410803

I guess this post won’t be long. I already did all of my assigned issues (You can check the current and past issues here). I’ll be working alongside my partners in any way they need. And I will star doing some refactoring and code documentation. And I will talk with my parters in the project administration area regarding my working payload.

Miguel Montoya
Esperanto enthusiast
ʕ•ᴥ•ʔ

Wrapping up week 4 – End of week 4

--Originally published at That Class Blog

This week passed way too fast, and I feel there wasn’t a very stable calendar for working hours. Still, I enojoyed the developement, as always…

Wrapping up week 4 – End of week 4
“Mongo (and Mongo clone)” by spDuchamp (CC BY). From https://www.flickr.com/photos/duchamp/415211871

This week I worked with the database, succesfully. I helped with the development of a json’s format for level loading (It includes the coordinates for every object and text, as well as some strigified lambda functions to parse when the level is loaded. This last feature I didn’t know it could be applied.

Also with this topic, a back-end function to make a request to the mLab server was made, and a function to properly load the level when the client makes a request.

I also worked with my partners to clean the code and fix some damn bugs we hadn’t ecountered. Well, the truth is that most of them weren’t bugs, just tome minor functionalities that weren’t implemented and caused some undesired characteristics.

Miguel Montoya
Esperanto enthusiast
ʕ•ᴥ•ʔ

2nd sprint ready to ignite – To-Do week 4

--Originally published at That Class Blog

Okay, so I already have my assigned issue for this week. I found quite nice the idea of just having some assigned tasks, not bothering about what can or should do. Thank you project manager!

2nd sprint ready to ignite – To-Do week 4
“Milestones” by Professor Bop (CC BY-NC-ND). From https://www.flickr.com/photos/professorbop/2766103746/

Thiw week I’ll be focusing on getting the remote database up and feed it with levels designed by Gerardo. I estimate it will be an easy implementation. So I guess I will be available to assist any of my partners.

Miguel Montoya
Esperanto enthusiast
ʕ•ᴥ•ʔ

I understand testing now – End of week 3

--Originally published at That Class Blog

Okay. 3/15 done.

I felt quite more productive this week.

I finally cracked chai (Using mocha) and supertest. It just clicked somehow. Last week was a lot of confusion and then it just… worked. I can’t even remember the process I made to make it work. Hehe.

I understand testing now – End of week 3
“Drone First Test Flight” by Richard Unten (CC BY). From https://www.flickr.com/photos/unten44/9631706311

Part of the problem is that I didn’t worked with http requests before. I didn’t knew what a http mock request was, or if i needed one (After trying a lot I realized that I don’t). At the end I achieves victory. I made my description of the tests. I used supertest’s request to assert the main get request to the server and to check the JSON response of a post (Used to properly load the level).

So I’m happy about that.

After passing the JSON test, I helped Arturo making the level actually load from the JSON. It was difficult, again, because my poor HTML skills, and some poor documentation about which function is the adequate to make the request, whatshould the headers contain and how to encode the JSON trough the response.

I had fun.

The team, in general, worked hard to improve the gameplay and add functionalities. I think that a lot of bugs arose during this week’s development. A lot of them just from merging branches. That did also consume work time.

I’m proud of our GitHub more proffesional usage. Finally a full team that comprehends branches and the use of issues… YAY!

Let’ s keep it up!

Miguel Montoya
Esperanto enthusiast
ʕ•ᴥ•ʔ