Skip to content

Instantly share code, notes, and snippets.

View a-seskunas's full-sized avatar

Adam Seskunas a-seskunas

1 follower · 8 following
  • San Diego, CA
  • 16:24 (UTC -08:00)
View GitHub Profile
@a-seskunas
a-seskunas / ReportBuiler Final Report.md
Last active December 16, 2025 10:32
ReportBuiler Final Report

Final Report - GSoC - Implement ReportBuilder in C++

Author - Adam Seskunas
Project - LibreOffice - The Document Foundation
Mentors - Hossein Nourikhah, Michael Weghorn

@a-seskunas
a-seskunas / Debugging with jdb.md
Created February 10, 2025 20:58
Debugging with jdb

Debugging a LibreOffice Java Extension

This post aims to explain the process of debugging a LibreOffice extension on Linux that is written in Java, using jdb, the java debugging tool. From the jdb help page

The Java Debugger (JDB) is a simple command-line debugger for
Java classes. The `jdb` command and its options call the JDB.
The `jdb` command demonstrates the Java Platform Debugger Architecture (JDBA) and provides inspection and debugging of a
local or remote Java Virtual Machine (JVM).
@a-seskunas
a-seskunas / Git and Python.md
Last active January 27, 2025 22:16
Parsing a Git Log With Python

Parsing a Git Log With Python

In this post I will describe my experience adding functionality to a python script used to create documentation for the LibreOffice open source project. I will go into some details about how a Python script can be used to pull some interesting information from a git repository and also talk about some issues I faced when using Python to parse a large dataset.

Motivation

Over this past summer I was working on writing tests for the LibreOffice open source office suite. LibreOffice is a large code base with lots of active development and has great documentation and resources to help get new developers involved. One of these is Missing Unit Test Wiki, it looked like this

enter image description here

Writing tests can be a great way for a new deve
@a-seskunas
a-seskunas / Write a test from Missing Unit Wiki.md
Last active January 27, 2025 05:16
Write a test from Missing Unit Wiki

LibreOffice - Writing a Test from the MissingUnitTest Wiki.

LibreOffice uses some automation to compile a list of bug reports that have been fixed, but are missing a test. Writing a test for a bug fix in this list is a great way to contribute to the LibreOffice open source project.

A successfully merged test is run in the Continuous Integration pipeline via Jenkins each time a patch is uploaded to Gerrit. This ensures that the original bug is not introduced back into the project in the form of a regression. Below we’ll go through some steps to write a test from this list.

Missing Unit Tests Wiki Imagehttps://wiki.documentfoundation.org/MissingUnitTests

Finding a suitable bug

Not all bugs and bug reports are created equal, so finding
@a-seskunas
a-seskunas / FinalReport.md
Last active January 27, 2025 05:16
Google Summer of Code 2024 Final Report

Final Report - GSoC More and Better Tests

Author - Adam Seskunas
Project - LibreOffice - The Document Foundation
Mentors - Hossein Nourikhah, Xisco Fauli

Project Proposal Page - More and Better Tests Project Proposal

The goal of this project was to write more and better tests for the LibreOffice open source project. The first part of the project focused on porting tests from Java to C++. These Java tests are in some cases 20 years old, can be poorly documented and hard to debug when they fail. Porting these tests to C++ will ensure that they will continue to be run in the CI pipeline, preventing regressions from entering the code base.

The second part of the project consisted of writing tests from scratch, from the LibreOffice <