Sebastian Jakowski

In this entry I want to introduce tool which should be used in each projects. It covers how to install and configure a simple job. First of all I started from installation of jenkins in my local machine (Ubuntu). You can download installation package from official page or use jenkins wiki . As like always I met some problem:  The following packages have unmet dependencies:  jenkins : Depends: daemon but it is not installed As a resolving of it I used command apt-get -f install and next apt-get upgrade . Then we should be able see the page like below on address http://localhost:8080 After unlock and installation some pluggins we should be able to see something like below. Next I added simple job which will check the repository and run command gradle -p nany-server test . The result is on an image below. I think that few of us met with lost jobs definitions. What then? We need to define each job manually again. From my point of view the better option

  Hello and sorry for absence during last weeks. This time was very busy because I had to prepare myself for OCA certification. In this post I want to write few word about: what I've done how it looks what I will improve next time  I've read one book from beginning to the end. It was   OCA Java SE 8 Programmer I Certification Guide MALA GUPTA   I think that it is good book for gain knowledge about base java. There is a lot of examples, very detail description. Form point of exam just reading and making the tests is not enough. The test inside this book are not so easy but they don't cover real exam. Next books which were only source of mock tests: OCA / OCP Java SE 8 Programmer Practice Tests OCA: Oracle Certified Associate Java SE 8 Programmer I Study Guide: Exam 1Z0-808   The mocks in the first position are very easy and so short. In real exam the examples of code was so longer and requires more concentration. During the preparation I was receiving s

As a java developer with more than 3 years of experience I had opportunity of participating in few projects. To be honest only in a last one a testing strategy is on high level.  I encourage you for introduce and put more pressure on testing strategy during a delivery process. As with all new things the beginnings are difficult but I'm sure that it is worth. As almost testers know undermentioned pyramid I need to put it for people who have not seen it. In a big amount of projects we can meet this pyramid in inverted order. What can impact of quality of a system. For example when we have a lot of manual tests it is boring for users and sometimes they can be skipped what can missed bug. So in the lowest level we see the Unit tests and the count of this should be the bigger and on the highest level, there are manual tests. As we can expect the count should of them should be the lowest. A few words about each of them: Unit tests - should be quick and small. They check jus

" Nany " Wymagania: Użytkownik może podłączyć/odłączyć się do detektora wysyłającego powiadomienia. Użytkownik musi zostać poinformowany o dochodzącym dźwięku z pokoju dziecka. Powiadomienia powinny zostać wysłane do wszystkich zarejestrowanych urządzeń. Użytkownik musi zareagować na powiadomienie. Schemat:   Pierwszy etap prac (13.03.2017): [Telefon*] Prosta aplikacja android umożliwiająca odbieranie powiadomień. [Detektor*] Obsługa detekcji dźwięku. *Telefon - urządzenie z systemem android. *Detektor - Raspberry Pi B  wraz z mikrofonem.

Rest API best practices During creating an http api we should remember about few rules. As a API designers we must know how to name our endpoints. When we have a library which contains users and their books. As a collection we should use a plural form of verb like books and users. Below we can find examples of endpoints for certain activity and strict HTTP methods Add new book: /users/{userId}/books/{bookId} POST Get book: /users/{userId}/books/{bookId} GET Edit book: /users/{userId}/books/{bookId} PUT Remove book: /users/{userId}/books/{bookId} DELETE   Status codes 200 OK 201 Created 202 Accepted - request has been accepted but not completed. 204 Non content - the request is correct but no content in response body. 400 Bad request 401 Unauthorized 403 Forbidden 404 Not found 408 Request time out 409 - Conflict - duplicate data or invalid data state would occur. 500 Internal server error 501 Not implemented 503 Service unavailable    I think that above

Witam wszystkich uczestników ;) Od jakiegoś czasu chodziło mi po głowie założenie bloga niestety nie miałem do tego wystarczającej motywacji. Wtedy wpadł mi w ręce artykuł zachęcający do wzięcia udziału w DSP 2017. Myślę, że jest to fantastyczna okazja na powstanie (od dawna planowanego) projektu oraz spróbowania własnych sił w tworzeniu bloga :) Projekt "Nany" Celem projektu jest stworzenie aplikacji zbierającej dźwięk z pokoju dziecka. W momencie wykrycia dźwięku system powinien informować rodziców o zaistniałej sytuacji. Projekt prowadzony będzie w metodologii Agile, a o wszystkich rezultatach oraz zmianach będę informował na blogu. Technologie: Python – aplikacja do zbierania dźwięku i wysyłania sygnału do serwera, Java – implementacja serwera aplikacji.