Alesh Dulal

I tend to describe myself as a QA professional in a developer's body, having the mindset to break things but the toolset to create and restore. I have more than 6 years of experience as a QA Engineer who mainly emphasizes manual testing but also with a habit of automating the required tests.  Well-versed with all types of testing and tools.

Mainly, I focus on (Black-box-testing, Gray-box testing, Performance-testing, Test plan creation, Test case design and writing, Bug reporting, Communication with team members, Documentation with a detailed report, and Creating user guides for applications).

I have hands-on with the following responsibilities:

1. Creating QA procedures for a project

2. Develop test plans based on requirements, specifications, and test techniques

3. Writing acceptance criteria on scenario-oriented and rule-oriented methods

4. Using scenario-oriented and rule-oriented methodologies to write acceptance criteria

5. Manual or automated testing, depending on the requirements

6. Reporting the bugs found with detailed replication steps and bug tracking

7. Creating detailed bug reports and incident reports

8. Participating in backlog grooming with the team and product owners

9. Putting effort into sprint planning, spring grooming, and sprint finalization.

10. Using tools like Jira and Confluence for requirements as well as sprint tracking

11. Effective test data preparation

12. Using SQL Queries to make essential data modifications to debug database issues

13. Performance testing with Katalon Studio, Jmeter, or Locust

14. Performing API Testing using Postman

15. Synchronizing branches, merging branches with Git

16. Deploying branches to different test servers

17. Server log monitoring

I am following this process during my Testing:

1. Review software requirement specifications.

2. Creating the test plan

3. Creating the test cases of all the features including functional as well as non-functional test cases

4. Perform testing based on the test cases prepared.

5. Complete the system test.

6. Report the bugs found in a proper format. Basically in Jira or any preferred tools

7. Retest bugs after the fixes are done by the developer

8. Write a test completion report.

9. Perform regression testing before each release into production.

10. Perform sanity testing on the build after release.

I have hands-on with the following tools:

Functional Automation: Selenium Web Driver, cypress, Katalon Studio.

Mobile Automation: Appium.

API Testing: Postman, Katalon Studio

Performance Testing: Jmeter, Locust

Progress Tracking: Jira and other tracking tools like Trello, Asana, Redmine, monday.com

Other optional experience

Version Control: Git and GitHub

SQL Queries

Javascript & Frameworks

I can ensure the quality of software while leveraging my coding abilities to build and utilize different testing tools. I am proficient in all stages of the QA process from test planning to post-release verification. Throughout my QA career, I have worked in many different environments, following methodologies of Agile like SCRUM and KANBAN.

I grow up in an environment where I can test the boundaries of the software but also contribute to the QA process and procedures used to ensure quality. QA is my passion and I would like to help whoever will find my skills suitable for their projects.