# Final QA before launching ScholarX for the pilot

**URL:** <https://sef.discourse.group/t/final-qa-before-launching-scholarx-for-the-pilot/328>\
**Category:** ScholarX\
**Created:** [July 14, 2021, 4:02pm UTC](https://sef.discourse.group/t/final-qa-before-launching-scholarx-for-the-pilot/328 "2021-07-14T16:02:29Z")\
**Posts on this page:** 11\
**Page:** 1

<div class="post-metadata">

**Author:** ![anjisvj](https://yyz2.discourse-cdn.com/free1/user_avatar/sef.discourse.group/anjisvj/32/9_2.png) [@anjisvj](https://sef.discourse.group/u/anjisvj)\
**Post date:** [July 14, 2021, 4:02pm UTC](https://sef.discourse.group/t/final-qa-before-launching-scholarx-for-the-pilot/328/1 "2021-07-14T16:02:30Z")

</div>

We successfully finished the backend stress test thanks to @piumal1999 we are ready to launch the ScholarX platform for the pilot. Before that, we need to do a final QA to make sure that we don’t have any bugs. It’s better to do it using a small call.

Please add your availability for the QA call, [@EngTeam](https://sef.discourse.group/groups/engteam)

_Poll ([view on site](https://sef.discourse.group/t/final-qa-before-launching-scholarx-for-the-pilot/328/1))_

---

<div class="post-metadata">

**Author:** ![Gravewalker](https://yyz2.discourse-cdn.com/free1/user_avatar/sef.discourse.group/gravewalker/32/12_2.png) [@Gravewalker](https://sef.discourse.group/u/Gravewalker)\
**Post date:** [July 14, 2021, 4:12pm UTC](https://sef.discourse.group/t/final-qa-before-launching-scholarx-for-the-pilot/328/2 "2021-07-14T16:12:26Z")

</div>

Friday from 7 to 8 we have the web squad call right?? maybe you wanna remove that option @anjisvj

---

<div class="post-metadata">

**Author:** ![anjisvj](https://yyz2.discourse-cdn.com/free1/user_avatar/sef.discourse.group/anjisvj/32/9_2.png) [@anjisvj](https://sef.discourse.group/u/anjisvj)\
**Post date:** [July 14, 2021, 4:13pm UTC](https://sef.discourse.group/t/final-qa-before-launching-scholarx-for-the-pilot/328/3 "2021-07-14T16:13:31Z")

</div>

Oops, yeah Thanks for reminding.

---

<div class="post-metadata">

**Author:** ![Gravewalker](https://yyz2.discourse-cdn.com/free1/user_avatar/sef.discourse.group/gravewalker/32/12_2.png) [@Gravewalker](https://sef.discourse.group/u/Gravewalker)\
**Post date:** [July 14, 2021, 5:08pm UTC](https://sef.discourse.group/t/final-qa-before-launching-scholarx-for-the-pilot/328/4 "2021-07-14T17:08:50Z")

</div>

None of the time slots work for me. ☹

---

<div class="post-metadata">

**Author:** ![anjisvj](https://yyz2.discourse-cdn.com/free1/user_avatar/sef.discourse.group/anjisvj/32/9_2.png) [@anjisvj](https://sef.discourse.group/u/anjisvj)\
**Post date:** [July 15, 2021, 6:43am UTC](https://sef.discourse.group/t/final-qa-before-launching-scholarx-for-the-pilot/328/5 "2021-07-15T06:43:41Z")

</div>

Before doing the QA we have to do a release cuz there are some improvements in the development branch in the frontend.  
cc: @YohanAvishke @Gravewalker

---

<div class="post-metadata">

**Author:** ![Gravewalker](https://yyz2.discourse-cdn.com/free1/user_avatar/sef.discourse.group/gravewalker/32/12_2.png) [@Gravewalker](https://sef.discourse.group/u/Gravewalker)\
**Post date:** [July 15, 2021, 6:47am UTC](https://sef.discourse.group/t/final-qa-before-launching-scholarx-for-the-pilot/328/6 "2021-07-15T06:47:27Z")

</div>

Yup, we can add the email template function as well to the release notes. I don’t think it’s finalised but we do have the functionality.  
@anjisvj what is the progress on that?

---

<div class="post-metadata">

**Author:** ![anjisvj](https://yyz2.discourse-cdn.com/free1/user_avatar/sef.discourse.group/anjisvj/32/9_2.png) [@anjisvj](https://sef.discourse.group/u/anjisvj)\
**Post date:** [July 15, 2021, 8:31am UTC](https://sef.discourse.group/t/final-qa-before-launching-scholarx-for-the-pilot/328/7 "2021-07-15T08:31:28Z")

</div>

@Gimhan_minion Can you give us an update regarding the email template function?

---

<div class="post-metadata">

**Author:** ![anjisvj](https://yyz2.discourse-cdn.com/free1/user_avatar/sef.discourse.group/anjisvj/32/9_2.png) [@anjisvj](https://sef.discourse.group/u/anjisvj)\
**Post date:** [July 15, 2021, 9:03am UTC](https://sef.discourse.group/t/final-qa-before-launching-scholarx-for-the-pilot/328/8 "2021-07-15T09:03:17Z")

</div>

Time is finalised for the call.

ScholarX Final QA  
Friday, July 16 · 6:00 – 7:00pm  
Google Meet joining info  
Video call link: [https://meet.google.com/ytq-twbt-qqu](https://meet.google.com/ytq-twbt-qqu)

---

<div class="post-metadata">

**Author:** ![Gimhan\_minion](https://yyz2.discourse-cdn.com/free1/user_avatar/sef.discourse.group/gimhan_minion/32/109_2.png) [@Gimhan\_minion](https://sef.discourse.group/u/Gimhan_minion)\
**Post date:** [July 15, 2021, 12:44pm UTC](https://sef.discourse.group/t/final-qa-before-launching-scholarx-for-the-pilot/328/9 "2021-07-15T12:44:04Z")

</div>

Just finished finalizing the PR. @anjisvj

> <https://github.com/sef-global/scholarx/pull/177>
>
> \## Purpose
> The purpose of this PR is to fix #174 
> 
> \## Goals
> \- To make Schola…rX email notification more attractive and user friendly
> 
> \## Approach
> \- Added SEF logo and SEF social media links
> \- Add a button to directly access the dashboard
> 
> \### Screenshots
> !\[Screenshot from 2021-07-15 16-50-38\](https://user-images.githubusercontent.com/60275681/125781357-b523f469-4b9a-4fd3-8bcf-d475ae50fc8f.png)
>   
> \### Preview Link
> N/A
> 
> \## Checklist
> \- \[x\] This PR doesn't commit any keys, passwords, tokens, usernames, or other secrets.
> \- \[x\] I have read and understood the development best practices guidelines ( http://bit.ly/sef-best-practices )
> \- \[x\] My code follows the style guidelines of this project
> \- \[x\] I have performed a self-review of my own code
> \- \[\] I have commented my code, particularly in hard-to-understand areas
> \- \[\] I have made corresponding changes to the documentation

---

<div class="post-metadata">

**Author:** ![anjisvj](https://yyz2.discourse-cdn.com/free1/user_avatar/sef.discourse.group/anjisvj/32/9_2.png) [@anjisvj](https://sef.discourse.group/u/anjisvj)\
**Post date:** [July 16, 2021, 2:08pm UTC](https://sef.discourse.group/t/final-qa-before-launching-scholarx-for-the-pilot/328/10 "2021-07-16T14:08:08Z")

</div>

### QA call

# 2021-07-16T12:30:00Z

Attendees: @Gravewalker, @Gimhan_minion, @kumuditha_udayanga , @DESIRA , @cmdrGuyson , @YohanAvishke , @piumal1999 , @Neith , @YaiyaSam, @anjisvj

Using a test program a live QA session was held here are the bugs we found and who’s gonna work on them.

- Lorem Ipsum near change state button of programs in admin dashboard - @kumuditha_udayanga
- Mentor Question numbers are incorrect(those are getting retrieved as the table ids) - @anjisvj
- Login popup comes when refreshing and in the mentor application question - @anjisvj
- New LinkedIn user exception null. request to retrieve the token is getting 401. It was caused due to not adding a profile picture
- Prevent mentors from editing application after approval(from both backend and frontend)
- Emails were not received after mentor confirmation @cmdrGuyson
- Mentee applications view is not working - @Neith
- MENTEE\_APPLICATION period showing a manage button for mentors (in my programs) - @kumuditha_udayanga

---

<div class="post-metadata">

**Author:** ![anjisvj](https://yyz2.discourse-cdn.com/free1/user_avatar/sef.discourse.group/anjisvj/32/9_2.png) [@anjisvj](https://sef.discourse.group/u/anjisvj)\
**Post date:** [July 17, 2021, 6:12am UTC](https://sef.discourse.group/t/final-qa-before-launching-scholarx-for-the-pilot/328/11 "2021-07-17T06:12:23Z")

</div>

Here are the relevant GitHub issues,

> <https://github.com/sef-global/scholarx-frontend/issues/205>
>
> \*\*Describe the bug\*\*
> \- In the mentor application, where we have the mentor ques…tions it shows the wrong ID for the question number
> 
> \*\*To Reproduce\*\*
> Steps to reproduce the behavior:
> 1. Go to the mentor application
> 2. See the question numbers
> 
> \*\*Expected behavior\*\*
> \- Question numbers should be in the order
> 
> \*\*Desktop (please complete the following information):\*\*
> - OS: BigSur
> - Browser: Chrome

> <https://github.com/sef-global/scholarx-frontend/issues/206>
>
> \*\*Is your feature request related to a problem? Please describe.\*\*
> \- Currently,… We have dummy text in the change state program view under the admin dashboard 
> 
> \*\*Describe the solution you'd like\*\*
> \- Replace the following text with this,
> 
> \`\`\`
> {
> stepNo: 0,
> name: 'Created',
> description:
> 'The program is in the created state',
> },
> {
> stepNo: 1,
> name: 'Mentor Applicaiton Period',
> description:
> 'In this state mentors can start sending their applications.',
> },
> {
> stepNo: 2,
> name: 'Mentor Approval Period',
> description:
> 'During this state, the admin can review the mentor application and approve or reject them ',
> },
> {
> stepNo: 3,
> name: 'Mentee Applicaiton Period',
> description:
> 'In this state mentees can start sending their applications.',
> },
> {
> stepNo: 4,
> name: 'Mentee Approval Period',
> description:
> 'During this state, mentors can review the mentor application and approve or reject them ',
> },
> {
> stepNo: 5,
> name: 'Mentor Confirmation',
> description:
> 'During this state, mentees can see their mentor and if they have been chosen by multiple mentors they can choose one of them as their mentor',
> },
> {
> stepNo: 6,
> name: 'Ongoing',
> description:
> 'This state indicates that the program is currently running',
> },
> {
> stepNo: 7,
> name: 'Completed',
> description:
> 'The program is completed',
> },
> \`\`\`

> <https://github.com/sef-global/scholarx-frontend/issues/204>
>
> \*\*Describe the bug\*\*
> \- MENTEE\_APPLICATION period showing a manage button for me…ntors (in my programs) 
> 
> \*\*To Reproduce\*\*
> \- Add a condition to prevent showing the button.
> 
> \*\*Expected behaviour\*\*
> A clear and concise description of what you expected to happen.
> \- 'Manage' button shouldn't appear to mentors in the "MENTEE\_APPLICATION" state.
> 
> 
> \*\*Desktop (please complete the following information):\*\*
> - OS: MacOS BigSur
> - Browser : Safari
> - Version : 14.0.1

> <https://github.com/sef-global/scholarx-frontend/issues/208>
>
> \*\*Describe the bug\*\*
> \- The login popup comes when the user refreshes the page.
> …
> 
> \*\*To Reproduce\*\*
> Steps to reproduce the behaviour:
> 1. Go to a page
> 2. Refresh the page
> 3. Login popup comes and goes
> 
> \*\*Expected behaviour\*\*
> \- The popup shouldn't come when the browser refreshed
> 
> \*\*Desktop (please complete the following information):\*\*
> - OS: BigSur
> - Browser : Chrome

> <https://github.com/sef-global/scholarx/issues/180>
>
> \*\*Describe the bug\*\*
> \- The emailing function we implemented is not working now.…
> 
> \*\*To Reproduce\*\*
> Steps to reproduce the behaviour:
> 1. Change the state of a program
> 2. See that email method is not getting called
> 
> \*\*Expected behaviour\*\*
> \- Users should get emails with relevant details
> 
> \*\*Desktop (please complete the following information):\*\*
> - OS: BigSur
> - Browser: Chrome
