ichthyo/LUMIERA.clone
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
LUMIERA.clone/tests/library/query-text-test.cpp

98 lines
2.4 KiB
C++
Raw Normal View History

generic query representation (placeholder) ...planned to be replaced later by a real AST based implementation, which acutally parses the query definitions
2012-12-03 00:41:57 +01:00
/*
QueryText(Test) - verify syntactical query representation
Copyright: clarify and simplify the file headers * Lumiera source code always was copyrighted by individual contributors * there is no entity "Lumiera.org" which holds any copyrights * Lumiera source code is provided under the GPL Version 2+ == Explanations == Lumiera as a whole is distributed under Copyleft, GNU General Public License Version 2 or above. For this to become legally effective, the ''File COPYING in the root directory is sufficient.'' The licensing header in each file is not strictly necessary, yet considered good practice; attaching a licence notice increases the likeliness that this information is retained in case someone extracts individual code files. However, it is not by the presence of some text, that legally binding licensing terms become effective; rather the fact matters that a given piece of code was provably copyrighted and published under a license. Even reformatting the code, renaming some variables or deleting parts of the code will not alter this legal situation, but rather creates a derivative work, which is likewise covered by the GPL! The most relevant information in the file header is the notice regarding the time of the first individual copyright claim. By virtue of this initial copyright, the first author is entitled to choose the terms of licensing. All further modifications are permitted and covered by the License. The specific wording or format of the copyright header is not legally relevant, as long as the intention to publish under the GPL remains clear. The extended wording was based on a recommendation by the FSF. It can be shortened, because the full terms of the license are provided alongside the distribution, in the file COPYING.
2024-11-17 23:42:55 +01:00
Copyright (C)
2012, Hermann Vosseler <Ichthyostega@web.de>
generic query representation (placeholder) ...planned to be replaced later by a real AST based implementation, which acutally parses the query definitions
2012-12-03 00:41:57 +01:00
Copyright: clarify and simplify the file headers * Lumiera source code always was copyrighted by individual contributors * there is no entity "Lumiera.org" which holds any copyrights * Lumiera source code is provided under the GPL Version 2+ == Explanations == Lumiera as a whole is distributed under Copyleft, GNU General Public License Version 2 or above. For this to become legally effective, the ''File COPYING in the root directory is sufficient.'' The licensing header in each file is not strictly necessary, yet considered good practice; attaching a licence notice increases the likeliness that this information is retained in case someone extracts individual code files. However, it is not by the presence of some text, that legally binding licensing terms become effective; rather the fact matters that a given piece of code was provably copyrighted and published under a license. Even reformatting the code, renaming some variables or deleting parts of the code will not alter this legal situation, but rather creates a derivative work, which is likewise covered by the GPL! The most relevant information in the file header is the notice regarding the time of the first individual copyright claim. By virtue of this initial copyright, the first author is entitled to choose the terms of licensing. All further modifications are permitted and covered by the License. The specific wording or format of the copyright header is not legally relevant, as long as the intention to publish under the GPL remains clear. The extended wording was based on a recommendation by the FSF. It can be shortened, because the full terms of the license are provided alongside the distribution, in the file COPYING.
2024-11-17 23:42:55 +01:00
  **Lumiera** is free software; you can redistribute it and/or modify it
  under the terms of the GNU General Public License as published by the
  Free Software Foundation; either version 2 of the License, or (at your
  option) any later version. See the file COPYING for further details.
generic query representation (placeholder) ...planned to be replaced later by a real AST based implementation, which acutally parses the query definitions
2012-12-03 00:41:57 +01:00
Copyright: clarify and simplify the file headers * Lumiera source code always was copyrighted by individual contributors * there is no entity "Lumiera.org" which holds any copyrights * Lumiera source code is provided under the GPL Version 2+ == Explanations == Lumiera as a whole is distributed under Copyleft, GNU General Public License Version 2 or above. For this to become legally effective, the ''File COPYING in the root directory is sufficient.'' The licensing header in each file is not strictly necessary, yet considered good practice; attaching a licence notice increases the likeliness that this information is retained in case someone extracts individual code files. However, it is not by the presence of some text, that legally binding licensing terms become effective; rather the fact matters that a given piece of code was provably copyrighted and published under a license. Even reformatting the code, renaming some variables or deleting parts of the code will not alter this legal situation, but rather creates a derivative work, which is likewise covered by the GPL! The most relevant information in the file header is the notice regarding the time of the first individual copyright claim. By virtue of this initial copyright, the first author is entitled to choose the terms of licensing. All further modifications are permitted and covered by the License. The specific wording or format of the copyright header is not legally relevant, as long as the intention to publish under the GPL remains clear. The extended wording was based on a recommendation by the FSF. It can be shortened, because the full terms of the license are provided alongside the distribution, in the file COPYING.
2024-11-17 23:42:55 +01:00
* *****************************************************************/
generic query representation (placeholder) ...planned to be replaced later by a real AST based implementation, which acutally parses the query definitions
2012-12-03 00:41:57 +01:00
Doxygen: prepare all unit tests for inclusion in the documentation Doxygen will only process files with a @file documentation comment. Up to now, none of our test code has such a comment, preventing the cross-links to unit tests from working. This is unfortunate, since unit tests, and even the code comments there, can be considered as the most useful form of technical documentation. Thus I'll start an initiative to fill in those missing comments automatically
2017-02-22 01:54:20 +01:00
/** @file query-text-test.cpp
Doxygen: magically insert a reference to the test class this bit of Sed magic relies on the fact that we happen to write the almost correct class name of a test into the header comment. HOWTO: for F in $(find tests -type f \( -name '*.cpp' \) -exec egrep -q '§§TODO§§' {} \; -print); do sed -r -i -e' 2 {h;x;s/\s+(.+)\(Test\).*$/\\ref \1_test/;x}; /§§TODO§§/ {s/§§TODO§§//;G;s/\n//}' $F; done
2017-02-22 03:17:18 +01:00
** unit test \ref QueryText_test
Doxygen: identify all files lacking a @file comment reason is, only files with a @file comment will be processed with further documentation commands. For this reason, our Doxygen documentation is lacking a lot of entries. HOWTO: find src -type f \( -name '*.cpp' -or -name '*.hpp' \) -not -exec egrep -q '\*.+@file' {} \; -print -exec sed -i -r -e'\_\*/_,$ { 1,+0 a\ \ \ /** @file §§§\ ** TODO §§§\ */ }' {} \;
2016-11-03 18:20:10 +01:00
*/
generic query representation (placeholder) ...planned to be replaced later by a real AST based implementation, which acutally parses the query definitions
2012-12-03 00:41:57 +01:00
#include "lib/test/run.hpp"
#include "lib/query-util.hpp"
#include "lib/query-text.hpp"
#include "lib/util.hpp"
#include <string>
//#include <map>
using util::contains;
using util::isnil;
using std::string;
namespace lib {
namespace test{
namespace { // test fixture...
} //(End) test fixture
fix **** in doxygen comments to make them stand out more prominently, some entity comments where started with a line of starts. Unfortunately, doxygen (and javadoc) only recogise comments which are started exactly with /** This caused quite some comments to be ignored by doxygen. Credits to Hendrik Boom for spotting this problem! A workaround is to end the line of stars with *//**
2013-10-24 23:06:36 +02:00
/***************************************************************************//**
generic query representation (placeholder) ...planned to be replaced later by a real AST based implementation, which acutally parses the query definitions
2012-12-03 00:41:57 +01:00
* @test cover basic properties of the generic syntactical query representation.
* - build from query string
*
* @todo this is placeholder code. The actual query representation needs to be written /////////////////////////////TICKET #899
* @see QueryText
*/
class QueryText_test : public Test
{
virtual void run (Arg)
{
emptyRepresentation();
build_from_string();
useHashValue();
}
void emptyRepresentation ()
{
QueryText noText;
CHECK (isnil (noText));
CHECK (isnil (string(noText)));
}
void build_from_string ()
{
QueryText eternal ("beats(lumiera, duke_nukem_forever).");
CHECK (contains (string(eternal), "lumiera"));
CHECK (contains (string(eternal), "beats"));
CHECK (contains (string(eternal), "duke_nukem_forever"));
CHECK (eternal.hasAtom ("lumiera"));
}
void useHashValue ()
{
QueryText one("one");
QueryText two("two");
CHECK (0 < hash_value(one));
CHECK (0 < hash_value(two));
CHECK (hash_value(one) != hash_value(two));
}
};
/** Register this test class... */
LAUNCHER(QueryText_test, "unit common");
}} // namespace lib::test
Reference in a new issue Copy permalink