Jun-19-2024, 08:12 PM
Hi Friends!
Briefly: here is the exercise I've created couple days ago but for which I feel my skills are not adequate to test it properly, thus any remarks on the statement flaws, probable errors or hacks, deficiencies, issues with automated check - are welcome (and most wished for).
Longer story:
It so happened that recently I worked in a company where people were working on some automated testing system for students (job candidates) and I participated in a discussion where managers quarreled with programmers because testing exercises were too "remote" from "practical needs".
Now it happened so that I myself run this small site with coding problems for some years and I felt this reproach is correct. I tried to recollect some interview questions or test projects I met in my career and at last decided on this one. In my idea the user (student) is to create code to listen both UDP and TCP simultaneously. In my opinion this requires multithreading (but perhaps this is wrong?) - and here is a small catch when testing code opens two connections
one after another but tries to exchange the data on the second of them first (in my opinion this should stuck with single-threaded TCP server).
You see, regretfully I am not much in Python - actually I thought about this very small exercise perhaps for a week or more - despite the checking code (which runs in separate thread (daemon) is perhaps 20 lines and my "reference" solution for the server about another 20 lines.
Briefly: here is the exercise I've created couple days ago but for which I feel my skills are not adequate to test it properly, thus any remarks on the statement flaws, probable errors or hacks, deficiencies, issues with automated check - are welcome (and most wished for).
Longer story:
It so happened that recently I worked in a company where people were working on some automated testing system for students (job candidates) and I participated in a discussion where managers quarreled with programmers because testing exercises were too "remote" from "practical needs".
Now it happened so that I myself run this small site with coding problems for some years and I felt this reproach is correct. I tried to recollect some interview questions or test projects I met in my career and at last decided on this one. In my idea the user (student) is to create code to listen both UDP and TCP simultaneously. In my opinion this requires multithreading (but perhaps this is wrong?) - and here is a small catch when testing code opens two connections
one after another but tries to exchange the data on the second of them first (in my opinion this should stuck with single-threaded TCP server).
You see, regretfully I am not much in Python - actually I thought about this very small exercise perhaps for a week or more - despite the checking code (which runs in separate thread (daemon) is perhaps 20 lines and my "reference" solution for the server about another 20 lines.