Skip to content

fix: update to new lvt testing API#7

Merged
adnaan merged 2 commits intomainfrom
fix/lvt-testing-api
Nov 30, 2025
Merged

fix: update to new lvt testing API#7
adnaan merged 2 commits intomainfrom
fix/lvt-testing-api

Conversation

@adnaan
Copy link
Copy Markdown
Contributor

@adnaan adnaan commented Nov 30, 2025

Summary

  • Updated test files to use the new lvt testing API
  • Changes affect avatar-upload, counter, and todos test files

Test plan

  • CI checks should pass

🤖 Generated with Claude Code

Update all examples to use the new lvt testing API:
- StartDockerChrome now returns error instead of *exec.Cmd
- StopDockerChrome now takes (t, debugPort) instead of (t, cmd, debugPort)

This aligns with the latest lvt/testing package changes.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
Copilot AI review requested due to automatic review settings November 30, 2025 06:01
Copy link
Copy Markdown

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR updates three test files to use the new lvt testing API for Docker Chrome container management. The main change is in the function signatures: StartDockerChrome now returns an error instead of a command object, and StopDockerChrome no longer requires the command object parameter.

Key Changes

  • Updated StartDockerChrome to check for errors instead of capturing a command object
  • Simplified StopDockerChrome calls by removing the command object parameter
  • Added proper error handling with t.Fatalf for Chrome startup failures

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated no comments.

File Description
avatar-upload/avatar-upload_test.go Updated Docker Chrome API calls with new error handling pattern
counter/counter_test.go Updated Docker Chrome API calls with new error handling pattern
todos/todos_test.go Updated Docker Chrome API calls with new error handling pattern

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

The previous commit assumed the new lvt testing API was published,
but the new API (StartDockerChrome returning error, StopDockerChrome
taking 2 args) is still unpushed in the local lvt repo.

Reverting to the published API:
- StartDockerChrome returns *exec.Cmd
- StopDockerChrome takes (t, cmd, debugPort)

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
@adnaan adnaan merged commit a7e4893 into main Nov 30, 2025
7 of 9 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants