Forem: Lenni Ojala

Git ohjeet suomeksi: Muokkaa edellistä committia

Lenni Ojala — Sat, 21 Nov 2020 16:43:24 +0000

Joskus git-kommitin tekemisen jälkeen tekisi mieli tehdä muutoksia - korjata commit-viestin kirjoitusvirhe tai tehdä vielä pieni muutos koodiin.

Tässä artikkelissa kerrotaan ohjeet commit-viestin muokkaamiseen sekä edellisen commitin tiedostojen muuttamiseen. Bonuksena myös ohjeet Vim-editorin käyttämiseen.

📝 Git-historiaa ei kannattaa muuttaa, jos olet jo puskenut (push) committeja remote-repositorioon muiden käytettäväksi, sillä muiden ihmisten historian sotkeminen ei ole hyvä tapa.

Alla on ohjeet commit-viestin muuttamiseen (ohjeet 1 ja 2) sekä edellisen commitin tiedostojen muuttamiseen (ohje 3):

1. Edellisen commit-viestin korvaaminen uudella

Kirjoita komentoriville uusi commit-message amend-parametria käyttäen:
git commit --amend -m "uusi commit message"

2. Commit-viestin muokkaaminen ja Vim-editorin käyttö

Jos haluat muokata commit-viestiä, jätetään -m (message) parametri pois, jolloin viesti avautuu gitin tekstieditoriin (yleensä Vi tai Vim). Tässä ohjeet editorin käyttämiseen:

Anna komento git commit --amend
Editori avautuu commit messagen muokkaamista varten
Paina tietokoneen näppäimistöltä i ja editori siirtyy kirjoitustilaan (insert)
Muokkaa commit-messagea. Risuaidalla (#) alkavat rivit eivät kuulu git-committiin.
Paina näppäimistöltä esc, jolloin editori siirtyy komentotilaan
Uusi commit message tallennetaan ja editori suljetaan kirjoittamalla :wq ja painamalla näppäimistöltä enter/rivinvaihto (tässä : aloittaa komennon, w tarkoittaa write (eli tiedoston tallennus) ja q tarkoittaa quit)

Vim-editorin sulkemisesta löytyy läjäpäin meemejä. Tämä naurattaa: "Olen käyttänyt Vimiä nyt noin 2 vuotta, lähinnä siksi, että en tiedä miten se suljetaan."

3. Tiedostojen muuttaminen edelliseen committiin

Edellisen commitin tiedostoja voi muuttaa amend -parametrin avulla seuraavasti:

Tee tiedostoihin halutut muutokset (lisää uusia tiedostoja tai tee muutoksia tiedostoihin):
Lisää tiedostot staging-tilaan komennolla git add ja tiedostonimi
Tässä välissä kannattaa ajaa komento git status ja tarkistaa, että halutut tiedostot ovat stagingissa
Commitoi lisäys edelliseen committiin komennolla git commit --amend tai git commit --amend -m "haluttu commit message"

Loppusanat

Jos tämän jutun git-versiohallintaan liittyvä terminologia kuulostaa vieraalta, ohje suomeksi löytyy esimerkiksi LevelUP-koodarien sivuilta.

Robot Framework: Pass Boolean variables from command line

Lenni Ojala — Fri, 18 Sep 2020 07:38:41 +0000

I am often googling how to pass Boolean Command Line arguments in the Robot Framework when starting tests. The answer is: True and False work (case is important here as this is Python).

In some earlier releases, 0 and 1 were seen as Boolean but that does not apply in the newer Robot Framework versions.

Example, passing CLI (Command Line Interface) variables

Below is an example that tests that variable MY_BOOLEAN is Boolean type (so tests pass both with True and False).

I wanted to play with the new Python Inline Evaluation (see User Guide here) so the example has another test that uses that (both tests test exactly the same thing, the only difference is the syntax):

And to start that test, MY_BOOLEAN is given using --variable notation:

robot --variable MY_BOOLEAN:False path/to/tests/

Or, in a shorter form using -v:

robot -v MY_BOOLEAN:True path/to/tests/

Closing words

Next time when I google "robot framework how to pass boolean command line arguments" I hopefully pop into this blog post 🤓. Maybe this post might also help with the concept of passing Robot Framework variables from the command line.

ps. Passing multiple arguments is done by adding multiple -v "blocks":

robot -v MY_VARIABLE:cat -v SOME_OTHER_VARIABLE:dog path/to/tests/

Robot Framework - Run tasks using GithubActions

Lenni Ojala — Mon, 24 Aug 2020 14:53:30 +0000

Submission for the DEV: GitHub Actions For Open Source 🍕🍝🥕

My Workflow

Continuous Integration (CI) workflow for running Robot Framework RPA (Robotic Process Automation) tasks.

Task (this is not implemented using actions) searches recipe from foodie.fi site and returns the number of search results. GitHub Action workflows handle following:

Basic CI (running tests for Pull Requests, commits to the main branch, and manually)
Recipe Bot: When someone opens an issue to a GitHub project, recipe search is triggered, Bot closes the issue, and posts number of results as a comment. Bot is implemented using existing Action Issue matching auto-closer.

Submission Category:

Maintainer Must-Have

Link to Code

laojala / rpa_challenge

GitHub Actions demo for Robot Framework RPA

Demo: Find number of recipes in foodie.fi website

Demo project for running Robot Framework tasks in Docker and in GitHub Workflows.

Background

Demo is inspired by the Mimmit Koodaa RPA summer challenge 2020. Project is also a submission to a GitHub Actions Hackathon on DEV as it demonstrates usage of GitHub Actions.

Project demonstrates

How to run Robot Framework Tasks using Docker without need to install Python and Robot Framework to a computer
How to run Robot Framework Tasks in GitHub Workflow using GithubActions:
- Automated runs for commits in the main branch and pull requests. Action can be also triggered manually (configuration: .github/workflows/trigger_search.yml)
- Run Tasks when a new issue is opened. Action uses issue title to search a recipe in foodie.fi/recipes and closes issue by commenting number of search results in a comment. This is the wacky wildcard submission for the DEV.to Hackathon 🍕🍝🥕.

Run Tasks locally using

…

View on GitHub

Additional Resources / Info

See also my other submission that implements similar CI for a Robot Framework project: Robot Framework - Configure CI using GitHub Actions. Both of these projects are intended as an example for someone who is building CI that runs Robot Frameworks tests/tasks.

Robot Framework - Setup CI using GitHub Actions

Lenni Ojala — Sun, 23 Aug 2020 15:20:22 +0000

Submission for the DEV: GitHub Actions For Open Source 🦕🦖

My Workflow

Continuous Integration (CI) workflow for running Robot Framework tests. Demo has two Workflows that provide these use cases:

Run Robot Framework tests:
- when new commits are pushed to the main branch
- when new commits are pushed to a Pull request
- run tests with a pre-defined schedule
- Trigger tests manually. Input variables for a test run.
Reporting:
- Store Robot Framework reports from test runs
- Post summary of results as comment to a commit. Comment is posted only to the main (master) branch.

Submission Category

Maintainer Must-Haves

Link to Code

laojala / robot_docker_demo

Robot Framework - Setup CI using GitHub Actions

Robot Framework CI Demo

This project demonstrates how to setup Continous Integration for Robot Framework tests using GitHub Actions.

Use Cases

Demo covers these use cases:

Run Robot Framework tests
- when new commits are pushed to the main branch
- when new commits are pushed to a Pull request
- run tests with a pre-defined schedule
- Trigger tests manually. Input variables for a test run.
Reporting:
- Store Robot Framework reports from test runs
- Post summary of results as a comment to a commit. The comment is posted only to the main (master) branch.

In other words, a separate CI server (such as Jenkins) is not needed to run Robot Framework tests.

Why use Actions for CI?

Using GitHub Actions for setup CI is almost better than sourdough bread 🍞🎉 Setup is straightforward and usage is free for public repositories (see pricing for other types of repositories).

Setup described here is very…

View on GitHub

Additional Resources / Info

The project is intended as a demo about how to integrate Robot Framework tests to the CI.

Description of the tests

The project implements a simple "dinosaur test" that takes two inputs and tests if those are dinosaurs. Test is coded using Robot Framework and it's standard Libraries. Project has also a cron-schedule for running tests for this dinosaur test once a year and running tests for the pull requests and for commits to the main branch.

Image below displays how the Dinosaur test can be triggered manually in the Actions:

achillobator", "Creature that is not a dinosaur:
pteranodon", and "Tag for tests to run. Use '*' to run all: dinosaur". Button in the bottom has text "Run workflow""/>

Further resources

I have created another demo project that describes Docker usage with Robot Framework RPA tasks. This project contains GitHub Actions BOT for closing issues. Project describes in detail how to run Robot Framework tests inside a ready-made Docker container:

Appium & Robot Framework: Record Test Execution

Lenni Ojala — Fri, 24 Jul 2020 12:18:07 +0000

The latest release of the Robot Framework's Appium Library introduces keywords for recording a video of the Appium test execution in iOS and Android phones.

Instructions for use:

If test is run in iPhone, install ffmpeg in the Mac where Appium is running: brew install ffmpeg
Simple use case: Use Appium Library's keyword Start Screen Recording in the Test Setup and Stop Screen Recording in the Test Teardown. Recording is stored in the same place where Robot test case reports are. Video file is not stored permanently to the storage of the phone.
Error-proof use case: Some Android phones (for example Huawei models) are not capable of recording the screen and the test case will fail (in the latest Appium library 1.5.0.4 - this might change in the future). It is a good idea to start and stop recording using a keyword Run Keyword And Ignore Error (remember also import BuiltIn library for the Robot Framework code). Here's an example of this error-proof case:
Storing recording only for failed tests: Here's an example code that stores screen recording only when a test case fails:

Viewing videos

For Android recordings, file format is .mp4 that is easy to open with many tools. For iOS, file format is .ffmpeg. To view ffmpeg videos, use ffplay in the command line (in a computer where ffmpeg is installed):

ffplay appium-screenrecord-10.ffmpeg

Free word

In my opinion, this example showcases nicely how the use of readily available Robot Framework libraries reduces the amount of test automation code (and thus less maintenance and bugs in it!). Capturing video of the screen is now only a few simple lines of code, whereas file handling using native Appium would require more logic.

How many mistakes can you spot in this exercise?

Lenni Ojala — Mon, 13 Jul 2020 12:56:16 +0000

Content warning: This post contains sexist material that might make your brain melt.

Update (June 2020): Course provider has promised to change the wording of their exercises! That is great!

I could not believe my eyes when I saw this programming exercise on a C++ course that is widely offered in Finnish Universities.

How many mistakes can you spot here?

“Write a program that asks the users gender and age. Finally the program prints a sentence based on the following rule:

Male 0-55 years: “You are a man in his prime!”

Male 56-100 years: “You are a wise man!”

Female 0-55 years: “You are like a blooming flower!”

Female 56-100 years: “You look young for your age!”

Else “Error encountered!” Age is handled as an integer variable and gender as string variable (m/f). Letter case is ignored.”

And if someone does believe this is true, here's a screencap of it:

This might be some wicked way of pointing out sexism in IT industry. In my opinion, simply, not cool!

Book review: It’s About Damn Time

Lenni Ojala — Sat, 02 May 2020 06:59:17 +0000

Heuristics: If I can concentrate on reading a business book during the great lockdown of 2020, it must be good!

And yes, Arlan Hamilton's unexpected journey (It's About Damn Time, 2020) to venture capitalist, was a catching read. She started with her resourcefulness and practically without any money, and is now investing in high-potential founders who are people of color, women, and/or LGBT.

Arlan writes that she wrote this book for mentoring others like her - the book is for anyone, who wants more than society has allotted for them. Book is also for allies - for those who want to understand how diversity can be our greatest superpower.

And yes, I did get mentoring. And what was great - advice given in the book didn't felt patronising (that is something I find difficult in some self-help books). Arlan's story is about being resourceful and honest and building on top of what you already have. She gives insights into many topics, such as how to handle getting no's, stage fright, importer syndrome, substance abuse, taking care of yourself, and what venture capitalists are looking for when they make their investment decisions.

The book is funny, and also very queer. I felt warm feelings when seeing chapter "Shane is my homegirl" (Shane is one of the main characters in the iconic TV show The L Word that was aired when I came out from my lesbian closet in the mid-2000s):

To whom I recommended the book:

To someone, who is dreaming of going big and longes for an inspirational read
For those, who know their privilege and are maybe little ashamed of that. Book does not shame or blame but gives insights into how that privilege can be used for good.

To read more reviews, check Goodreads.

(I got my copy of the book by participating in a book launch team.)

Full Stack Open - Reflections of the Course

Lenni Ojala — Sun, 05 Jan 2020 06:48:00 +0000

Full stack open is a free online course organized by University of Helsinki and some top-notch Finnish companies. Stack is very up-to-date: single-page-app development using latest React, Redux, Node.js and MongoDB and course contains also GraphQL tutorial. I attended to the 2019's course and completed 7 ETCS credits (this corresponds to 189 hours of work - it is also very close to what I actually used!).

What I enjoyed the most in the course:

Course was very practical - it introduced many npm packages, browser extensions and Node scripts, VSCode editor plugins and programming practices that ease the development.
Sometimes when doing the first exercises of a topic I felt like "oh-no, this coding style hurts my soul", but then in the end, same exercises were revisited and refactored according to the current best practices. So course really promoted understanding of the stack.
Course included lots of well curated links about the topics, so it was easy to find extra information. Students were also encouraged to make pull request to the material, if they felt that something could be included.
Exercises covered unit testing using Jest/React Testing Library and E2E testing using Cypress. I am especially happy for the Cypress part! In addition, this is the first time when I really got a grab of a functional programming (this is definitely something that'll be needed when writing more Cypress tests).
Discussion in the course Telegram community was supporting and friendly and course lecturer Matti Luukkainen was very active there. So if you get stuck, there is knowing, that help is available. Tone of the voice in the course material was encouraging and often hilarious (example below):

To whom I would recommended the course:

Someone, who has gained solid programming knowledge but is stuck to tutorials and tiny projects - after this course you will know how to create full stack web applications and host those online. Problem solving skills promoted in this course make it even possible to obtain new stack (such as React Native).
Someone, who is already working in the industry and wants to get working knowledge about latest React/Redux/Node.js and shape their Javascript (ES6) skills and the ways of working.

There will be new course on 2020 (it starts on 15th of March). Revised course contains new section about TypeScript. In the meanwhile, current course is still online.

I would love to hear your experiences of the Full Stack Open! Have you benefit from it professionally? Or are you planning to take it and would like to ask for something?