Lundi Dyonta

Key Responsibilities include:

• Drove implementation of quality requirements for new product designs and adherence to customer specifications and production requirements.
• Developed test methodology to check product features and devised test plans for modules.
• Worked closely with Developers and BAs to execute and improve test coverage.
• Participating in design reviews with some of the technical stakeholders such as Architects, Developers, Business Analysts etc.
• Mentoring less experienced staff and consult with peers when a need arises.
• Coordinating every task assigned to me and those of junior team members to meet project schedules.
• Integration, Functional as well as Regression testing where necessary.

Other Responsibilities include:

• Used critical thinking to break down problems, evaluate solutions and make decisions.
• Keeping a Test Lead informed of delays in testing activities or problems arising from variances.
• Demonstrate new product features and functionality to Clients, Managers and Team members

Key Responsibilities Include:

• Participating in design and planning sessions, giving analytical views on the test coverage and test approach.
• Responsible for Identifying tools and environments on/with which to execute tests, but also to set up and configure the environments to simulate production environments
• Responsible for Ensuring efficient and enough documentation that is applicable to a particular project or feature need is in place such as requirement specification, user guides, test specification or any other possible technical documents that could assist both development and QA teams
• Participated in the test case creation which would sometimes be written in an automation framework called cucumber
• Participated in release management processes, from when the project begins to when it is signed off and released in ensuring efficiency.
• Played a pivotal role within an Agile framework to ensure all the right processes are followed and the necessary testing is executed for each feature.
• Contributed to root cause analysis to determine core reason for failures and errors.

Key Responsibilities included:

• Attending meetings with quality assurance, developers and project managers to assess scope and sequence of project.
• Reviewing software requirements and preparing test scenarios.
• Executing tests on software usability.
• Analyzing test results on database impacts, errors or bugs, and usability.
• Preparing reports on all aspects related to the software testing carried out and reporting to the design team.
• Participating in design reviews and providing input on requirements, product design, and potential problems.
• Identifyng bugs and issues within system and applied troubleshooting techniques for mitigation purposes.

Key Responsibilities:

• Participated actively in the development process through the AGILE framework by collaborating with the rest of the development team from the initial phases of development.
• Analyzed application requirements and design documents so that the potential problems can be picked up or identified preemptively
• Responsible for the development of test plans and protocol. Had to ensure all test plans created adhere to both industry regulations and business standards. Once a particular test plan document was completed, the rest of the project stakeholders had to approve and sign it off.
• Execution and documenting of test results was the main responsibility. Tests had to be run and analyzed with findings presented to the relevant stakeholders such as developers and or project managers.
• User Acceptance Testing had to be performed from time to time.

Key Responsibilities:

• Collaboratively worked with QA, development, and business groups to compete testing.
• Performed variety of tests, such as regression, integration, platform to confirm the stability of software systems.
• Responsible for test planning , test case creation and test execution to ensure the system functions in accordance with both technical requirements and business specification.
• Logging, tracking, and reporting on bugs captured through a system called Bugzilla.

• Assisted customers in identifying issues and explained solutions to restore service and functionality.
• Resolved minimum of 10 technical support inquiries per day.
• Monitored systems in operation and input commands to troubleshoot areas such as Data and Non Data Services.
• Cancellation, deferring of faults that are Invalid 'and Clearing those that have been completed and fixed
• Collaborated with field technicians to locate replacement components and resolve advanced problems.
• Escalate quiries for clients interested in new services.