dsp-dr/guile-nimbus

Test: Example projects functionality

Open

#5 opened on Aug 20, 2025

View on GitHubContributor guide
 (0 comments) (0 reactions) (0 assignees)Scheme (1 fork)auto 404
examplesgood first issueintegrationtesting

Repository metrics

Stars
 (0 stars)
PR merge metrics
 (PR metrics pending)

Description

Description

Test the example projects to ensure they work and demonstrate real functionality.

Examples to Test

  • Web App Example (examples/web-app/)

    • Follow the README setup instructions
    • Test API endpoints
    • Verify file upload functionality
    • Test environment switching

  • Microservices Example (examples/microservices/)

    • Test service discovery
    • Verify load balancer configuration
    • Test inter-service communication
    • Validate monitoring setup

Tasks

  • Create test environments for each example
  • Follow all setup instructions exactly
  • Test all claimed functionality
  • Verify LocalStack integration works
  • Document any issues or improvements needed

Expected Outcome

  • Examples work as documented
  • Real-world usage patterns are validated
  • Any gaps between claims and reality are identified
  • Examples serve as good learning resources

Resources

Skills Needed

  • Infrastructure concepts understanding
  • API testing (curl, Postman, etc.)
  • Following complex setup instructions
  • Integration testing mindset

Perfect for validating our real-world examples!

Contributor guide

Research direction
Set up each example project following the README, then execute the test scenarios (API endpoints, file upload, service discovery, load balancer configuration, inter service communication, monitoring setup, LocalStack integration) and document any issues or improvements found.
Tech stack
None
Domain
testingbackend
Issue type
Test
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitBasic understanding of infrastructure concepts
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75