<bitcoin-git>
bitcoin/master 7777a13 MarcoFalke: test: Move Fetching-print to download_from_url util
<bitcoin-git>
[bitcoin] fanquake merged pull request #34679: ci: Download script_assets_test.json for Windows CI (master...2602-win-cross-json) https://github.com/bitcoin/bitcoin/pull/34679
memset has quit [Remote host closed the connection]
memset has joined #bitcoin-core-dev
timbo_xyz has joined #bitcoin-core-dev
durandal_ has quit [Remote host closed the connection]
durandal_ has joined #bitcoin-core-dev
durandal_ has quit [Remote host closed the connection]
<bitcoin-git>
[bitcoin] ajtowns opened pull request #34730: util/log: Combine the warning/error log levels into a single alert level (master...202603-logalert) https://github.com/bitcoin/bitcoin/pull/34730
<johnny9dev>
dergoegge: I'm pretty sure the same thing can be done where you hook into the gui object tree and find the widgets by objectName and edit/click. I'm less familiar with how the widgets engine works though.
TheRec has joined #bitcoin-core-dev
AaronvanW has quit [Remote host closed the connection]
timbo_xyz has quit [Ping timeout: 258 seconds]
l0rinc has quit [Quit: l0rinc]
janb84 has joined #bitcoin-core-dev
dermoth has quit [Read error: Connection reset by peer]
<dergoegge>
johnny9dev: Thanks! I was looking at this in the context of fuzzing the gui. I'll bring this up in the meeting, see if anyone wants to work on this
<johnny9dev>
dergoegge: there is a commercial product called Squish for Qt that definitely does it but I know for QML that it's easy enough to just build your own test instrumentation bridge and so what I've done in the gui-qml project is create a simple test bridge that is very similar to one ive used in an enterprise product. The api is find object, wait for property, click, enter text, screenshot, etc. and you can build a comprehensive test
<johnny9dev>
framework with that.
timbo_xyz has joined #bitcoin-core-dev
<johnny9dev>
you could also do a monkey style test where you send click events and key events randomly all over to see if you can crash it. i imagine that might be similar to fuzzing
arejula27 has joined #bitcoin-core-dev
timbo_xyz has quit [Ping timeout: 258 seconds]
arejula27 has quit [Client Quit]
adil has joined #bitcoin-core-dev
durandal_ has quit [Remote host closed the connection]
<bitcoin-git>
[bitcoin] arejula27 opened pull request #34736: refactor: use explicit `&util::TraceThread` function pointer in thread spawns (master...tracethread-consistency) https://github.com/bitcoin/bitcoin/pull/34736
edouardparis has joined #bitcoin-core-dev
dzxzg has joined #bitcoin-core-dev
l0rinc has quit [Quit: l0rinc]
memset_ has joined #bitcoin-core-dev
memset has quit [Remote host closed the connection]
jonatack has quit [Ping timeout: 276 seconds]
dzxzg has quit [Quit: Konversation terminated!]
jonatack has joined #bitcoin-core-dev
jonatack has quit [Ping timeout: 264 seconds]
memset_ has quit [Remote host closed the connection]