iRefScape Test Cases 1.0

Last edited: 2011-04-19

Search cases

Test case name: UniProt_Ac 1

Operation:

Query box:

Q39009
Q9ZNV8

Search type: UniProt_Ac

Taxon id: Any

Iterations: 1

Create new view: no

Use canonical expansion: no

Add edges between neighbours: no

Expected Observation:

33 nodes, 94 edges. 2 queried nodes are blue (DMC_ARATH and AHP2_ARATH). Checked node AHP2_ARATH linkout from i.RefSeq_Ac_TOP attribute to Entrez/protein was correct. IRefIndex has correct i.taxid and i.geneID.

Checked node AHP2_ARATH linkout from i.UniProt_Ac_TOP attribute to UniProt/KB beta was correct. IRefIndex has correct i.taxid and i.geneID. UniProt record agreed with iRefIndex on iRefSeq_Ac_TOP, i.taxid, i.geneID.

Selected two edges between query nodes : EBI-1555390, EBI-1555417. Checked linkouts for both edges (i.src_intxn_id) to Interaction databases/Intact. Confirmed that i.PMID and i.method_name were correct. Viewed EBI-1555390 in MI-XML 2.5 format and confirmed that i.RefSeq_Ac_TOP, i.UniProt_Ac_TOP, i.type_cv, i.type_name were correct. Note that NP_188928.2 was listed by IntAct while i.RefSeq_Ac_TOP listed NP_188928. The molecule names were DMC1 and ATHP1 in intact and these names were available under interactor_alias attribute Checked linkout to http://wodaklab.org/iRefWeb/interaction/show/102203 from both interactions above.

Last tested: April 18, 2011

Plugin Version: 1.00

Data Version: 8.0

Result: PASS

Tester: Sabry

Notes: :(SABRY) : Although this is a pass, the index file name was included the control tag _EXT_ (To perform only exact matches), therefore behavior has to be retested in beta 0.84

Test case name: RefSeq_Ac 1

Operation:

Query box:

NP_188928.2

Search type: RefSeq_Ac

Taxon id: Any

Iterations: 1

Create new view: yes

Use canonical expansion: no

Expected Observation:

11 nodes, 29 edges. i.RefSeq_Ac = NP_188928 was returned. Edges returned include two edges described in test UniProt_Ac 1.

The same results are returned if the query box is changed to NP_188928.

The same results are returned if the query box is changed to NP_188928.567.

The same results are returned if the query box is changed to 188928. This should return 0 results. FAIL. What if the user meant to search for geneIds and had mistakenly selected this search type. This is an exact match search except for characters trailing the .

No results are returned if the query box is changed to NP 188928. Ok.

Change the search type to UniProt_Ac. The interface says no results and when user presses ok, shows a blank panel. Ok.

The search type can also be changed to UniProt_ID, geneID, geneSymbol, ipi,, mass or rog with no results returned.

No results are returned if the query box is changed to 0. Error message says : Error resolving query. Ok.

No results are returned if the query box is changed to abcde.

Last tested: June 1, 2010

Plugin Version: 0.83

Data Version: 7.0 public

Result: NOT TESTED

Tester: Ian

Notes: :(SABRY) : The index file name was included the control tag _EXT_ (To perform only exact matches), Behavior has to be retested in beta 0.84

Test case name: UniProt_ID 1

Operation:

Query box:

AHP2_ARATH

Search type: UniProt_ID

Taxon id: Any

Iterations: 1

Create new view: yes

Use canonical expansion: no

Expected Observation:

26 nodes, 67 edges.

The same results are returned if the query box is changed to AHP2. FAIL. This should not be allowed. The user might have entered gene names, selected UniProt_ID by mistake and would not be aware of their mistake because their search returned results. Also, first few characters of UniProt_ID's may be shared by multiple proteins from different organisms. If you want to allow for inexact matches, use the query helper.

AHP2 ARATH returns no results. Ok.

ARATH returns "1001 matches and only first 1000 are shown". Ok. Inexact matches trigger the query helper.

AH2_ARATH returns CAH2_ARATH. It should return 0 results. FAIL. Imagine if the user accidently had such a query term imbedded in a long list. They would never detect this search error! This should be is an exact match search by default (or use the query helper to allow the user to decide.

AHP2_ARATH.2 returns results. It should return 0 results. FAIL.

23 returns query helper dialog for disambiguation. Ok. But not very useful in this artificial test case.

Searching for AHP2_ARATH but with search type UniProt_Ac, geneID, geneSymbol, ipi or mass all return 0 results. The interface says no results and when user presses ok, shows a blank panel. Ok.

No results are returned if the query box is changed to 0. Error message says : Error resolving query. Ok.

No results are returned if the query box is changed to abcde.

Last tested: June 1, 2010

Plugin Version: 0.83

Data Version: 7.0 public

Result: NOT TESTED

Tester: Ian

Notes: :(SABRY) : UniProt_ID is now EXACT match only. If the user failed to enter exactly matching query no results will be returned. Query helper will never be invoked.

Test case name: geneID 1

Operation:

Query box:

821860
822593

Search type: geneID

Taxon id: Any

Iterations: 1

Create new view: yes

Use canonical expansion: no

Expected Observation:

Should return the same result as a UniProt_Ac query for Q39009 and Q9ZNV8 (33 nodes and 94 edges). Ok.

0 returned "error resolving query. Ok.

00001 returned 0 results. Ok.

abcdes returned 0 results. Ok.

1234 returned 34 nodes and 70 edges. Ok. 1234 is CCR5.

Retrieved all geneIds from above query and queried (iterations = 0). Should return same number of nodes as above (33 protein nodes). But 30 protein nodes are returned and there are differences. NOTE. Keep this example for further reference. Explanation. Two of the nodes from the first graph did not have a gene id. Two nodes had the same gene id 7852. If you search for 7852, a graph of 12 nodes, 21 edges is returned. But only one of the nodes has a gene id of 7852. This seems like the search does not continue past the first match found?! FAIL until this is resolved. Also check that all other searches that are exact match searches are "continue after first match found" and write in test cases to ensure that this happens.

The gene in question is CXCR4 and has two isoforms (P61073-2 and P61073).

A geneSymbol search for CXCR4 (iteration=0) returns two nodes as expected.

A UniProt_Ac search for P61073-2 or P61073 each return only one node when use canonical expansion is turned off. Each search returns two nodes when canonical expansion is turned on. By default, canonical expansion should be turned on. A hidden advanced option should be made available to turn this off.

This can be used as a test case for the Export function "on Target network Node ID type"= i.Canonical_ROGID_TOP

Searched 821860 but by each other search type. No results returned in any case. Ok

Last tested: June 1, 2010

Plugin Version: 0.83

Data Version: 7.0 public

Result: NOT TESTED

Tester: Ian

Notes: :(SABRY) : The search results of a protein accession and a gene identifier (which could refer to more than one protein) will not be the same and it is OK as I see it (correct me if I am wrong). But as requested if canonical expansion is turned on the results will be the same. Although this is a very good suggestion for this search , I am sorry that I am against the idea of default canonical expansion and hiding the stop expansion in advanced (which is now features under development) (but this does not mean I will not implement it).

1. When turned on canonical expansion affects many of the default behavior (abstract implementations) i.e I use the same network construction for ROG ,molecular mass and geneID and so on.
2. The expansion uses a second phase index to index mapping and this slows down the query.
3. Batch quires will take long time to complete and will get more interactions (This seems to be a good thing, but the current network is already to much information), and the user has the option to expand if wanted

• Let me know the final decision,

Test case name: geneSymbol 1

Operation:

Query box:

CXCR4

Search type: geneSymbol

Taxon id: Any

Iterations: 0

Create new view: yes

Use canonical expansion: no

Expected Observation:

Returns two nodes with i.UniProt_Ac_TOP of P61073 and P61073-2.

Change search to PTK2. The user should be warned that they have not selected a taxon. "You have not limited your search to a specific organism. Proceed anyway? Yes No

FAIL. No warning is given. With no taxon specifier present, the search (iteration=0) returns 6 nodes and 5 taxons. This will create havoc if the user has searched using a list of identifiers.

0 returns no results. Ok.

0000 returns no results. Ok.

12345 returns no results. Ok.

abcde returns no results. Ok.

cxcR4 returns identical results to CXCR4. Ok.

CXCR prompts the user to select from a set of possibilities. Linkouts to NCBI are impossible to use. FAIL. Take this hyperlink feature out until a later release. This should be an exact match search unless the user specifically asks for related terms.

A search for "CXC CXCR CXCR4" returns results identical for CXCR4. Ok. The provides a helper window and a chance to refine the query. User can select one or more specific terms for each ambiguous term (using shift or cntrl keys and pressing return to add the selected items to a new search). The user should be informed of their options. FAIL. Message should read:

"One or more of your query terms did not have an exact match. For each term on the left, you may select one or more of the refined terms on the right (shift-click and cntrl-click are supported). Press return to add the selected terms to a new query. Clear the "Create new view" tick-box if you want to add the results to the current view."

Search CXCR5 as a UniProt_ID, presented user with option for refining the query. Ok

Search CXCR5 against other query types returned no results. Ok.

Last tested: June 1, 2010

Plugin Version: 0.83

Data Version: 7.0 public

Result: NOT TESTED

Tester: Ian

Notes: :(SABRY) :

1. hyperlink removed
2. Do you want to check the taxonid only for geneSymbol ?
3. The default batch file mode the user has to specify a taxonid, this was overridden as requested in an earlier release should this be reactivated?.

Test case name: geneSymbol 2

Operation:

Query box:

RPB1

Search type: geneSymbol

Taxon id: Any

Iterations: 0

Create new view: yes

Use canonical expansion: no

Expected Observation:

RPB1 for any taxon returns 1 node (RPB1_SCHPO). Ok.

RPB1 for taxon 4932 returns 0 nodes. Ok. Even though an alias for yeast RPO21 (Gene Id 851415) is RPB1, this search only searches on official gene symbols from Entrez.

RPB1 for taxon 9606 returns 3 nodes one of which is SIRPB1. FAIL. This is an exact match search.

Last tested: June 7, 2010

Plugin Version: 0.83

Data Version: 7.0 public

Result: NOT TESTED

Tester: Ian ' Notes: ':(SABRY) :Changed to exact search.

1. There is a conflict between Test case name: geneID 1 and Test case name: geneID 2. When the search is now made a exact search, the query helper will never pop-up.

Test case name: rog search 1

Operation:

Query box:

5366033

Search type: rog

Taxon id: Any

Iterations: 1

Create new view: no

Use canonical expansion: no

' Notes: ':(SABRY) The bug coursing freeze when performing ROG searches is fixed in 0.85

Test case name: Iterations 1

Operation:

Perform search described in test UniProt_Ac 1 with Iterations=1. Then again with Iterations = 0 and confirm that the number of edges between the query nodes is identical.

Expected Observation:

Same number of edges (2 edges, 1 loop) in both cases.

Last tested: June 1, 2010

Plugin Version: 0.83

Data Version: 7.0 public

Result: NOT TESTED

Tester: Ian

Notes:

Test case name: ipi 1 #

Operation:

Query box:

IPI00543858
IPI00517160

Search type: ipi

Taxon id: Any

Iterations: 1

Create new view: no

Use canonical expansion: no

Expected Observation:

Returns results identical to test case UniProt_Ac 1. Ok

Changing the query to "IPI00543858.1 IPI00517160.1" produces identical results. Ok.

Changing the query to "00543858 00517160" produces identical results. Ok.

Changing the query to "00543858 0051716" produces identical results for first query term and initiates query helper to resolve second term. Ok.

Changing the query to "abcd" produces no results. Ok.

Changing the query to "IPI" initiates query helper. Ok.

Searching for IPI00543858 as any other search type returns no results. Ok

Last tested: June 1, 2010

Plugin Version: 0.83

Data Version: 7.0 public

Result: NOT TESTED

Tester: Ian

Notes:

Test case name: mass search #

Operation:

Query box:

72854<-->72866

Search type: ipi

Taxon id: Any

Iterations: 0

Create new view: yes

Use canonical expansion: no

Expected Observation:

The user is presented with the query helper to refine the query. A prompting message reads:

"One or more of your mass query terms corresponds to a range. You may select one or more of the masses on the right (shift-click and cntrl-click are supported). Press return to add the selected terms to a new query. Clear the "Create new view" tick-box if you want to add the results to the current view."

FAIL. The message given should be replaced with the above text. Also, there are inappropriate and unusable links to NCBI given in the query helper. Also, interface changes my selected iterations from 0 to 1 without asking. Annoying.

The query returns 4 nodes with mass in the expected range. Ok.

0 returns no results. Ok.

-1 returns no results. Ok.

MW returns no results. Ok.

72854 kda returns no results but hangs the interface. FAIL.

Last tested: June 1, 2010

Plugin Version: 0.83

Data Version: 7.0 public

Result: NOT TESTED

Tester: Ian

Notes:

Test case name: PMIDsearch 1

Operation:

Query box:

11401546

Search type: pmid

Taxon id: Any

Iterations: 0

Create new view: yes

Use canonical expansion: no

Expected Observation:

4 nodes and 7 edges are returned. Three edges have PMID 11401546 and these involve the 4 nodes shown. All other edges (from different PMIDs) involve these proteins. Ok.

11401546.1 returns 0 results. Ok.

1140154 returns 0 results and starts query helper. FAIL. This should be an exact match search.

SPTAN1 returns 0 results. Ok.

11401546 SPTAN1 returns 0 results. Ok.

0 finds 21493 matches and then says there are no results and open the query helper. FAIL. This is an exact match search.

-1 returns 0 results. Ok.

10551855 [return character] 11401546 returns 6 nodes and 27 edges. Ok.

10551855|11401546 returns 6 nodes and 27 edges. Ok.

10551855| 11401546 returns 6 nodes and 27 edges. Ok.

10551855 | 11401546 returns 6 nodes and 27 edges. Ok.

10551855 [tab] 11401546 returns 6 nodes and 27 edges. Ok.

10551855, 11401546 returns 6 nodes and 27 edges. Ok.

10551855 11401546 returns 0 results. Ok. We dont day we support space delimited queries.

Last tested: June 7, 2010

Plugin Version: 0.83

Data Version: 7.0 public

Result: NOT TESTED

Tester: Ian

Notes:

Test case name: example search 1

Operation:

Test the example searches listed at http://irefindex.uio.no/wiki/README_Cytoscape_plugin_0.8x#Using_the_Search_Panel

Query box: see below

Search type: see below

Taxon id: Any

Iterations: 1

Create new view: yes

Use canonical expansion: yes

Expected Observation:

Search Type	Example	Results
UniProt_Ac	Q7KSF4	67 nodes, 146 edges. 4 nodes are returned directly by the query, but only one is marked with i.query = Q7KSF4. FAIL nodes returned by a query (even with canonical expansion) should have an i.query value. i.order is 0 for Q7KSF4 but 10 for the other three nodes from the same canonical group. CAUTION. This is not what the documentation says for these attributes. With canonical expansion off, this search returns 43 nodes, 43 edges all from BioGRID.
RefSeq_Ac	NP_996224	67 nodes, 146 edges. See above. i.query feature fails to update to reflect the most recent search. FAIL.
UniProt_ID	Q7KSF4_DROME	67 nodes, 146 edges.
geneID	42066	67 nodes, 146 edges. See above. Now two nodes are marked as Q7KSF4 under i.query. FAIL. 42066 should be listed for the recently returned node.
geneSymbol	cher	67 nodes, 146 edges. Now i.query says Q7KS4 for all four nodes returned by the search. FAIL.
mass	72854<-->72866	40 nodes, 94 edges. Four molecular mass values are returned by the query helper. Selecting all of these and doing the search returns 8 hi-lited nodes and their interactors. The 72855 mass node returns 1 node with that mass and two other members of the same canonical group. Two of the nodes are returned with i.query of Q7KSF4. FAIL.
rog	10121899	FAIL. This should return the Q7KSF4 node. Instead got "Sorry, please wait until current operations finish or stop the proces and restart Cytoscape." Subsequent searches do not work. Have to restart Cytoscape
PMID	14605208	929 nodes and 1605 edges returned all with PMID of 14605208. SAme results if iteration is set to 0. Ok. Same results if canonical expansion is de-selected. Ok.
src_intxn_id	47513	2 nodes and 1 edge returned.
src_intxn_id	EBI-212627	2 nodes and 4 edges returned (2 from intact, 1 from BIND and 1 from MINT). Ok
src_intxn_id	147805	Returns 4 nodes and three interactions because BIND and BioGRID interaction id space overlap.
omim	227650	74 nodes and 224 edges returned. Ok.
digid	449	58 nodes and 60 edges returned. FAIL. This should return the same results as omim 227650 plus more nodes that have the same digid. digid search is like searching for multiple omims. Problem with file name _EXT__ROG_digid.irft
dig_title	fanconi	FAIL - do not fix until next release.

Last tested: June 7, 2010

Plugin Version: 0.83

Data Version: 7.0 public

Result: NOT TESTED

Tester: Ian

Notes:

Preferences

Test case name: what is being tested #

Operation:

Expected Observation:

Last tested: July 8, 2010

Plugin Version: 0.83

Data Version: 7.0

Result: NOT TESTED

Tester: Ian

Notes:

Test case template

Test case name: what is being tested #

Operation:

Expected Observation:

Last tested:

Plugin Version:

Data Version:

Result: NOT TESTED

Tester:

Notes:

to be corrected

• Remove the non-proprietary flag/check for current data
• Handle the neighbourhood completion when expanding network (do not use all the nodes)