QA Dashboard - provide a easy overview of the quality status of a product in development
a project by xgonzo
Updated over 4 years ago. 4 hacker ♥️.

QA uses a dashboard (SUSE internal: http://qa.suse.de/dashboard/ ) to provide an overview of various data to assess the quality of a product.

The project is about improving the available data points and the usability for users outside of QA department.

  • improved navigation
  • structure data in blocks
  • make the view more interactive (provide most important data initially, open/close blocks as needed interactively)
  • review the data points we fetch from Fate, Bugzilla, Testopia

Longer term

  • we can add authentication and role based access, which would enable us to provide an instance for opensuse.org

Join this project

Looking for hackers with the skills:

quality qa php bugzilla fate testopia metrics quality-standards javascript ajax sqlite css css3 html5 html

This project is part of:

No hackweek.

Activity

  • over 9 years ago: dmaiocchi liked this project.
  • over 9 years ago: sebchlad liked this project.
  • over 9 years ago: maritawerner left this project.
  • about 11 years ago: xgonzo added keyword "css" to this project.
  • about 11 years ago: xgonzo added keyword "css3" to this project.
  • about 11 years ago: xgonzo added keyword "html5" to this project.
  • about 11 years ago: xgonzo added keyword "html" to this project.
  • about 11 years ago: sunyan joined this project.
  • about 11 years ago: abonilla liked this project.
  • about 11 years ago: maritawerner disliked this project.
  • about 11 years ago: maritawerner liked this project.
  • about 11 years ago: maritawerner joined this project.
  • about 11 years ago: xgonzo added keyword "javascript" to this project.
  • about 11 years ago: xgonzo added keyword "ajax" to this project.
  • about 11 years ago: xgonzo added keyword "sqlite" to this project.
  • about 11 years ago: xgonzo added keyword "php" to this project.
  • about 11 years ago: xgonzo added keyword "bugzilla" to this project.
  • about 11 years ago: xgonzo added keyword "fate" to this project.
  • about 11 years ago: xgonzo added keyword "testopia" to this project.
  • about 11 years ago: xgonzo added keyword "metrics" to this project.
  • about 11 years ago: xgonzo added keyword "quality-standards" to this project.
  • about 11 years ago: xgonzo added keyword "quality" to this project.
  • about 11 years ago: xgonzo added keyword "qa" to this project.
  • about 11 years ago: xgonzo liked this project.
  • about 11 years ago: xgonzo started this project.

    • All Activity

    Comments

    • sebchlad
      over 9 years ago by sebchlad | Reply

      have you seen this one: https://hackweek.suse.com/14/projects/1706? Perhaps the ultimate goal is similar? should we somewhat collaborate on this?

    Similar Projects

    Impove Tracking Milestone Quality by rtsvetkov

    Description

    We need to track better the milestone quality.

    Goals

    Propose a transparent process for managing the Milestone-relevant bugs in Bugzilla. - Transparency on the delivery - Clear current Responsibility - Clear TPM responsibility - Clear current assignee

    Resources

    No special resources Bugzilla,

    Questions to answer:

    What is the best way to track the responsibilities on the tickets, including those of the technical project managers, developers, and subject matter experts?

    openSUSE Lounge by Ishwon

    Description

    openSUSE Lounge is a membership management platform for the openSUSE Project. It aims to simplify how we maintain member records, track membership status, and support election processes.

    The platform provides Membership Officials with an easier way to keep the membership database accurate and up to date. It also helps Election Officials export the latest voter list and report issues such as bounced voter-credential emails, giving the Membership team early visibility into outdated or inactive accounts.

    Goals

    This project seeks to make openSUSE membership management more efficient, reliable, and transparent.

    Long-term plans include enabling contributors to apply for membership directly through the platform and improving coordination between Membership and Election teams.

    Technology stack

    • Laravel - Backend framework powering the core application logic, routing, and data management.
    • Tailwind CSS - Utility-first CSS framework used for building responsive and clean user interfaces.
    • Alpine.js - Lightweight JavaScript framework for adding interactivity and dynamic behavior to frontend components.
    • MariaDB — Relational database management system for storing and managing application data.

    Demo

    Available at https://lounge-test.cloudnativemauritius.com. Test account:

    • Election: election@example.com

    Password is oSL0ung3Pass.

    Project Repo

    https://github.com/ishwon/opensuse-lounge

    Port the classic browser game HackTheNet to PHP 8 by dgedon

    Description

    The classic browser game HackTheNet from 2004 still runs on PHP 4/5 and MySQL 5 and needs a port to PHP 8 and e.g. MariaDB.

    Goals

    • Port the game to PHP 8 and MariaDB 11
    • Create a container where the game server can simply be started/stopped

    Resources

    • https://github.com/nodeg/hackthenet

    issuefs: FUSE filesystem representing issues (e.g. JIRA) for the use with AI agents code-assistants by llansky3

    Description

    Creating a FUSE filesystem (issuefs) that mounts issues from various ticketing systems (Github, Jira, Bugzilla, Redmine) as files to your local file system.

    And why this is good idea?

    • User can use favorite command line tools to view and search the tickets from various sources
    • User can use AI agents capabilities from your favorite IDE or cli to ask question about the issues, project or functionality while providing relevant tickets as context without extra work.
    • User can use it during development of the new features when you let the AI agent to jump start the solution. The issuefs will give the AI agent the context (AI agents just read few more files) about the bug or requested features. No need for copying and pasting issues to user prompt or by using extra MCP tools to access the issues. These you can still do but this approach is on purpose different.

    Goals

    1. Add Github issue support
    2. Proof the concept/approach by apply the approach on itself using Github issues for tracking and development of new features
    3. Add support for Bugzilla and Redmine using this approach in the process of doing it. Record a video of it.
    4. Clean-up and test the implementation and create some documentation
    5. Create a blog post about this approach

    Resources

    There is a prototype implementation here. This currently sort of works with JIRA only.

    Bugzilla goes AI - Phase 1 by nwalter

    Description

    This project, Bugzilla goes AI, aims to boost developer productivity by creating an autonomous AI bug agent during Hackweek. The primary goal is to reduce the time employees spend triaging bugs by integrating Ollama to summarize issues, recommend next steps, and push focused daily reports to a Web Interface.

    Goals

    To reduce employee time spent on Bugzilla by implementing an AI tool that triages and summarizes bug reports, providing actionable recommendations to the team via Web Interface.

    Project Charter

    https://docs.google.com/document/d/1HbAvgrg8T3pd1FIx74nEfCObCljpO77zz5In_Jpw4as/edit?usp=sharing## Description

    Project Achievements during Hackweek

    In this file you can read about what we achieved during Hackweek.

    https://docs.google.com/document/d/14gtG9-ZvVpBgkh33Z4AM6iLFWqZcicQPD41MM-Pg0/edit?usp=sharing

    GenAI-Powered Systemic Bug Evaluation and Management Assistant by rtsvetkov

    Motivation

    What is the decision critical question which one can ask on a bug? How this question affects the decision on a bug and why?

    Let's make GenAI look on the bug from the systemic point and evaluate what we don't know. Which piece of information is missing to take a decision?

    Description

    To build a tool that takes a raw bug report (including error messages and context) and uses a large language model (LLM) to generate a series of structured, Socratic-style or Systemic questions designed to guide a the integration and development toward the root cause, rather than just providing a direct, potentially incorrect fix.

    Goals

    Set up a Python environment

    Set the environment and get a Gemini API key. 2. Collect 5-10 realistic bug reports (from open-source projects, personal projects, or public forums like Stack Overflow—include the error message and the initial context).

    Build the Dialogue Loop

    1. Write a basic Python script using the Gemini API.
    2. Implement a simple conversational loop: User Input (Bug) -> AI Output (Question) -> User Input (Answer to AI's question) -> AI Output (Next Question). Code Implementation

    Socratic/Systemic Strategy Implementation

    1. Refine the logic to ensure the questions follow a Socratic and Systemic path (e.g., from symptom-> context -> assumptions -> -> critical parts -> ).
    2. Implement Function Calling (an advanced feature of the Gemini API) to suggest specific actions to the user, like "Run a ping test" or "Check the database logs."
    3. Implement Bugzillla call to collect the
    4. Implement Questioning Framework as LLVM pre-conditioning
    5. Define set of instructions
    6. Assemble the Tool

    Resources

    What are Systemic Questions?

    Systemic questions explore the relationships, patterns, and interactions within a system rather than focusing on isolated elements.
    In IT, they help uncover hidden dependencies, feedback loops, assumptions, and side-effects during debugging or architecture analysis.

    Gitlab Project

    gitlab.suse.de/sle-prjmgr/BugDecisionCritical_Question

    Kudos aka openSUSE Recognition Platform by lkocman

    Description

    Relevant blog post at news-o-o

    I started the Kudos application shortly after Leap 16.0 to create a simple, friendly way to recognize people for their work and contributions to openSUSE. There’s so much more to our community than just submitting requests in OBS or gitea we have translations (not only in Weblate), wiki edits, forum and social media moderation, infrastructure maintenance, booth participation, talks, manual testing, openQA test suites, and more!

    Goals

    • Kudos under github.com/openSUSE/kudos with build previews aka netlify

    • Have a kudos.opensuse.org instance running in production

    • Build an easy-to-contribute recognition platform for the openSUSE community a place where everyone can send and receive appreciation for their work, across all areas of contribution.

    • In the future, we could even explore reward options such as vouchers for t-shirts or other community swag, small tokens of appreciation to make recognition more tangible.

    Resources

    (Do not create new badge requests during hackweek, unless you'll make the badge during hackweek)

    Work on kqlite (Lightweight remote SQLite with high availability and auto failover). by epenchev

    Description

    Continue the work on kqlite (Lightweight remote SQLite with high availability and auto failover).
    It's a solution for applications that require High Availability but don't need all the features of a complete RDBMS and can fit SQLite in their use case.
    Also kqlite can be considered to be used as a lightweight storage backend for K8s (https://docs.k3s.io/datastore) and the Edge, and allowing to have only 2 Nodes for HA.

    Goals

    Push kqlite to a beta version.
    kqlite as library for Go programs.

    Resources

    https://github.com/kqlite/kqlite

    Kudos aka openSUSE Recognition Platform by lkocman

    Description

    Relevant blog post at news-o-o

    I started the Kudos application shortly after Leap 16.0 to create a simple, friendly way to recognize people for their work and contributions to openSUSE. There’s so much more to our community than just submitting requests in OBS or gitea we have translations (not only in Weblate), wiki edits, forum and social media moderation, infrastructure maintenance, booth participation, talks, manual testing, openQA test suites, and more!

    Goals

    • Kudos under github.com/openSUSE/kudos with build previews aka netlify

    • Have a kudos.opensuse.org instance running in production

    • Build an easy-to-contribute recognition platform for the openSUSE community a place where everyone can send and receive appreciation for their work, across all areas of contribution.

    • In the future, we could even explore reward options such as vouchers for t-shirts or other community swag, small tokens of appreciation to make recognition more tangible.

    Resources

    (Do not create new badge requests during hackweek, unless you'll make the badge during hackweek)