This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Summary: | Window's Title isn't always constructed well | ||
---|---|---|---|
Product: | platform | Reporter: | dmladek <dmladek> |
Component: | Window System | Assignee: | Peter Zavadsky <pzavadsky> |
Status: | CLOSED WORKSFORME | ||
Severity: | blocker | CC: | issues, mslama |
Priority: | P2 | Keywords: | T9Y |
Version: | 3.x | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | DEFECT | Exception Reporter: | |
Attachments: |
Test failed 'cause of bad Window's title
jemmy.log testStatus.log |
Description
dmladek
2002-08-28 11:17:07 UTC
Created attachment 7228 [details]
Test failed 'cause of bad Window's title
Created attachment 7229 [details]
jemmy.log
Created attachment 7230 [details]
testStatus.log
I'd like to mention that after test finished, I performed another cvs->Status on another file. The output has been docket into previous frame. So now the Window has correct title and contains 2 TAB (each was holding the output of Status command of different file). Switching between those 2 TABs...was changing the Windows title, but always correctly... But don't think that it happens only when those actions are performed automaticaly! It also happens by hand... CC'ing the vcscore There's the related isuue: http://www.netbeans.org/issues/show_bug.cgi?id=26811 Maybe they are the same, but QA just doesn't "see" that the contents of the window is all-grey. Hmm. P2 and not reproducible? Window title contains name of selected top component in square brackets. If selected top component is null question mark is put there instead of tc name. Without way to reproduce (at least using automatic test) I cannot find why top component is not selected. This is P2 'cause it occures very often and breaks automatical test for version control modules eg. JavaCVSValidationTest.java You could see daily results on http://beetle.czech/automatedtests/xtest/ I know that now it is hard to find solution....but if you include some debug's messages... we could be faraway,can't we?;-) Please, let me know where is the test and how to run it, thanks. Pleaes provide the exact steps how to get and try out the test, otherwise I can't do anyting with it. Closing it up to that time. Hi Peter, excuse me I didn't answer your previous question:-( I was investigating if publishing on netbeans.org site of latest test's result will be corrected soon, so I could point you here, instead our internal web, but seems it won't:-((( So, if you look here,please: http://ffjqa.czech.sun.com/automatedtests/xtest/netbeans_dev/netbeans-qa-functional.html And see a few latest results on SunOS-5.8-sparc for JavaCVS module, you'll get mi true that it happens regulary. And how to execute this tests? Checkout javacvs module from cvs.netbeas.org Find JavaCVSValidationTest.java (javacvs/test/qa-functional/src/org/validation) How to set your testing environment, please read http://testtools.netbeans.org/ here, you could get all appropriate info or I could try to tell you all steps which I do for setting my env.: also checkout jemmy, jelly modules and compile them you need download xtestdistribution ->you need mount from it all junit*jars (or you could autoupdate junit, optionaly jemmysupport & jemmy & testools modules) http://xtest.netbeans.org/Download/license-xtest-distribution.html mount also core, openide, terminalemulator, vcscore, javacvs, cvslib jars. you need eddit jour junit.properties file :here is the example: ---- nbjunit.workdir=/home.local/danielm/junit/tests/workdir nbjunit.diff.impl=org.netbeans.junit.diff.NativeDiff nbjunit.diff.impl.CmdLine=/usr/bin/diff -bw %TESTFILE% %PASSFILE% ---- and then execute internaly JavaCVSValidationTest or you could executed via Xtest harness (as automation test are executed, but again I please you to read xtest.netbeans.org site how to set up it) Is it all clear? Don't hesitate to ask for other clarifications:) Thanks, I'll try to set it up. I have make one's excuse for reopening this issue. I had to be overworked too:-) I was thinking that this issue was a bug which I enter a few days ago with P4/P5 priority. And this issue #28592 is very similar to this...:-) But it happens only on Solaris 8 on CDE Win.Manager... It's quite senceless to continue work on this bug 'cause (without any explicit fixes) seems that issue disappeared... So, I'm closing it as WORKS FOR ME, and let's focus on issue #28592 (if you have a time...it not so serrious as this one probably was, and it is P4-P5 only on Solaris...) -Dan |