Friday, June 24, 2016

Third week: London!

My third week of internship was a pretty special one: I went to London to the Mozilla meeting named "All Hands". This meeting happens twice a year (one in the summer and other one in the winter) and puts together all the Mozillians, from the CEO to the interns and some top contributors (volunteers to Mozilla Open Source projects), everyone (even the invited contributors) has no cost to go to this meeting, they pay everything: from the food to the visa (if needed), including flights, hotel, etc.

Me in the Police Box, in Mozilla All Hands. In the opening session of All Hands, the speakers got out of Tardis


The meeting was huge, there was more than 1,300 Mozillians and so many sessions, lectures, meetings, Hackathons, etc in two hotels in the center of London: Mozilla All Hands is definitely overwhelming for a first time attendee: there is so much to see in so little time. Even more if it happens in a city like London! You can imagine how much a new comer as me, in a such city that I have never have been before, felt!

The event was amazing, but the city even more: I could go to three nice points of the city: The Parliament, The Tower Bridge and The British Museum, it was amazing.

Me and a friend in Parliament.

Me in British Museum.

I saw many good things about London: it was very clean, it has a very good public transport system, it seems to be very safe, I haven't saw many house less people etc. But other things were quite weird to me, such as: I could barely listen to English in London, people on the streets were talking in Portuguese, Italian, Hungarian, German, etc. but so few talking in English! I could understand why the European immigration is such an issue to English people: I could not feel anything Britain in London, because there were so many foreigners there, it is like there is not a culture from London: just a crazy mix of cultures.

Sunday, June 12, 2016

First two weeks: Filter tests by outcome


On my first two weeks as an Outreachy intern, I worked on the issue 38 of Pytest-HTML. That issue is to allow users filter tests results by its outcome. My strategy to do that is putting check-boxes on each outcome, so when the checkbox is checked, we can see the result of that outcome, but when it is unchecked, we can't see that.

https://camo.githubusercontent.com/c945c72d28f1dc827bed0a84676951a2c56123c0/687474703a2f2f6f6936372e74696e797069632e636f6d2f723837306a362e6a7067
Now is how it looks

A few changes has been made on Pytest-HTML code to do that. Maybe the biggest one is that before, the log row and the result row were totally separated rows, so we had to do the checking twice to hide the result and the log row. So now, both rows, are under a element, and like that, we can associate the result and its log.

On the plugin structure, a few changes were made, now there is a class named "Outcome" in the main plugin, so now the summary can be created in a much more elegant way. Maybe it can be created classes to build the table also (And it may helps on the next issue that I will work on).

Also, a few enhancements to the testing methods were created, now the assert summary (now named "assert results") is asserting more things than before, and in a more elegant and legible way.

Today I am going to travel to London, to meet my mentor and other Outreachy people! But I already started to take a look on my next issue: support to another Pytest plugin, the Automatic reruns.