Functions using libfcgi stuff are more complicated to test. For example :
The libpyfcgi.IoIn class allows worker to read HTTP data from an RawIo interface. This class is written in C and calls FCGX_* functions to read data from FCGX_Stream* returned by FCGX_Accept….
A way to test all this stuff is to create a valid FCGI context. Maybe with a dummy HTTP server sending FCGI requests to the test programm…. Or by re-defining/mocking all FCGX_* functions…. (the second solution seems the simplest/better one)
Functions using libfcgi stuff are more complicated to test. For example :
The libpyfcgi.IoIn class allows worker to read HTTP data from an RawIo interface. This class is written in C and calls FCGX_* functions to read data from FCGX_Stream* returned by FCGX_Accept....
A way to test all this stuff is to create a valid FCGI context. Maybe with a dummy HTTP server sending FCGI requests to the test programm.... Or by re-defining/mocking all FCGX_* functions.... (the second solution seems the simplest/better one)
yannweb
added this to the BETA version milestone 5 years ago
Functions using libfcgi stuff are more complicated to test. For example :
The libpyfcgi.IoIn class allows worker to read HTTP data from an RawIo interface. This class is written in C and calls FCGX_* functions to read data from FCGX_Stream* returned by FCGX_Accept….
A way to test all this stuff is to create a valid FCGI context. Maybe with a dummy HTTP server sending FCGI requests to the test programm…. Or by re-defining/mocking all FCGX_* functions…. (the second solution seems the simplest/better one)