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
2021.07.15 - Thursday - 6.00P.M - 7.00P.M
2021.07.15 - Thursday - 7.00P.M - 8.00P.M
2021.07.15 - Thursday - 8.00P.M - 9.00P.M
2021.07.16 - Friday - 6.00P.M - 7.00P.M
2021.07.16 - Friday - 8.00P.M - 9.00P.M
Friday from 7 to 8 we have the web squad call right?? maybe you wanna remove that option @anjisvj
1 Like
Oops, yeah Thanks for reminding.
None of the time slots work for me.
1 Like
Before doing the QA we have to do a release cuz there are some improvements in the development branch in the frontend.@YohanAvishke @Gravewalker
1 Like
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?
1 Like
@Gimhan_minion Can you give us an update regarding the email template function?
Time is finalised for the call.
ScholarX Final QAhttps://meet.google.com/ytq-twbt-qqu
Just finished finalizing the PR. @anjisvj
sef-global:development ← Gimhan-minion:email-temp
opened 11:33AM - 15 Jul 21 UTC
## 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
### 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
1 Like
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
Here are the relevant GitHub issues,
opened 04:30AM - 17 Jul 21 UTC
**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
opened 05:25AM - 17 Jul 21 UTC
**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',
},
```
opened 02:51PM - 16 Jul 21 UTC
**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
opened 06:21AM - 17 Jul 21 UTC
**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
opened 08:02AM - 17 Jul 21 UTC
**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
1 Like
