ichthyo/LUMIERA.clone
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
LUMIERA.clone/tests/core/steam/mobject/session/deletecliptest.cpp

88 lines
2.9 KiB
C++
Raw Normal View History

TDBS (test driven brain storming) :-)
2007-09-03 02:33:47 +02:00
/*
DeleteClip(Test) - removing an Clip-MObject from the Session
GPL header whitespace
2010-12-17 23:28:49 +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
Copyright (C)
2008, Hermann Vosseler <Ichthyostega@web.de>
GPL header whitespace
2010-12-17 23:28:49 +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.
GPL header whitespace
2010-12-17 23:28:49 +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
* *****************************************************************/
TDBS (test driven brain storming) :-)
2007-09-03 02:33:47 +02: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 deletecliptest.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 DeleteClip_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
*/
TDBS (test driven brain storming) :-)
2007-09-03 02:33:47 +02:00
finish common->lib transition for the tests
2008-12-18 04:47:41 +01:00
#include "lib/test/run.hpp"
Global-Layer-Renaming: adjust header includes
2018-11-15 23:42:43 +01:00
#include "steam/assetmanager.hpp"
#include "steam/mobject/session.hpp"
#include "steam/mobject/session/testsession1.hpp"
#include "steam/mobject/session/clip.hpp" // TODO: really neded?
mass clean-up: adapt usage of std::cout pretty much everywhere - remove unnecessary includes - expunge all remaining usages of boost::format - able to leave out the expliti string(elm) in output - drop various operator<<, since we're now picking up custom string conversions automatically - delete diagnostics headers, which are now largely superfluous - use newer helper functions occasionally I didn't blindly change any usage of <iostream> though; sometimes, just using the output streams right away seems adequate.
2016-01-07 03:58:29 +01:00
#include "lib/format-cout.hpp"
finish common->lib transition for the tests
2008-12-18 04:47:41 +01:00
//#include "lib/util.hpp"
TDBS (test driven brain storming) :-)
2007-09-03 02:33:47 +02:00
mass clean-up: adapt usage of std::cout pretty much everywhere - remove unnecessary includes - expunge all remaining usages of boost::format - able to leave out the expliti string(elm) in output - drop various operator<<, since we're now picking up custom string conversions automatically - delete diagnostics headers, which are now largely superfluous - use newer helper functions occasionally I didn't blindly change any usage of <iostream> though; sometimes, just using the output streams right away seems adequate.
2016-01-07 03:58:29 +01:00
//using std::string;
Segmentation: reorganise namespaces The Fixture and the low-level model backbone deserve a distinct namespace on their own. Since it's built by the Builder from the Session contents, and also used by the frame dispatch, we can expect dependence on some types from Steam-Layer, and thus this namespace needs to reside in Steam-Layer rather, while the actual low-level Model might become part of Vault-Layer, creating a hierarchy of data structures. (Remark: likely also the session related namespaces will need a reorganisation)
2023-04-25 18:27:16 +02:00
using std::dynamic_pointer_cast; //////////////////// TODO only temp
TDBS (test driven brain storming) :-)
2007-09-03 02:33:47 +02:00
implement access to current session. add lots of UNIMPLEMENTED stubs and finally get the sourcebase through the compiler....
2007-09-27 23:26:54 +02:00
using proc_interface::AssetManager;
using proc_interface::PAsset;
using proc_interface::IDA;
TDBS (test driven brain storming) :-)
2007-09-03 02:33:47 +02:00
passes the compiler again. (using direct references instead of smart-ptrs for the 'backlink' from Clip-MO to asset::Media)
2007-11-14 10:10:52 +01:00
Segmentation: reorganise namespaces The Fixture and the low-level model backbone deserve a distinct namespace on their own. Since it's built by the Builder from the Session contents, and also used by the frame dispatch, we can expect dependence on some types from Steam-Layer, and thus this namespace needs to reside in Steam-Layer rather, while the actual low-level Model might become part of Vault-Layer, creating a hierarchy of data structures. (Remark: likely also the session related namespaces will need a reorganisation)
2023-04-25 18:27:16 +02:00
namespace steam {
fixing, stubbing, and some chainsaw surgery to get half-finished code through the compiler
2009-06-09 09:05:19 +02:00
namespace mobject {
namespace session {
namespace test {
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
/***************************************************************//**
kill "the EDL"
2010-02-22 03:52:52 +01:00
* @test removing a test clip from the Session/Model.
fixing, stubbing, and some chainsaw surgery to get half-finished code through the compiler
2009-06-09 09:05:19 +02:00
* @see mobject::session::Clip
kill "the EDL"
2010-02-22 03:52:52 +01:00
* @see mobject::Session
*
* @todo ////////////////////////////////////////////////TICKET #499
fixing, stubbing, and some chainsaw surgery to get half-finished code through the compiler
2009-06-09 09:05:19 +02:00
*/
class DeleteClip_test : public Test
TDBS (test driven brain storming) :-)
2007-09-03 02:33:47 +02:00
{
fixing, stubbing, and some chainsaw surgery to get half-finished code through the compiler
2009-06-09 09:05:19 +02:00
virtual void
run (Arg)
TDBS (test driven brain storming) :-)
2007-09-03 02:33:47 +02:00
{
fixing, stubbing, and some chainsaw surgery to get half-finished code through the compiler
2009-06-09 09:05:19 +02:00
buildTestsession1();
PSess sess = Session::current;
AssetManager& aMang = AssetManager::instance();
kill "the EDL"
2010-02-22 03:52:52 +01:00
UNIMPLEMENTED("typesafe searching for MObjects in the Session");
fixing, stubbing, and some chainsaw surgery to get half-finished code through the compiler
2009-06-09 09:05:19 +02:00
(cont) analyzing the problem of output designation
2010-06-25 04:43:06 +02:00
#if false /////////////////////////////////////////////////////////////////////////////////////////////////////TICKET #639 : work out how to search within the Model!!
fixing, stubbing, and some chainsaw surgery to get half-finished code through the compiler
2009-06-09 09:05:19 +02:00
PClipMO clipPlacement = sess->currEDL().find(SESSION1_CLIP);
kill "the EDL"
2010-02-22 03:52:52 +01:00
// global Var assigned in buildTestsession1()
fixing, stubbing, and some chainsaw surgery to get half-finished code through the compiler
2009-06-09 09:05:19 +02:00
PMedia media = clipPlacement->getMedia();
IDA clipAID = media->getID();
Use CHECK instead of ASSERT in test suite. (Ticket #250)
2010-12-10 02:55:40 +01:00
CHECK (clipPlacement);
fixing, stubbing, and some chainsaw surgery to get half-finished code through the compiler
2009-06-09 09:05:19 +02:00
sess->remove (clipPlacement);
Use CHECK instead of ASSERT in test suite. (Ticket #250)
2010-12-10 02:55:40 +01:00
CHECK (!sess->currEDL().find(SESSION1_CLIP)); // Session forgot the Clip/Placement
CHECK (!aMang.known (clipAID)); // corresponding Clip Asset has disappeared
CHECK (!clipPlacement->getMedia()); // internal cross-links removed
(cont) analyzing the problem of output designation
2010-06-25 04:43:06 +02:00
#endif /////////////////////////////////////////////////////////////////////////////////////////////////////TICKET #639 : work out how to search within the Model!!
fixing, stubbing, and some chainsaw surgery to get half-finished code through the compiler
2009-06-09 09:05:19 +02:00
}
};
passes the compiler again. (using direct references instead of smart-ptrs for the 'backlink' from Clip-MO to asset::Media)
2007-11-14 10:10:52 +01:00
TDBS (test driven brain storming) :-)
2007-09-03 02:33:47 +02:00
fixing, stubbing, and some chainsaw surgery to get half-finished code through the compiler
2009-06-09 09:05:19 +02:00
/** Register this test class... */
LAUNCHER (DeleteClip_test, "function session");
Global-Layer-Renaming: rename namespaces
2018-11-15 23:55:13 +01:00
}}}} // namespace steam::mobject::session::test
Reference in a new issue Copy permalink