0.0.10

[douglasdcm]

What's Changed

• Add precommit by @douglasdcm in Add precommit #98
• Implement AENA flight data scraper using Selenium and BeautifulSoup by @douglasdcm in Implement AENA flight data scraper using Selenium and BeautifulSoup #92
• Added a structured comparison of POM and Page Transactions (PT) by @douglasdcm in Added a structured comparison of POM and Page Transactions (PT) #101
• Remove warings and turn-off logger by @douglasdcm in Remove warings and turn-off logger #103
• Replace slow tests by @douglasdcm in Replace slow tests #104
• feat: Add Selenium Stealth Integration and Tests by @theijhay in feat: Add Selenium Stealth Integration and Tests #83
• Add readme to examples by @douglasdcm in Add readme to examples #105
• Add copyright by @douglasdcm in Add copyright #106
• improve readmes by @douglasdcm in improve readmes #107
• Add method 'when' and bump version by @douglasdcm in Add method 'when' and bump version #108

Full Changelog: 0.0.9...0.0.10

---

This discussion was created from the release 0.0.10.

[DONALDBZR]

Version: 0.0.10
Test Duration: 00:17:37.230354548
Average CPU Usage: 19.11 % ✅
@douglasdcm It has a better performance than the previous version on the 61 test cases

[douglasdcm]

Thanks! One of the tests that was hitting a slow web page now uses a local page. It made the tests faster. Do you use Linux? Are you able to use the command 'top'? If so, check if there are instances of chrome consuming CPU, please. It may be impacting the test results

[DONALDBZR]

I used top and even checked the amount of system calls done during the execution of the library. The tests spawns multiple instances. However, now the noise from the I/O bound operations removed, it makes the library more CPU Bound. As long as the implementation of the library has an average CPU usage which is less than 25% on 4-Core CPU, the library will remain lightweight and can be used on various machines without affecting other operations. I forgot to mention that the version of python used for this test is 3.10.

[douglasdcm]

Thanks. I will consider check the decreasing of python version. There are some tests that are skipped so it is necessary to know if they still work with low python version. If don't mind to open a issue to it, I appreciate ☺️ we can work on it later

About the CPU usage, as the tests are launching instances of chrome we are introducing noise in the test result. To test the performance of the library itself it is necessary to run tests that do not raise chrome or any other driver. This way we can see the performance of the core code in isolation. The core code does not suffer any major change from version 0.0.9 to 0.0.10. Just one new method was added in the Application class. I mean, nothing in the core code justifies the performance increasing. Does it make sense to you?

[DONALDBZR]

So, far, we know that the library will not work on 3.9. It works well as from 3.10, so we can ditch 3.9