0chain / 0chain/system_test

Compare 0box tables with sharder tables for a particular round in the very end

Abierto
#1,069 0 comentarios 0 reacciones 1 asignado Reclamado por @shohan2001 Ver en GitHub
Lenguaje dominante
Go
Estrellas
8
Forks
6
Métricas de merge de PR
Sin PR fusionados en 30 d

Descripción

We migrated 13 tables from 0chain and 0box and building them from events in 0chain using kafka : ` -t blobbers -t validators -t miners -t sharders -t authorizers -t blobber_snapshots -t validator_snapshots -t miner_snapshots -t sharder_snapshots -t authorizer_snapshots -t users -t user_snapshots -t provider_rewards` .

To make sure the data is consistent and is not breaking, we need to write tests to compare the data in the end of system tests run. We have 2 approaches to deal with it :

1. We should have multiple endpoints to share all the fields of all the tables above on both 0chain and 0box. If some fields are missing then we can add them as test endpoints.
2. We can just create 2 endpoints that can return us the result of db query. We can use it to get and compare data of all fields and run them only when network is deployed on test mode.

We can discuss more ideas or use hybrid approach as well.

Guía de contribución

No hay ninguna guía de contribución indexada para este repositorio

Línea de trabajo

The issue involves comparing data between 0chain and 0box tables for 13 migrated tables (blobbers, validators, etc.) after system tests. First, examine the existing system test codebase to understand the current test structure and database setup. Identify the endpoints or queries needed to fetch table data from both sources. Determine how to implement comparison logic, possibly via new test endpoints or direct database queries, and ensure it runs only in test mode. Verify consistency by checking all fields across the listed tables.

Escrito por el modelo de indexación a partir del texto del issue.

Evaluación

Stack tecnológico
go, kafka, postgresql
Área
backend, databases, testing
Tipo de issue
Nueva funcionalidad
Dificultad
4/5
Tiempo estimado
3-5 días
Estado de actividad
Estancado
Claridad
Bastante claro
Aptitud para principiantes
35/100

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.