gil/test/extension/io/png_write_test.cpp
Mateusz Łoskot 96df5442bc
Move tests of extensions inside test/ directory (#302)
Split header tests accordingly i.e. test core headers as part of
core tests, numeric extension headers as part of numeric tests, etc.

It extends the convention of sub-directories already established in
`include/boost/gil` directory. It is sensible to follow it in other
areas of the source tree (i.e. `test/`, `doc/` and `benchmark/`).

Another important reason to move the tests is to enable removal of
the top-level `Jamfile` with all its definitions of test-specific
requirements.
The top-level `Jamfile` is not advised, especially if it specifies
build requirements like C++ language version.
Those affect non-tests builds e.g. documentation, causing failures
during generation of HTML documentation (leads to missing docs).

(cherry picked from develop branch commit 4ed7701b47)
2019-09-26 11:43:13 +02:00

41 lines
1016 B
C++

//
// Copyright 2013 Christian Henning
//
// Distributed under the Boost Software License, Version 1.0
// See accompanying file LICENSE_1_0.txt or copy at
// http://www.boost.org/LICENSE_1_0.txt
//
//#define BOOST_TEST_MODULE png_read_test_module
#define BOOST_GIL_IO_ADD_FS_PATH_SUPPORT
#define BOOST_GIL_IO_ENABLE_GRAY_ALPHA
#define BOOST_FILESYSTEM_VERSION 3
#include <boost/gil/extension/io/png.hpp>
#include <boost/test/unit_test.hpp>
#include <cstdint>
#include <iostream>
#include "color_space_write_test.hpp"
#include "paths.hpp"
#include "scanline_read_test.hpp"
using namespace std;
using namespace boost;
using namespace gil;
using namespace boost::gil::detail;
using tag_t = png_tag;
BOOST_AUTO_TEST_SUITE( gil_io_png_tests )
BOOST_AUTO_TEST_CASE( rgb_color_space_write_test )
{
color_space_write_test< tag_t >( png_out + "rgb_color_space_test.png"
, png_out + "bgr_color_space_test.png"
);
}
BOOST_AUTO_TEST_SUITE_END()