File: version.cpp

package info (click to toggle)
gromacs 2025.4-1
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid
  • size: 287,236 kB
  • sloc: xml: 3,718,478; cpp: 654,820; ansic: 75,282; python: 20,471; sh: 3,471; perl: 2,218; yacc: 644; fortran: 397; lisp: 265; makefile: 171; lex: 125; awk: 68; csh: 39
file content (104 lines) | stat: -rw-r--r-- 3,876 bytes parent folder | download | duplicates (3)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
/*
 * This file is part of the GROMACS molecular simulation package.
 *
 * Copyright 2018- The GROMACS Authors
 * and the project initiators Erik Lindahl, Berk Hess and David van der Spoel.
 * Consult the AUTHORS/COPYING files and https://www.gromacs.org for details.
 *
 * GROMACS is free software; you can redistribute it and/or
 * modify it under the terms of the GNU Lesser General Public License
 * as published by the Free Software Foundation; either version 2.1
 * of the License, or (at your option) any later version.
 *
 * GROMACS is distributed in the hope that it will be useful,
 * but WITHOUT ANY WARRANTY; without even the implied warranty of
 * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the GNU
 * Lesser General Public License for more details.
 *
 * You should have received a copy of the GNU Lesser General Public
 * License along with GROMACS; if not, see
 * https://www.gnu.org/licenses, or write to the Free Software Foundation,
 * Inc., 51 Franklin Street, Fifth Floor, Boston, MA  02110-1301  USA.
 *
 * If you want to redistribute modifications to GROMACS, please
 * consider that scientific software is very special. Version
 * control is crucial - bugs must be traceable. We will be happy to
 * consider code for inclusion in the official distribution, but
 * derived work must not be called official GROMACS. Details are found
 * in the README & COPYING files - if they are missing, get the
 * official version at https://www.gromacs.org.
 *
 * To help us fund GROMACS development, we humbly ask that you cite
 * the research papers on the package. Check out https://www.gromacs.org.
 */

#include "gmxapi/version.h"

#include <climits>

#include <gtest/gtest.h>

#include "testingconfiguration.h"

namespace gmxapi
{

namespace testing
{

namespace
{

using gmxapi::Version;

/* Copy header version info with intentionally sloppy type-ing to try to catch
 * worst-case scenarios and unexpected behavior. Otherwise the isAtLeast function
 * uses major(), minor(), and patch() so testing them might be superfluous.
 */
//! \cond
const int current_major = gmxapi::c_majorVersion;
const int current_minor = gmxapi::c_minorVersion;
const int current_patch = gmxapi::c_patchVersion;
//! \endcond

/*!
 * \brief Check basic Version interface functionality.
 */
TEST_F(GmxApiTest, SaneVersionComparisons)
{
    EXPECT_TRUE(Version::isAtLeast(0, 0, 0));
    EXPECT_FALSE(Version::isAtLeast(SHRT_MAX, SHRT_MAX, SHRT_MAX));
    EXPECT_TRUE(Version::isAtLeast(current_major, current_minor, current_patch));
    EXPECT_FALSE(Version::isAtLeast(current_major + 1, current_minor, current_patch));
    EXPECT_FALSE(Version::isAtLeast(current_major, current_minor + 1, current_patch));
    EXPECT_FALSE(Version::isAtLeast(current_major, current_minor, current_patch + 1));
}

/*!
 * \brief Check whether gmxapi correctly advertises or refutes feature availability.
 *
 * Check for correct responses from the Version API for features or
 * functionality not (yet) guaranteed by the current API version.
 * If a feature is available, it is expected to conform to the API specification
 * for the library Version::release(). As we discover features that break
 * forward-compatibility of the API, we will have to provide developer documentation
 * or sample code for build-time CMake feature checks.
 *
 * This is the test for pre-0.1 features leading up to that specification.
 *
 * \internal
 * Designed but unimplemented features should be tested with ``EXPECT_FALSE``
 * until they are implemented, then toggled to ``EXPECT_TRUE`` as implemented as
 * extensions of the current API spec. (There aren't any yet.)
 */
TEST_F(GmxApiTest, VersionNamed0_1_Features)
{
    EXPECT_FALSE(Version::hasFeature(""));
    EXPECT_FALSE(Version::hasFeature("nonexistent feature"));
}

} // end anonymous namespace

} // namespace testing

} // namespace gmxapi