Supernova Internship Test Report

Introduction

• I’m excited to share that I’ve just finished a 3-month internship with Supernova MGU, where I significantly improved my software QA skills. Supernova is developing innovative insurance software in Canada, and I’m proud to have been part of the team that helped enhance the quality and future user experience of their product.
• Working alongside an awesome team including Daniel Tifft, Myrrh Rachel Hsu, Kristiana Kaila Ingco, Ray Grigolla, Michael Reasoner, Jezer Medina, and Refat Ullah, under the mentorship of Prashant Vaghela and Jonathan Cost, we focused on API and web/mobile UI testing. We operated in an Agile environment with daily stand-ups and weekly team meetings, as well as a final presentation to our stakeholders.
• The internship introduced me to new tools like DrivT for project management and methodologies like charter testing/session-based testing; which greatly improved my approach to complex testing tasks. Over the course of the internship, our team executed hundreds of test cases. I developed strong organizational habits while logging extensive amounts of bug reports in Atlassian Jira by creating structured folders and applying consistent labels.
• My API testing skills grew substantially. We tested several complex API endpoints with a focus on edge cases, valid and invalid input tests while checking HTTP validation and error handling. I learned how to fork collections and create pull requests and utilize pre and post-request test scripts in Postman.
• Going beyond my assigned tasks, I practiced automation in my free time, converting manual API tests to automated scripts using JavaScript, Axios, and Jest. With collaboration from Kristiana Kaila Ingco, she taught me essential Github version control techniques and introduced me to efficient coding practices, such as importing constants and using 'before' hooks for repetitive tests. This collaboration not only sharpened my automation skills but also gave me practical experience in teamwork.
• What I valued most was the chance to work in a professional agile environment, with a really motivated team while meeting real deadlines and expectations. The practical application of my theoretical knowledge was also super rewarding.
• While I’m sad to see the internship end, I’m stoked about applying these new skills in my future QA career. I would like to extend my thanks to Supernova MGU and TripleTen for this opportunity to be a part of enhancing their awesome software!

Tester Information

Name: Ryley Johnson

Date: Aug-Oct 2024

Video Demonstration

Disclaimer: Some scenes in this video have been blurred/redacted to maintain privacy.

Focus Areas

• API Testing: Backend API testing for cal_carrier_remmitance and ping endpoints
• UI Testing: Frontend exploratory testing for Leads Management/Kanban Board (broker space)
• UI/UX Testing: Mobile device exploratory testing

Test Results Summary

Detailed Test Analysis

Cal_carrier_remmitance API Testing

Endpoint Parameters: carrier_id(string, requires uppercase), transaction_date(string, format: "YYYY-MM-DD")

Key Findings

• Most failures involved HTTP response code inconsistencies
• Expected HTTP 400 Bad Request
• Received HTTP 500 for invalid inputs
• transaction_date parameter showed the most issues
• Notable edge case: Date format with misleading zeros (2024-9-01)
• Postman: Returns 200 OK
• Automated testing: Returns 400 Bad Request
• Inconsistency remains unresolved

Ping API Testing

- Limited test cases executed

- Potential for expansion into security testing (SQL injections)

Leads Management/Kanban Board Testing

Primary Issues

• Filtering functionality problems
• Lead count discrepancies between kanban board and backlog
• Inconsistent drag-and-drop functionality

Mobile UI Testing

Key Issues

• Web-app download prompt issues:
• Pixelated app launcher icon ("Covera")
• Multiple clicks required to launch
• Initial 404 error page
• Small home link button for web-app access
• Limited testing scope due to time constraints

Recommendations

Technical Improvements

1. Enhance error handling for invalid requests
2. Implement user-friendly error messages
3. Conduct comprehensive mobile testing
4. Establish clear frontend functionality requirements

Specific API Recommendations

Error Response Enhancement

- Current issue: Complex error messages with stack traces

Disclaimer: The following error response is a generic example and has been modified to protect the privacy of the company's data.

{
                "error": "single positional indexer is out-of-bounds",
                "stackTrace": "Traceback (most recent call last):\n  File \"/path/to/api/file.py\", line 48, in http_trigger\n    response = temp_df.iloc[0].to_dict()\n               ~~~~~~~~~~~~^^^\n  File \"/path/to/library/file.py\", line 1191, in __getitem__\n    return self._getitem_axis(maybe_callable, axis=axis)\n           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^\n  File \"/path/to/library/file.py\", line 1752, in _getitem_axis\n    self._validate_integer(key, axis)\n  File \"/path/to/library/file.py\", line 1685, in _validate_integer\n    raise IndexError(\"single positional indexer is out-of-bounds\")\nIndexError: single positional indexer is out-of-bounds\n"
            }

- Recommendation: Implement user-friendly error messages

French Character Support

- Current behavior: Returns HTTP 400 for carrier_id with French accents

- Recommendation: Add support for French accented characters given Canadian service context

Date Handling Logic

- Current issue: Inconsistent start_date_inclu values

- Example: transaction_date of 2030-04-15 returns start_date_inclu of 2024-01-01

- Recommendation: Review and align date logic with business requirements

- My understanding of how this API is supposed to work is somewhat limited, but based on my assumption, for example, if I set a transaction_date of 2030-04-15, the start_date_inclu in the results should not be before that. However, when I tested this, I set the transaction_date to 2030-04-15, but the API response returned a start_date_inclu of 2024-01-01. Because of this assumption, I wrote a new postman pre-request and post-request script.

Final Conclusion

Testing the Supernova API and UI of the webapp was an excellent experience for the entire team. In this project, the API and UI testing efforts revealed significant areas of both success and improvements. While the platform demonstrated reliable handling of requests, a notable number of failed assertions and defects, particularly in error handling and validation were identified. The exploratory testing on both desktop and mobile platforms also uncovered several usability and functional issues, particularly concerning responsiveness and session management. Addressing these will be crucial for improving the overall user experience and reliability of the platform.