|
Cambridge SMT System
|
Unit testing: TaskInterface methods. More...
#include <googletesting.h>#include "main.custom_assert.hpp"#include "main.logger.hpp"#include "taskinterface.hpp"
Go to the source code of this file.
Classes | |
| class | googletesting::DataTest1 |
| Trivial data class with three bool variables. More... | |
| class | googletesting::Task1< Data > |
| Trivial task class implementing run method to modify first bool variable. More... | |
| class | googletesting::Task2< Data > |
| Trivial task class implementing run method to modify second bool variable. More... | |
| class | googletesting::Task3< Data > |
| Trivial task class implementing run method to modify third bool variable. More... | |
| class | googletesting::Task2b< Data > |
| Trivial task class implementing run method to modify second bool variable. Additionally, signals that execution is to stop after finishing with Task2b. More... | |
| class | googletesting::DataTest2 |
| Trivial data class, now contains unsigned and vector<unsigned>. More... | |
| class | googletesting::Task4< Data > |
| Trivial task class, implements run to modify DataTest2. More... | |
| class | googletesting::PostEditTask< Data > |
| This is a test to show how an imaginary postedit class could work. The class would contain a pointer to the whole hifst system A single run of PostEditTask may kickoff several times the decoder. More... | |
Namespaces | |
| googletesting | |
| test-specific classes and functions | |
Functions | |
| googletesting::TEST (TaskInterface, chainoftasks1) | |
| Tests chainoftasks implementation in taskinterface. Three objects are appended Each of them modifies a single bool. The three should get executed so all bool variables are set to true. More... | |
| googletesting::TEST (TaskInterface, chainoftasks2) | |
| Tests chainoftasks implementation in taskinterface. Three objects are appended Each of them modifies a single bool. The three should get executed so all bool variables are set to true. More... | |
| googletesting::TEST (TaskInterface, chainoftasks3) | |
| Test that the functor works well appending tasks. More... | |
| googletesting::TEST (TaskInterface, chainoftasks4) | |
| Test the introduction of a NULL in the chain of tasks. Task1 should point directly to task3 and hence both tasks get executed. More... | |
| googletesting::TEST (TaskInterface, idx) | |
| Test. As datatest not renewed, therefore we can accumulate information from a task on subsequent runs. vector<unsigned> should contain all k indices. More... | |
| googletesting::TEST (TaskInterface, idx_chainrun) | |
| Test. Task Class encapsulating another task(s). Executes twice for each index k – vector<unsigned> contains repeated k values. More... | |
| int | main (int argc, char **argv) |
| main function. If compiled individualy, will kickoff any tests in this file. More... | |
| int main | ( | int | argc, |
| char ** | argv | ||
| ) |
main function. If compiled individualy, will kickoff any tests in this file.
Definition at line 226 of file taskinterface.gtest.cpp.