SoK/2024/StatusReport/Sarthak Negi: Difference between revisions

From KDE Community Wiki
No edit summary
No edit summary
Line 8: Line 8:
3. Create tests for KEcolab<br>
3. Create tests for KEcolab<br>
4. Measuring in Wayland<br>
4. Measuring in Wayland<br>


<h3>Weekly Progress</h3>
<h3>Weekly Progress</h3>
'''WEEK 1 - 2''': I've established Selenium on three virtual machines (Kubuntu, Fedora, Ubuntu) for simultaneous testing and conducted thorough KecoLab testing, identifying and reporting bugs to enhance its quality. Proactive communication was initiated with the Okular team for pipeline integration and with KdeEcoTest contributors regarding Wayland support timelines. Additionally, Also, resolved the dynamic IP issue for Powemeter access, streamlining testing processes.
'''WEEK 1 - 2''': I've established Selenium on three virtual machines (Kubuntu, Fedora, Ubuntu) for simultaneous testing and conducted thorough KecoLab testing, identifying and reporting bugs to enhance its quality. Proactive communication was initiated with the Okular team for pipeline integration and with KdeEcoTest contributors regarding Wayland support timelines. Additionally, Also, resolved the dynamic IP issue for Powemeter access, streamlining testing processes.

Revision as of 00:54, 7 February 2024

Testing and development of KEcoLab

Introduction and Abstract: Sustainability is a key goal for KDE over the next two years. One aspect of this goal is to measure the energy consumption of KDE softwares. To do this, it is necessary to access lab in KDAB, Berlin, which can be done remotely using KEcoLab.

deliverables:
1. Testing KEcoLab & bug squashing
2. Integrating measurement workflow in Okular repository
3. Create tests for KEcolab
4. Measuring in Wayland

Weekly Progress

WEEK 1 - 2: I've established Selenium on three virtual machines (Kubuntu, Fedora, Ubuntu) for simultaneous testing and conducted thorough KecoLab testing, identifying and reporting bugs to enhance its quality. Proactive communication was initiated with the Okular team for pipeline integration and with KdeEcoTest contributors regarding Wayland support timelines. Additionally, Also, resolved the dynamic IP issue for Powemeter access, streamlining testing processes.