Tests summary

This page summarises information for results of test cases for Last 25 builds in Jalview Builds - Gradle Develop Build - patch-JAL-4410_multimers_from_3dbeacons - Clover and Tests.

Test	Times broken	Most recent builds
Check import p a e to structure(examples/ alpha fold/ a f- q5 v s l9- f1-model v4.pdb, examples/ alpha fold/ a f- q5 v s l9- f1-predicted aligned error v4 cmp.json)	2	2
Check import p a e for structure(examples/ alpha fold/ a f-0000000203848083-model v1.cif, examples/ alpha fold/ a f-0000000203848083-predicted aligned error v1.json)	1	3

There have been no fixed test cases identified in this plan for Last 25 builds.

Test	Average duration (seconds)*
Coverageof range	23 seconds
Open crossrefs for ensembl twice	12 seconds
Store and recover reference seq settings	12 seconds
Store and recover expandedviews	12 seconds
Version checker	10 seconds
Headless or gui image output test([ ljava.lang. string;@4ee8051c, [ ljava.lang. string;@53125718)	9 seconds
Headless or gui image output test([ ljava.lang. string;@621f23ac, [ ljava.lang. string;@7761e342)	9 seconds
Headless or gui image output test([ ljava.lang. string;@7f0766ef, [ ljava.lang. string;@1e56bc9b)	8 seconds
Do structure opening args test(--gui --nonews --nosplash --debug --nowebservicediscovery --props=test/jalview/bin/commands test.jvprops --open=./examples/uniref50.fa --structuresfile=./examples/structuresfile.txt --structure=./examples/ s m- p83527- f e r c a p a a.pdb --seqid= f e r c a p a a --nosuperpose --viewerid=id1 --structuresfile=./examples/structuresfile2.txt , -1, -1, -1, 3)	7 seconds
Do structure opening args test(--gui --nonews --nosplash --debug --nowebservicediscovery --props=test/jalview/bin/commands test.jvprops --open=./examples/uniref50.fa --structuresfile=./examples/structuresfile.txt --structure=./examples/ s m- p83527- f e r c a p a a.pdb --seqid= f e r c a p a a --nosuperpose --viewerid= t h i s --structuresfile=./examples/structuresfile2.txt , -1, -1, -1, 2)	6 seconds

* average duration is calculated based on the entire history of this test.

The chart below shows the number of tests across time. This provides a rough indication of the level of testing over time for the build.