Eyup Y.

Was responsible for testing the desktop and mobile application called Horizon; it was a farm management platform that allowed farmers to manage their daily work; it displayed information and data coming from Lely robots in farms across the world; robot simulators were used to execute test cases.

• Featured and user stories planned during PI Planning and Scrum Planning were tested;
• Test cases were created using Target Process and were discussed for their automation feasibility;
• Frontend and backend test cases were automated to assist test automation engineers;
• Virtual machines were used for test execution;
• Bugs and defects were created and tracked using Target Process;
• Functional, end-to-end, regression, re-test, and integration test types were applied;
• Support was provided during the UAT process to improve customer satisfaction;
• Testing Chapter meetings were organized to discuss and improve testing processes;

• Followed all Scrum and SAFe rituals for epics and user stories;

• Conducted QA review processes before developing new features;

• Provided comments on user stories to clarify potential misunderstandings;

• Executed automated regression test cases before starting release or user story test execution;

• Halted release or user story test execution if critical functionality was compromised during automated regression testing;

• Created and executed test cases for manual testing based on User Story Acceptance Criteria;

• Logged bugs for any anomalies detected during functional testing;

• Determined the priority and severity of bugs upon creation;

• Performed bug re-tests after code fixes were implemented;

• Clarified misunderstandings about bugs and user stories during refinement meetings;

• Automated manually created frontend test cases and integrated them into the test automation suite;

• Updated automation test cases as needed to align with Acceptance Criteria;

• Executed manual and automated regression test cases at the end of every release cycle;

• Ran automated smoke test cases after release completion.

• QA-processerna dokumenteras, implementeras och körs från grunden enligt principerna agile och scrum.
• Testfallen skapas, granskas och körs för webbappar från plattformen Rally.
• Sedan körs testerna Integration, Sanity och Regression Defekter rapporteras, prioriteras och spåras från plattformen Rally.
• Webb-API:er automatiseras med hjälp av Java, Cucumber, Postman, RestAssured, TestNG och hamcrest.
• CI/CD-processer och distribution av producerande och icke-producerande miljöer körs av testingenjören, release managern och mig.
• Testskript för automatisering skrivs med hjälp av Selenium WebDriver för webbplatser med språket Java.
• Jag har erfarenhet av följande koncept inom testautomatisering: lokaliseringstekniker, identifiering av objekt, automatisering av nedrullningsbara menyer, kryssrutor, radioknappar, java-meddelanden och hantering av flera fönster och ramar.

• Ansvarig för design och körning av testfall för webbaserad lokal terminalprogramvara som används för underhåll och som simulerar basstationen.
• Design av testfall och körning görs enligt dokumentet med kravspecifikationer.
• Säkerhetstester görs med olika typer av testverktyg.
• Nya programvarupaket installeras i testmiljön via Jenkins.

Eyup's career began at Huawei as a Senior QA Engineer. In the second year, he was assigned the role of Test Team Lead.

His responsibilities encompassed a wide range of critical tasks, including:

• Designing and executing test cases for web-based Local Maintenance Terminal (WebLMT) software, a simulation of the base station, based on requirement specification documents;

• Performing security testing using various security testing tools to ensure robust system defenses;

• Conducting integration testing to ensure seamless functionality across multiple teams involved in the WebLMT project development;

• Installing new software packages in the test environment via Jenkins to maintain up-to-date systems;

• Testing APIs manually using Postman and automating them with advanced test automation tools;

• Monitoring the accurate and timely execution of feature and regression test cases to maintain quality standards;

• Leading the Test Team, managing people effectively, and ensuring successful analysis of issues and bugs reported by users from different countries;

• Contributing to capacity planning and workload distribution to optimize team efficiency;

• Ensuring adherence to all scrum rituals for epics and user stories to maintain alignment with agile practices.

• Sköter SDLC för försäljning av livförsäkringsprodukter genom Akbank och Odeabank.
• Process för programvarutestning.
• Utveckling, analys och processer för testhantering följs i verktyget Jira.

The product owner prioritized the development of mobile banking application requirements using Agile/Scrum methodology.

A test planning meeting was held every two weeks to determine the project to be tested and size the test effort. Tester handshakes were held with the Product Owner, Business Analyst, Developer, and Business Unit to determine the scope of the test. A weekly test grooming meeting was held to discuss upcoming projects' test plans.

When starting to work on the project, Eyup examined the business unit-approved analysis document containing content about the different functions of the Akbank Mobile App and completed the testing analysis process. Afterward, he created a test case template.

The daily responsibilities included:

• Writing detailed manual test steps using Microsoft Team Foundation Server (TFS) to ensure comprehensive test coverage;

• Creating keyword-driven automation test steps with the SilkTest tool, preparing them for execution;

• Preparing test data for specific projects using the Oracle database tool AQT (Advanced Query Tool);

• Initiating the test run process as soon as the smallest testable component of the business project was ready;

• Verifying table records by checking the relevant cells to ensure data accuracy after test case execution;

• Reporting detected defects or bugs to the assigned developers through Microsoft TFS for prompt resolution;

• Verifying fixed defects or bugs to ensure all issues were addressed as specified in the analysis document;

• Generating detailed test result reports upon completion of the assigned project tests.

• Prepared analysis for assigned mobile and internet projects;

• Created test data for specific projects using Oracle Database and the SQL Navigator tool;

• Conducted data analysis, performed testing, and resolved problems efficiently;

• Researched technology solutions and presented recommendations to enhance system performance;

• Tested applications and resolved complex issues throughout the software development life cycle (SDLC), preparing detailed program specifications;

• Played an active role in design and development activities to ensure alignment with software requirements;

• Collaborated with clients and vendors to resolve day-to-day issues and implement process improvements;

• Maintained and updated technical documentation for software and systems to ensure accuracy and usability;

• Contributed to technical team activities throughout the product lifecycle, including design, modeling, testing, and documentation.