Moataz Mahmoud Email and Phone Number

Managing a medium size team to increase the test automation coverage for all the CXMM 5 projects.We are using Cypress in JavaScript for automating both frontend (in react) and back-end (Ruby and elixir).

About the product:Upland mobile messaging is a market leader product in mobile messaging world. There are more than 1M user in more than 208 region have access to UMM now.About the job details:In UMM, we are integrating with Open Market as the aggregator to send messages building all the logic around giving the best user-experience for the customer companies.Job Duties:- Managing the test automation plans around the project.- Leading building end-to-end regression plan for UMM - Using Protractor in Typescript(ES6).- Developing performance testing scripts in Locust (1.2.0).- Maintaining the CI pipeline for testing and staging environments - using Jenkins.- Manually testing the new features to be released monthly - managing the workflow using Jira and logging the test results to TestRail.- Automating API tests - using Postman Automated Tests and Swagger.- Maintaining the test environments - with help of Rundeck, Jenkins, and RabbitMQ.

About the product:LeadLander is a web-based application that gives your sales staff access to real-time customer intelligence analytics reports.About the job details:I'm working on create a well-established automated regression plan.To have such a powerful and informative analytics system with all that features in reporting, your system must be extremely enormous. Hundreds of modules, Thousands of APIs, and Millions lines of code. So we need to create automated regression plan to cover all end-to-end scenarios to be run every release reporting the performance of the system. And I'm the responsible to convert every single step of the thousands of the test cases into a corresponding automated test been able to be run automatically every release.Job Duties:------------------ Developed the full end-to-end regression test plan - Using Protractor in Typescript(ES6).- Maintaining the test environments - with help of Docker, MongoDB, Spring Boot (JAVA), and RabbitMQ.- Maintaining the CI pipeline for testing and staging environments - using CircleCI.- Manually testing the new features to be released monthly - managing the workflow using Jira and logging the test results to TestRail.

Responsibilities:-------------------------- Building e2e scripts for the main features of the system. (Protractor & Selenium)- Building load testing scripts for handling users number increase.(JMeter)- Testing new features and releases. (Manual)- Managing the releases of the system and update the new changes. (Jira & Trello)- Testing APIs. (JMeter and Postman)Here are some stories about working in Tqweem.- I joined Tqweem in a moment where they were shifting from outsourcing to in-house development model. I was the first member to join. So I got handed over the system. And then decided to move all the backlog from Trello to Jira for the sake of more features and professionalism. And now Jira is ready and all the tech team is working on it.Secondly, Tqweem is working on revamping the system. The backend from Django to NodeJs and the frontend from Angular 1.0 to React. And I'm highly involved in the revamping process as the testing man in all the revamped components for unit tests, integration tests, and system test.Thirdly, I'm the only testing guy in Tqweem from my moment of join till now. So I'm managing all the testing stuff. CRs, bugs and fixes, documenting the new requirements for the technical team, automation testing (load and e2e testing). And it's a very good and informative experience for me.Finally, I really enjoy working in Tqweem. The environment here is amazing. The work is EXTREMELY Flexible when it comes to attendance and tasks delivery. So I can recommend anyone to join our team. He will really get amused.

Responsibilities: ----------------------- Write automated regression testing plan scripts for the website.- Testing all the APIs.- Agile testing manually the new features.- Documenting the new requirements.- Write detailed bug reports.Used Tools: ----------------- Web automation (Protractor).- Android automation (Appium & Espresso).- Testing API (Postman).- Agile testing, writing the documentation, and bug reports (Jira).

Gained skills are: automation for Android using Appium, automation testing for Angular JS using Protractor, black-box testing techniques, Agile methodology, and QA in DevOps. And here is the complete story ... At xWare we are developing software with passion under the slogan "You can mass-produce hardware, but you cannot mass-produce software; you cannot produce the human mind."xWare mainly has two main business lines. The first is the outsourcing business line. And we have only one partner till now which is @IPMagiX which is a leading software development company with existence in Cairo, Dubai, Riyadh, and US. The second business line is the production business line. In which we are building our own software products. We have an R&D team which is discovering the market and determine which ideas are worthy to be invested in and be applied. And then the development team is working on them.I'm the responsible for testing the applications which are built with our outsourcing partner @IPMagiX. So I'm a member at the outsourcing team.I test some large projects built in C# and Java. Most of the testing stuff were done manually when I joined the team. I was the responsible for starting automating them. I studied and then I'm applying automation with Selenium for automating desktop apps, JMeter for load testing and testing backend services, and Appium for automating mobile tests. I wrote many tests for Android applications using Appium.In addition, I worked as part-time employee on Code Tracer project built by xWare team. Code Tracer is a community for reviewing code. You share your code and get review from experts. I wrote some e2e tests for Code Tracer using Protractor for Angular JS. But our team leader decided to postpone the e2e testing until Code Tracer becomes more rich in features and have many more users, so I stopped writing those tests.