aboutsummaryrefslogtreecommitdiff
path: root/nexgb/xproto/xproto_test.go
diff options
context:
space:
mode:
Diffstat (limited to 'nexgb/xproto/xproto_test.go')
-rw-r--r--nexgb/xproto/xproto_test.go8
1 files changed, 5 insertions, 3 deletions
diff --git a/nexgb/xproto/xproto_test.go b/nexgb/xproto/xproto_test.go
index f061198..8d0ca88 100644
--- a/nexgb/xproto/xproto_test.go
+++ b/nexgb/xproto/xproto_test.go
@@ -12,7 +12,11 @@ package xproto
There are also a couple of benchmarks that show the difference between
correctly issuing lots of requests and gathering replies and
incorrectly doing the same. (This particular difference is one of the
- claimed advantages of the XCB, and therefore XGB, family.
+ claimed advantages of the XCB, and therefore XGB, family.)
+
+ In sum, these tests are more focused on testing the core xgb package itself,
+ rather than whether xproto has properly implemented the core X client
+ protocol.
*/
import (
@@ -164,8 +168,6 @@ func TestWindowEvents(t *testing.T) {
t.Fatalf("ConfigureWindow: %s", err)
}
- TestProperty(t)
-
evOrErr := waitForEvent(t, 5)
switch event := evOrErr.ev.(type) {
case ConfigureNotifyEvent: