Mailingliste - Einträge 2013
Mailingliste - Einträge 2013
Die Mailingliste ist seit Juli 2022 geschlossen, dient aber weiterhin als Informationsarchiv zu QF-Test.
Wenn Sie über Neuerungen zu QF-Test informiert bleiben wollen, können Sie einfach unseren Newsletter abonnieren:
Newsletter abonnieren
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [QF-Test] Obfuscated classes, Luciad Map use (and JXLayer)
Good morning, I have globally two main
questions that a member of QFTest adviced me to ask here, in this forum. First, has anyone ever used QFTest with an obfuscated code? In fact, a large part of
our code is obfuscated and, evidently, we want it to stay like this.
Nevertheless, we can know the hierarchy of the obfuscated elements (we just
non-obfuscate the code in another window just to have the information, but we
don't want to use a non-obfuscated code in our futur tests in QFTest). So : -
is it possible to access the obfuscated code if we know the entire hierarchy of
the component? - we
thought about coding a « resolver » taking in entry the mapping file
generated by proguard. This, in order to resolve the obfuscated classes. We
would like to know if it is a possible solution with QFTest and how many time it would take to make
it (we are obligated to give results very soon). - we also thought about
ensuring that this obfuscation does not
change from one version to another which
is normally possible with
Proguard. But we are not sure that this would resolve the entire problem
and won’t be too binding? - Finally, more generally, have you got advices for us or
returns of experiences on obfuscation, please? Second, have you ever used Luciad maps
or similar maps/systems with QFTest? Indeed, on our
Software, we use Luciad maps. We saw in the forum that a Luciad employee posted a question (26 Oct
2002 16:03:24) on components snapshots and we wondered if it is the best way to
identify components on these maps in order to be capable of getting its own component
properties (color, position...). In fact, we sent questions to a
person of QFTest who adviced us to use an ItemResolver but he was not so sure and
told us to ask the question because he does not know for the specific case of
the Luciad maps which has particularities : To be more precise, Luciad gives an environment where the components,
which are on the background map, are not really distinguished. In fact, the
whole interface (background map + the elements on it) are seen as a single
drawing, not as known objects (like JButton, for example). Knowing this, have you
other recommendations that will permit us to use QFTest with this type
of configuration? So, has anybody ever used an itemResolver or other methods
with this type of configuration, have you any experience on this? For it we have two components, one above the other. On the one which is
below we would like to access a great number of objects that it contains but it
is not possible due to the one which is above. So we do not know how to access
this JXLayer which is above : is it possible with QFTest to copy all the objects
on the JXLayer on the top or is there any other method to access them? We have been told by a
member of QFTest that it may function with “JLayers” and we would like to know
if there are special moduls in QFtest for the "JXLayer" or if anybody
has ever used it? Thank you very much
for your return, Best regards, Déborah.
|
Wir verwenden Cookies zur anonymisierten Auswertung Ihres Besuchs auf unserer Webseite durch »Matomo«. Dafür benötigen wir Ihr Einverständnis, welches für zwölf Monate gilt. Ein Widerruf bzw. Opt-out ist jederzeit auf unser Datenschutz-Seite möglich.
1. Funktionale Cookies
Wir verwenden funktionale Cookies, um die Basisfunktionalität der Webseite zu gewährleisten.
2. Performance und Statistik Cookies
Wir verwenden Matomo zur Analyse und Optimierung unserer Webseite. Cookies erlauben eine anonyme Erfassung der Informationen und helfen uns, Ihnen einen benutzerfreundlichen Besuch unserer Webseite zu bieten.
Dieses Cookie enthält eine eindeutige jedoch pseudonymisierte Matomo-interne Besucher-ID zur Erkennung wiederkehrender Besucher.
Dieses Cookie wird verwendet, um zu tracken, von welcher Website der anonymisierte Benutzer auf die Website gekommen ist.
Das Session Cookie von Matomo wird verwendet, um die Seitenanforderungen des Besuchers während der Sitzung zu verfolgen.
wird erzeugt und versucht sofort wieder zu löschen (zur Prüfung, ob der Browser des Besuchers Cookies unterstützt).
Kurzzeit-Cookies für temporäre Besuchsdatenspeicherung.
Kurzzeit-Cookies für temporäre Besuchsdatenspeicherung.
