General

Profile

Stefan Petscharnig

  • Registered on: 23.07.2018
  • Last connection: 12.12.2018

Issues

Projects

  • QKD Network (Engineer, AIT Staff, User, 23.07.2018)
  • QKD Stack (Engineer, AIT Staff, User, 23.07.2018)
  • GoodieBag (Engineer, AIT Staff, User, 23.07.2018)
  • QKD Software (Engineer, AIT Staff, User, 23.07.2018)
  • QKD (Engineer, AIT Staff, User, 23.07.2018)

Activity

03.09.2018

14:27 QKD Task #1475: Use google mock tests
update:
google mock is intended to mock virtual functions.
At a current state, google mock seems only to make...
14:24 QKD Task #1476 (Closed): Check ASSERT_PRED1 behavior in test_crypto.schemes
yes, apparently googletest seems to need "<<" defined to debugging, ASSERT_TRUE / ASSERT_FALSE do the job also, so we...
14:18 QKD Support #1463 (Closed): qkd::utility::memory - from_hex input VS as_hex output inconsistency
Commit 2fef0507:
drop support for odd inputs in qkd::utility::memory::from_hex
( https://git-service.ait.ac.at/q...

14.08.2018

12:13 QKD Task #1475: Use google mock tests
google mock (gmock) allows tests t be decoupled from other class' dependencies.
Therefore, gmock provides measure...

09.08.2018

15:06 QKD Task #1477 (New): reactivate module tests
module tests (unit/module/confiig|io|null|terminate are not really covered atm, they are also not added in cmake
14:11 QKD Task #1476 (Closed): Check ASSERT_PRED1 behavior in test_crypto.schemes
currently we use ASSERT_TRUE(valid_scheme(scheme));
we wanted to use ASSERT_PRED1(valid_scheme, scheme);
but tha...
13:56 QKD Task #1475 (New): Use google mock tests
include mock tests

06.08.2018

13:05 QKD Support #1470 (Feedback): Potential misleading terminology in utility/environment
In qkd/include/qkd/utility/environment.h (line 36), there is a definition for a struct called nic.
If I understood...

31.07.2018

16:27 QKD Support #1463: qkd::utility::memory - from_hex input VS as_hex output inconsistency
implemented:
@
qkd::utility::memory memory::from_hex(std::string const & hex) {

if( (hex.length() & 1)...
09:50 QKD Support #1463 (Closed): qkd::utility::memory - from_hex input VS as_hex output inconsistency

Between input of qkd::utility::memory::from_hex and output of qkd::utility::memory::as_hex there is an inconsistenc...

Also available in: Atom