Error Report: `func describe` Command Testing (LFX Mentorship)

[RayyanSeliya]

Summary

Comprehensive testing of the func describe command identified 15+ issues across 6 categories, with the primary concerns being application panics where invalid, case-sensitive, or empty output formats cause the application to crash with stack traces instead of returning user-friendly error messages; critical data display bugs where the image field is always empty even when the function has a deployed image in Kubernetes, and labels are shown as null or empty objects instead of displaying actual label values; and missing output formatting where XML output lacks newline characters and proper indentation, breaking file output and piping operations. Key findings include the critical bug where invalid format values (e.g., invalid, JSON, YAML, empty string) cause panics instead of graceful error handling; the image field bug where func describe fails to extract and display the actual container image from Kubernetes even though it exists; and the labels bug where deployed functions with labels show null or empty objects instead of the actual label key-value pairs. Additionally, the verbose flag has no visible effect on output, hyphen-prefixed function names are mis-parsed as flags, and error messages use technical Kubernetes terminology instead of user-friendly guidance.

Full Detailed Report : Link to Google Docs - https://docs.google.com/document/d/1sL6Tgg0lOSAkFZFr5LTilfSL3aoxq0ddWvdGh6qcslM/edit?usp=sharing

Resolved Issues

The following issues have been marked as resolved in the detailed report:

(No issues marked as resolved yet)