QA Engineer)
Mercedes-Benz Mobility AG(Senior
Total des années d'expérience :8 years, 5 Mois
• All scrum and Safe rituels are followed for epics and user stories
• QA Review process takes place before the development of new feature.
• QAs write their comment to the user story to clarify any misuderstanding.
• Automated regression test cases are executed before release/user story test execution has started.
• If there are bugs in critical functionality during the execution of automated regression test cases, release/user story test execution wont be started.
• Test cases are created and executed against User Story Acceptance Criteria for manual testing.
• Bug is created if there is any anomaly during functional testing.
• Priority and severity for bugs are determined when they are created.
• Bug re-test is performed after the code fix.
• If there is any misunderstanding for the bug and user story, they are clearified during the refinement meeting.
• Manually created test cases for frontend are automatized and added to test automation suite
• Automation test cases can be updated against Acceptance Criteria if there is a need
• Manual and automated regression test case are executed at the end of every release
• Automated smoke test cases are executed after the release has completed.
Project: I am responsible for testing the web application which is called Vehicle Booking System (VBS). Dealers all aroud the world can create booking for rental and test drive through VBS. My team is taking care of calculation of rental booking and its additional services. I am working in the pricing domain
• I have been assigned as a QA Team Lead for one of the web project within the team.
• QA processes are documented, implemented and executed from scratch according to agile/scrum principles.
• QA process are monitored and took actions if neccessary.
• Test cases are created, reviewed and executed for web application as part manual testing
• Integration, Sanity and Regression tests are performed
• Defects are reported, prioritized and tracked from Rally platform.
• APIs for FieldVision application are automated.
• CI/CD processes and prod and non-prod environment deployment are executed by Test Engineer as a Release Manager including me.
• UAT documents are prepared, shared and discussed with stakeholders
• Automation test scripts are written with the help of Selenium WebDriver for Web pages using Java language.
• Locator techniques, identify objects, automate dropdowns, checkboxes, radiobuttons, java alerts, handle multiple windows and frames are test automation concepts that I have already experienced.
• API requests are created and load test is performed for determined number of users using Jmeter
• APIs response time are monitored and created graphs are analyzed
Project: I am responsible for testing web application which is called FieldVision. Engineers in General Electric(GE) use FieldVision application in order to report outages, conditions, alarm of boiler, steam and gas turbine.
I have started my career in Huawei as Senior QA Engineer.
I was assigned as a Test Team Lead in the second year of my career in Huawei.
I desing test cases, execute test cases and also create bugs for user stories’ manual
testing
I also monitor if feature test cases and regression test cases are executed correctly and
on time
As the team leader, I also performed the people management duties of my team.
I take place capacity planning and workload distribution in my team.
All scrum rituels are followed for epics and user stories.
Issues/bugs are analyzed by Test Team that are coming from the users who are
located in different coutries
Several teams are developing the WebLMT project, so integration test is performed.
APIs are testing via Postman manually
APIs are also automatized using test automation tools
New software packages are installed to the test environment via Jenkins.
• I am in the Bankassurance IT team at Avivasa.
• Bankassurance team is responsible for SDLC of Life Insurance products sale through Akbank and Odeabank channel.
• I am taking place of Software Testing Process.
• Bankassurance team uses Agile/Kanban methodology for SDLC.
• Development, Analysis and Test Management Processes are followed by Jira tool.
• Manual Backend and Frontend tests are performed for Insurance Products
Agile/Scrum methodology is used for development of Mobile Banking Application
requirements that are prioritized by Product Owner.
Test planning meeting is held every two weeks to know what project is going to be
tested and to size the test effort.
Tester handshakes with Product Owner, Business Analyst, Developer and Business
Unit about what the scope of test is going to be.
Test grooming meeting is held every week to discuss upcoming projects test plan.
A daily meeting is held to tell us which test was carried out and which impedements
it encountered.
Examine business unit aproved analysis document that has a content about different
function of Akbank Mobile App and complete process of testing analysis.
Create test case template according to the previous examined analysis document.
Write manual test steps using Microsoft Team Foundation Server tool.
Keyword-Driven automation test steps are created using SilkTest tool to make them
ready to run.
Test data is prepared for the particular project using Oracle database tool which is
AQT(Advanced Query Tool).
When the smallest testable part of business project is ready, the test run process is
started.
The relevant cells of the table are checked to ensure that the records take place in
right cell after the test case execution.
Detected defects/bugs are sent to the assigned developer via Microsoft TFS(Team
Foundation Server).
Fixed defects/bugs are controlled and make sure all of them are fixed as it is written
in the analysis document.
Test result report is generated when the whole assigned project tests are done.