- 
                Notifications
    You must be signed in to change notification settings 
- Fork 12
Add e2e tests for Prefix #161
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
2d80bf7    to
    f0beacd      
    Compare
  
    | The happy path written are 
 | 
4ca1f10    to
    a299551      
    Compare
  
    | The e2e test run is consistently running around 8.5 min (https://github.com/netbox-community/netbox-operator/actions/runs/12273670479/job/34244939819?pr=161) The main time is spent on setting things up... | 
62c84ed    to
    458cfb2      
    Compare
  
    | @bruelea commented that we shouldn't load demo data for e2e tests | 
| 
 This is a lot more work than expected, since we need to extract the minimal tables to set up, etc. Propose to have it done in a follow-up PR. WDYT? Thanks | 
c6692ee    to
    7217ad1      
    Compare
  
    7217ad1    to
    275a9af      
    Compare
  
    There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice work! Great to be able to test against an NetBox instance in the kind cluster.
Mainly focusing on IPv4
Leveraging Chainsaw, we can easily write e2e tests for the NetBox operator, testing directly against the NetBox instance
This PR focuses solely on the Prefix and PrefixClaim, happy path.
Implements #163