influxdata / influxdata/influxdb

Write a new set of E2E tests exercising the v3 write API

Open
#25,035 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

v3
Dominant language
Rust
Stars
31.7k
Forks
3.7k
Avg merge
13h 37m
Merged PRs (30d)
8

Description

This issue has no description.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the existing E2E test entry point and the v3 write API, then determine which write scenarios the new test set should cover. The issue is complete when those agreed scenarios have reliable passing E2E tests.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
api, databases, testing
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.