Test cases

[gurdeep330]

Write tests to check with different inputs

[gurdeep330]

Hi @raimondifranc @nataliarosa9 @maticmarin ,

As we had discussed several weeks ago (Rob's email), I added (to begin with) some cases that will be automatically tested by GitHub (check folder) using the package pytest
As of now, every time we push any change to GitHub, it will automatically make the following checks:

1. Input: TP53 Expected: NOT OK (TP53 is not a GPCR)
2. Input: P32249 Expected: OK (this is a GPCR)
3. Input MC1R/M294L Expected: OK (this is a GPCR)
4. Input P046 Expected: NOT OK (Invalid UniProt Acc)
5. Input AGRV1_HUMAN Expected: NOT OK (though it is a GPCR but the len > 1024)

Since these tests involve running precogx (command line) via GitHub actions, it will also throw an error if the tests fail for any other reasons (eg: UniProt updates its API and thus precogx script fails - like what happened when Rob wrote us).

I will add more tests in the next weeks (eg: check if the position of the variant is incorrect). Hopefully, with this, we will avoid running into situations where precogx fails because of some stupid backend errors.

Let me know if you have more tests to suggest.

nice weekend,
gd

PS: this is still in branch beta. Will merge with main later (after you also have reviewed the frontend changes)

[raimondifranc]

Hi Gurdeep, wonderful, thank you so much. @marin: would you please try to input the top designed GNA13-Dreadd candidates sequences to see if they somehow cluster in the PCA panel of the new webserver version (https://precogxb.bioinfolab.sns.it/)? BTW, I'm tight until the end of the month, but it would be good to plan a new meeting in November. Thanks and all the best, Francesco

…

On Fri, Oct 14, 2022 at 5:34 PM Gurdeep Singh ***@***.***> wrote: Hi @raimondifranc <https://github.com/raimondifranc> @nataliarosa9 <https://github.com/nataliarosa9> @maticmarin <https://github.com/maticmarin> , As we had discussed several weeks ago (Rob's email), I added (to begin with) some cases that will be automatically tested by GitHub (check folder <https://github.com/raimondilab/precogx/tree/beta/tests>) using the package *pytest* As of now, every time we push any change to GitHub, it will automatically make the following checks: 1. *Input*: TP53 *Expected*: NOT OK (*TP53 is not a GPCR*) 2. *Input*: P32249 *Expected*: OK (*this is a GPCR*) 3. *Input* MC1R/M294L *Expected*: OK (*this is a GPCR*) 4. *Input* P046 *Expected*: NOT OK (*Invalid UniProt Acc*) 5. *Input* AGRV1_HUMAN *Expected*: NOT OK (*though it is a GPCR but the len > 1024*) Since these tests involve running precogx (command line) via GitHub actions, it will also throw an error if the tests fail for any other reasons (eg: UniProt updates its API and thus precogx script fails - like what happened when Rob wrote us). I will add more tests in the next weeks (eg: check if the position of the variant is incorrect). Hopefully, with this, we will avoid running into situations where precogx fails because of some stupid backend errors. Let me know if you have more tests to suggest. nice weekend, gd PS: this is still in branch beta. Will merge with main later (after you also have reviewed the frontend changes) — Reply to this email directly, view it on GitHub <#93 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACHY44IE4WGP2ZRWNQR7VH3WDF4PHANCNFSM6AAAAAAREVWCAY> . You are receiving this because you were mentioned.Message ID: ***@***.***>