REST API for QADB
a project by llipavsky
Updated almost 2 years ago. 2 hacker ♥️.

QADB is the database used to strore results of automated tests in SUSE QA.

It only has web intrface, which is mostly just a better DB view. The goal of this project is to create the REST API to it, which can later be used to query for results from external tools (and maybe even later used by the frontend)

Goal 2 of this project for me is to learn node.js.

Join this project

Looking for hackers with the skills:

qa rest api

This project is part of:

Hack Week 10

Activity

  • over 7 years ago: pkacer liked REST API for QADB
  • over 7 years ago: llipavsky liked REST API for QADB
  • over 7 years ago: llipavsky added keyword "qa" to REST API for QADB
  • over 7 years ago: llipavsky added keyword "rest" to REST API for QADB
  • over 7 years ago: llipavsky added keyword "api" to REST API for QADB
  • over 7 years ago: llipavsky started REST API for QADB
  • over 7 years ago: llipavsky originated REST API for QADB


    • Comments

    • llipavsky
      over 7 years ago by llipavsky | Reply

      day 1: learn node and express basics

      day 2: created part of r/o api

      day 3: decided it is wrong way, delete work of day 2 and start to learn sequelize ORM ;-)

    • llipavsky
      over 7 years ago by llipavsky | Reply

      day 3.2 after 2.5 hours reading documentation, I found that sequelize ORM will not help, since it requires to have PKs named 'id' for relations... So next two candidates are node-orm2 and jugglingdb

    • llipavsky
      over 7 years ago by llipavsky | Reply

      day 3.3 after playing with other ORMs, I decided to give sequelize a second chance...

    • llipavsky
      over 7 years ago by llipavsky | Reply

      day 4: sequelize is actually cool, only surprise was that some features in the documentation works only in git master and not in released npm package. Luckily it took just about 20 minutes to realize... I am getting better ;)

    • llipavsky
      over 7 years ago by llipavsky | Reply

      day 5: So, some part is done, but not yet usable. Next steps would be define how exactly it should look like. Also possibly to add some write support (currently only reading possible...)

    Similar Projects

    Predictive test selection for SUSE Manager by jordimassaguerpla

    I once had a bad dream.

    I started good, a su...

    Zero Trust vSphere Provisioning from Rancher by wjimenez

    Currently, when Rancher tries to provision a Ku...