Creating babelfisgpg_unit Extension

[shashank-yenni]

Description

At present, babelfish encompasses various testing frameworks such as JDBC, Python, .NET, and fuzz tests. Each of these frameworks serves specific purposes and relies on client drivers. However, we lack a framework dedicated to unit testing. This is the motivation behind this to create a unit testing framework for babelfish.

In this commit, we add unit testing framework which enable us to test any piece of our codebase. The babelfishpg_unit directory is added as a new extension within the contrib folder present in babelfish_extensions. It contains the necessary files for the unit testing framework. Here's a brief explanation of each file:

• Makefile: This file specifies the build instructions for the babelfishpg_unit extension.
• babelfishpg_unit.control: This files contain metadata and control information about the extension.
• babelfishpg_unit.h: This header file contains any necessary macros, definitions, or utility functions required for the unit tests.
• babelfishpg_unit—1.0.0.sql: This SQL script defines the necessary functions and setup for running the tests. It acts as the entry point for invoking the unit tests. Once it is invoked, it will trigger the execution of all the tests or specific tests.
• babelfishpg_unit.c: This file serves as the main entry point for the unit tests. It includes the necessary headers and implements the logic to execute all the defined tests.
• test_money.c, ...: These are the individual test files which contains the test cases and assertions specific to a particular area of functionality or component being tested.
• log_files: It is a folder which contains log files created after each test run

Issues Resolved

I have developed the framework in such a way that we can run multiple tests by passing multiple parameters. With this framework, all test functions associated with multiple specified parameters can be successfully executed.

Signed-off-by: Yenni Shashank [email protected]

Test Scenarios Covered

• Use case based - Yes

• Boundary conditions - Yes

• Arbitrary inputs - Yes

• Negative test cases - Yes

• Minor version upgrade tests -

• Major version upgrade tests -

• Performance tests -

• Tooling impact -

• Client tests -

Tests Running

jdbc_testdb=# create extension babelfishpg_unit; select * from babelfishpg_unit_run_tests();
CREATE EXTENSION
                  test_name                  | status | runtime(µs) | enabled 
---------------------------------------------+--------+-------------+---------
 GreaterThanOrEqualToCheck_INT4_FIXEDDECIMAL | pass   |          11 | enabled
 LesserThanOrEqualToCheck_INT4_FIXEDDECIMAL  | pass   |           4 | enabled
 NotEqualToCheck_INT4_FIXEDDECIMAL           | pass   |           4 | enabled
 EqualToCheck_INT4_FIXEDDECIMAL              | pass   |           4 | enabled
 LesserThanCheck_INT4_FIXEDDECIMAL           | pass   |           3 | enabled
 Comparison_INT4_FIXEDDECIMAL                | pass   |           4 | enabled
 FIXEDDECIMALUM                              | pass   |           7 | enabled
 GreaterThanOrEqualToCheck_FIXEDDECIMAL_INT2 | pass   |           3 | enabled
 LesserThanOrEqualToCheck_FIXEDDECIMAL_INT2  | pass   |           3 | enabled
 GreaterThanCheck_FIXEDDECIMAL_INT2          | pass   |           2 | enabled
 NotEqualToCheck_FIXEDDECIMAL_INT2           | pass   |           2 | enabled
 Comparison_FIXEDDECIMAL_INT2                | pass   |           5 | enabled
(12 rows)

Check List

• Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is under the terms of the Apache 2.0 and PostgreSQL licenses, and grant any person obtaining a copy of the contribution permission to relicense all or a portion of my contribution to the PostgreSQL License solely to contribute all or a portion of my contribution to the PostgreSQL open source project.

For more information on following Developer Certificate of Origin and signing off your commits, please check here.

[surendravishnoi]

we should place log file somewhere which is not part of source code