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.

Looking for hackers with the skills:

qa rest api

This project is part of:

Hack Week 10

Activity

  • about 11 years ago: pkacer liked this project.
  • about 11 years ago: llipavsky liked this project.
  • about 11 years ago: llipavsky added keyword "qa" to this project.
  • about 11 years ago: llipavsky added keyword "rest" to this project.
  • about 11 years ago: llipavsky added keyword "api" to this project.
  • about 11 years ago: llipavsky started this project.
  • about 11 years ago: llipavsky originated this project.

  • Comments

    • llipavsky
      about 11 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
      about 11 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
      about 11 years ago by llipavsky | Reply

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

    • llipavsky
      about 11 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
      about 11 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

    Yearly Quality Engineering Ask me Anything - AMA for not-engineering by szarate

    Goal

    Get a closer look at how developers work on the Engineering team (R & D) of SUSE, and close the collaboration gap between GSI and Engineering

    Why?

    Santiago can go over different development workflows, and can do a deepdive into how Quality Engineering works (think of my QE Team, the advocates for your customers), The idea of this session is to help open the doors to opportunities for collaboration, and broaden our understanding of SUSE as a whole.

    Objectives

    • Give $audience a small window on how to get some questions answered either on the spot or within days of how some things at engineering are done
    • Give Santiago Zarate from Quality Engineering a look into how $audience sees the engineering departments, and find out possibilities of further collaboration

    How?

    By running an "Ask me Anything" session, which is a format of a kind of open Q & A session, where participants ask the host multiple questions.

    How to make it happen?

    I'm happy to help joining a call or we can do it async (online/in person is more fun). Ping me over email-slack and lets make the magic happen!. Doesn't need to be during hackweek, but we gotta kickstart the idea during hackweek ;)

    Rules

    The rules are simple, the more questions the more fun it will be; while this will be only a window into engineering, it can also be the place to help all of us get to a similar level of understanding of the processes that are behind our respective areas of the organization.

    Dynamics

    The host will be monitoring the questions on some pre-agreed page, and try to answer to the best of their knowledge, if a question is too difficult or the host doesn't have the answer, he will do his best to provide an answer at a later date.

    Atendees are encouraged to add questions beforehand; in the case there aren't any, we would be looking at how Quality Engineering tests new products or performs regression tests

    Agenda

    • Introduction of Santiago Zarate, Product Owner of Quality Engineering Core team
    • Introduction of the Group/Team/Persons interested
    • Ice breaker
    • AMA time! Add your questions $PAGE
    • Looking at QE Workflows: How is
      • A maintenance update being tested before being released to our customers
      • Products in development are tested before making it generally available
    • Engineering Opportunity Board


    OpenQA Golang api client by hilchev

    Description

    I would like to make a simple cli tool to communicate with the OpenQA API

    Goals

    • OpenQA has a ton of information that is hard to get via the UI. A tool like this would make my life easier :)
    • Would potentially make it easier in the future to make UI changes without Perl.
    • Improve my Golang skills

    Resources

    • https://go.dev/doc/
    • https://openqa.opensuse.org/api