Aki Saukko Email and Phone Number

Test lead for high accuracy GNSS products. Testing new features, helping developers to debug issues, accuracy and other KPI testing. Support for customers, helping to solve customer issues.

Testing all areas of UNA Ydin, a AWS cloud-based system, which is fetching and displaying clinical data (social care and health care) and demographic data from various source systems. My responsibilities include API testing for multiple different APIs, debugging and solving issues in the system, solving integration issues with endpoint from different vendors, developing Soap and Rest mocks, deploying new features and fixes via Gitlab into different testing environments.https://unaoy.fi/una-ohjelmat/una-ydin/

Web shop test automation development and manual testing. Planning and implementing test automation with robot framework for web shop. Testing new features and fixes for web shop frontend and backend. Doing regression testing for web shop in system level. AWS statistics and logging testing and AWS alert settings testing.

Mobile application test automation. My tasks included planning and implementing test suites for Android and iOs applications using Robot Framework and Appium. Implementing automation libraries (Python) with Selenium for automated account handling, email verification and manual credit card acceptance etc. Integrating test automation as part of CI process in CircleCI. Implementing Python tool to add coupons in production database. Planning and implementing API tests in system level so that all system level testing than can be done with Android and iOS apps could be made via APIs also.

I planned and implemented tool for customer to migrate data from Excel data sheets to QCP application in Salesforce using QCP application UI. Tool was made in Python and it used selenium libraries for web UI automation.

I was helping integration architect to find out root causes for issues between integrations of different vendors and components. I made lot of system level log analysis and system level process analysis.

I was working in two different projects. In one project I developed web UI test automation and made system testing for service that integrated machinery devices with web-based control UI. I also set up the Linux based local environment for that system. In the other project I studied possibilities for Qt application test automation. I planned and implemented test automation using Robot Framework with qtwebdriver as webdriver. I ramped up test automation process for that QT application in Bamboo CI environment

When Microsoft acquired phones business from Nokia I was transferred to Microsoft also and continued my career in field testing area.In this work I'm very much involved in every area related to testing. I'm doing field test planning for products programs including all phases from new technologies ramp up in R&D phase to maintenance testing for released products. I'm also doing all test case development and test asset maintenance. Most of the test execution is done by sub-contracted test teams around the world. I'm responsible of doing the test schedules to external test teams and I'm also doing specific test sets for those teams.I'm doing test execution for new technologies (VoLTE, RCS, etc.) in live networks, but also in NW operators laboratories. Technology testing includes also problem solving to analyse possible root causes of found issues during the testing. I'm also developing and maintaining script based test tools that automates phone setup.Because these has been significant changes in phones business Nokia and now Microsoft is doing there has been also need to do process improvement in many areas. I have been participating to couple of Kaizen workshops representing Field Testing area in part of bigger process. In addition to that I have been driving improvements for Field Test process also.

My visit in user testing area was very short, because Nokia decided to ramp down S60 Symbian platform and start developing phones on Windows Phone platform. Due to these changes field testing activities were ramped up in Tampere site again and I got new start in Field testing area after previous short visit in field testing.During these years I was leading field testing activities for many Lumia phone programs. This work included test planning, test execution, field test project management for Lumia products. I also made test case specification for new platform and also for new technologies, like LTE. I also developed and maintained script based test tools to help testing activities in field.My work contained lot of project management for external teams that were doing most of the test execution all around the world. I was also managing small outsourced local test team in Tampere. I was also responsible of test assets and Field test cars in Tampere site.Field test work was very global and I was working closely with different stakeholders in Nokia and also with external stakeholders working in different NW operators. I travelled quite a lot in my work, because field testing was made globally around the world.

Due big changes company all field testing activities were ramped down in Tampere site and I started to work as a User Test Leader. My responsibilities included user test planning and leading for S60 Symbian phone program. In this position I didn’t do any testing by myself, but I was only managing test activities.

I applied for a Field Test Leader position job in Nokia job market and got that position. Reason to change my job was that I wanted work more with end product instead of only narrow area (data performance). This was also step from technology driven work to product driven work. I also liked to travel in my work which I was doing a lot during the Wimax work and this new position included travelling also.My work included test planning, test execution, and test leading in field test area for S60 Symbian phone product program. My responsibility was that product was tested in live operator networks in relevant market areas. Main focus was in cellular connectivity features, but also navigation applications were under the scope.

Soon after lauch of Wimax Nokia decided that it will focus on LTE instead of Wimax and all Wimax work was ramped down. I got new work in data protocol performance testing area as I was already doing similar testing in Wimax environment. This time testing was done with S60 Symbian devices. I was responsible for test case specification, test planning and test execution. I also setup test environment for end user type of data performance testing.My main task was to find performance bottle necks in code using my test cases and test environment. Most detailed testing was done using Lauterbach ARM debugger which enables to run code in device line by line. My test results and findings were used to optimize code to improve data protocol performance in S60 phones.In daily work our team was using Scrum methods.

Also due to changes in company 3GPP video call work was moved to other organization and I got very interesting opportunity to move to totally different testing area. Platform changed from S40/S60 to Maemo and NW technology to be tested was changed to Wimax which was very new and still totally under development in mobility area.At the beginning I worked with small and intense Wimax proof-of-concept project where I was responsible of test case development based on specification drafts, test execution and test planning. I was also participating to interoperability testing with Wimax NW vendors. I also set up Wimax test environment into our test lab. When doing this work I worked with very close co-operation with Wimax chip vendor, Maemo driver developers, Wimax NW vendors and also standardization people working on draft specification. Main focus in this project was to proof that Wimax technology could be usable technology in mobile devices.After Wimax proof-of-concept work was finished I started to work with product program that was bringing Wimax support in mobile device to market. My work tasks were similar that in previous phase, but this time testing focus was changed to ensure that Wimax is working with good quality in NW operator live NW. This work included lot of travelling since only operator planning to launch Wimax NW during that time was located in USA.

Due to organizational changes in company modem SW testing was transferred to different team and I had opportunity take new responsibilities in 3GPP video call testing. My work tasks includes test environment setup for 3GPP video call testing, test execution, test case specification and test planning. I also did interoperability testing with NW operators, with other 3GPP video call capable phones and office solutions and also with 3GPP video call stack developers.

After my graduation I continued modem SW release testing, but started to focus more on NW protocol testing and HSPA testing for S40 and S60 Symbian phones. I was also responsible of test case specification and test planning for NW protocol testing. I also maintained test lab environment for HSPA testing. Most of the testing was end user type of testing that was done in partially automated test environment. I was also developing automated test control for that test environment. Part of the testing was done against protocol testers. I was using TCL to create new test cases for tester environment.

After my summer trainee period ended I continued working in Nokia and started to do my Thesis work parallel with my other work tasks. My primary work continued to be modem SW release testing, test case specification and test planning. As part of my Thesis work I specified and implemented test environment for Robust Header Compression algorithm. That test environment was running on Linux and it was implemented using C. I finished my Thesis work at April 2005 and graduated from Tampere University of Technology.

I started my career in Nokia as summer trainee while my I was having summer holiday from my studies in Tampere University of Technology. My main work was modem software release testing for bi-weekly modem SW releases for S40 and S60 Symbian phones. My work also included test case specification and test planning for new features which were integrated into modem SW releases. Most of the testing was end user type of testing, but it also included testing against protocol tester.