QA Tester Portfolio

Curious about more technical matters like how I document bugs, communicate in Jira tickets, or write emails? Look below to get a feel for my communication style and attention to detail.

Please Note: These are real examples from my work. Company specific details have been replaced with placeholders.

Skill Name	Skill Type	Skill Level
Writing Automated Tests	Testing and Programming	Beginner
Regression Testing	Testing	Intermediate
White Box Testing	Testing	Beginner
Accessibility Testing	Testing	Beginner
Front End Testing	Testing	Beginner
Functional Testing	Testing	Intermediate
Test Plan and Test Case Creation	Testing	Intermediate
Integration Testing	Testing	Intermediate
User-Centric Testing	Testing	Intermediate
Black Box Testing	Testing	Intermediate
Test Execution	Testing	Intermediate
Exploratory Testing	Testing	Intermediate
Back End Testing	Testing	Beginner
Documentation Management	Tech Writing	Beginner
Team Building	Soft Skills	Intermediate
Leading a Team of Testers	Soft Skill	Intermediate
Intra-Team Communication	Soft Skill	Intermediate
Precision and Accuracy	Soft Skill	Intermediate
Cross Team Communication	Soft Skill	Intermediate
Writing C# Classes	Programming	Beginner
Writing Javascript Scripts	Programming	Beginner
SQL Use and Query Writing	Data	Beginner

Test Case Examples

1 / Item Title

Describe the item and include any relevant details. Click to edit the text.

2 / Item Title

Describe the item and include any relevant details. Click to edit the text.

3 / Item Title

Describe the item and include any relevant details. Click to edit the text.

Jira Bug Tickets

Here's how I set up various bug tickets in JIra.

Null Object Reference Bug

Example 1

Incorrect Calculation Returned from API

Example 2

"Testimonials are a great way to showcase positive feedback you've received. Click to edit and add yours."

Example 3

Misc. Communications

Read below to get a feel for how I communicate in Slack messages, Jira Comments and Emails.

Slack Message Example 1

Hello everybody. I am seeing very strange behavior from the V4 [Endpoint Name] . I am getting Null Object Reference errors in Postman and what appears to be 500+ debug logs but no error logs.

Endpoint: [Endpoint Name]

[Endpoint URL from Postman Test]

BaseUrL(Postman Variable):

[Application URL]

CustomerId: [Id]

AccountId: [Id]

Status Code: 500

Response:

{

"Code": "CommonApplicationException",

"Message": "Object reference not set to an instance of an object."

}

Logs:

[Logging Link]

Email Example 1

Today there were more issues but we worked through them. First, visual studio was not loading the build menu. Unfortunately, it had loaded the solution file as a folder. Once I figured out how to get the build menu back, I still wasn't able to build. With [Developer Team Member 1]’s help, we were able to figure out that it wasn't loading the projects. Once we resolved that I was able to build again.

However, once I was able to build, I ran into the package issue again. [Helpdesk Member] got back to us regarding permissions and saw that I already had access in active directory. So there was another issue. [Developer Team Member 2] figured it out! I needed to update visual studio to use the shared file as a Nuget package source. Once I added in the shared file location to the package manager, I was finally able to get a successful build. I cannot express how much of a relief that was.

Since it was later in the day, I was not able to get as much testing done but I anticipate having this ready for merge by tomorrow. Also, I identified some updates that I need to make to the test cases to make them more useful and clear for the next tester. I completed the changes on one of the test cases and I will copy it over to the other 4.

However, I am happy to record that the [Endpoint Name] passed local testing.

Jira Comment Example 1

Today there were more issues but we worked through them. First, visual studio was not loading the build menu. Unfortunately, it had loaded the solution file as a folder. Once I figured out how to get the build menu back, I still wasn't able to build. With [Developer Team Member 1]’s help, we were able to figure out that it wasn't loading the projects. Once we resolved that I was able to build again.

However, once I was able to build, I ran into the package issue again. [Helpdesk Member] got back to us regarding permissions and saw that I already had access in active directory. So there was another issue. [Developer Team Member 2] figured it out! I needed to update visual studio to use the shared file as a Nuget package source. Once I added in the shared file location to the package manager, I was finally able to get a successful build. I cannot express how much of a relief that was.

Since it was later in the day, I was not able to get as much testing done but I anticipate having this ready for merge by tomorrow. Also, I identified some updates that I need to make to the test cases to make them more useful and clear for the next tester. I completed the changes on one of the test cases and I will copy it over to the other 4.

However, I am happy to record that the [Endpoint Name] passed local testing.