savvato-software / dtim-mobile Goto Github PK

In the I'm New Here screen, if you enter a valid name, and a string of 10 digits that is invalid for a phone number, the Sign Me Up button becomes enabled. It should not.

Notice that the validator for that field still reports an error, but it also has the wrong error message: it reads "The phone should be ten digits long.", when in fact it is 10 digits long, but should instead read "Those 10 digits are not valid for a phone number."

If I enter the same phone number or email address as one found in the database, I should get an error saying "We already have a profile with that info." They'd then clickOK and be taken back to the Home page, where they could choose the I'm Back For More! button, to enter that email or phone number, and be logged in.

And when you click on one, you should be able to see who signed in during that session, click on their name, go to their profile, etc.

When you are a new user, and you press the submit button on the New User form, you should get a spinner while it goes to the API, etc.

So ensure that changes to the file do not make it appear in the git status list.

The validator on the field will report a valid email address if you enter 'test@email' . It should report an error condition, and only report valid for truly valid email addresses. At a minimum, the current validator should also expect a period, and at least two characters, at the end of the string, in addition to what it currently expects. So '[email protected]' would be considered valid.

From the Admin page, Click on Manage Questions, select Data Structures at Level 1, then select the "Describe a Linked List" question. Notice on the Question View page, the correct line item level is highlighted in blue. Click on the Edit button. Expected: The same line item and level is highlighted in the Edit View, as you see in the View View.

n/m

n/m

I want to be able to add keywords to a persons profile. Most likely the scenario is the host in the Tech Interview Meeting, listening to someone's introduction. As the guest said something interesting, the host would add a keyword to their profile, one at a time, or maybe in a comma separated list.

The app should suggest keywords that often go with the ones I've already chosen. We should use the set of keywords on someone's profile as one part of the reasoning for how we decide which questions to give someone in a mock interview. Etc. Maybe people with that set find this question difficult, or we find the most successful placements have these keywords, and are able to answer these questions, so we may prioritize them. Like that.

The phone number field should only allow digits, no symbols.

The button bar in techprofile, used to collapse the profile by topic or lineItems, should also have a filter button to only show those line items which have selected items. For instance, if I am looking at a question and its tech profile selections, I should be able to only see the rows that this question is associated with; the other rows would be collapsed.

Edit a line item in tech profile edit, change a descriptions, for example..

Then go back, and you see the change.

Edit another line item, change its description, and go back.

The changes do not show up. If you edit the line item again, you should see they are reflected there (the page load called the API), so they are being saved, but not showing up in the tech profile. At least until you reload it, and then they do show up.

The UI was initially written as it is just to get something working. Now it is time to get something that works better. We need someone to look at the functionality of the mobile and and create a better, more professional and modern UI. For instance, tapping on a cell usually has a set of options/functionality that can be done for that cell (adding a question to it, moving the row up or down, etc). How do we represent that in our Ionic/Angular UI?

And how do we modernize the techprofile itself?

This is a spike; we need some research done before defining more related user stories.

I want to be able to send an email to every one who logged in to a session in our mobile app. At first, that will just be a "Hey! Thanks for coming!" type email, but with time, we will do stuff like include links and images of their profile, how it was updated, what changed, what we recommend, that kind of stuff.

May wanna think about this on a higher level too, what other cases will we want to send emails, to a group of people, and perhaps not just the day after, but a month, year after.. what does that look like?

Create a new session, and sign someone in. Create another session, and they are still logged in.

Expected Behavior: A new session should not include anyone from the previous session, unless they logged in to the new session.

If you sign in as a user, and then go to their profile from the Admin page, the tech profile that is displayed does not use the same color scheme as, for instance, when you go to Tech Profile Edit.

We should ensure that all tech profile displays, where ever possible, should use the same color scheme. Highlighted lineItem-levels, I can see those being uniquely colored, as they have meaning depending on the view, but the skills themselves (the grouping for the lineitem levels) should be consistently colored, I do believe.

In the mobile app, create a new profile by clicking I'm new here!, and then add your name, an incorrect email (like 'fdsfs@'), and a correct phone number (like 3035551212). The Sign Me Up button will be disabled, which I think is correct, but it doesn't let the user know that only an email OR a phone number is required. So if they removed their errant email address, this would be valid, and they could click the button.

So, if the phone number is filled in, it should say in the error message for the email, "Please clear this field, or enter a valid email.". In cases where the phone number is not entered, or is not valid, the error message on the email field should read "Please enter a valid email."

Lets standardize in our cypress tests, to use data-cy as the data attribute that Cypress tests key on in order to find elements in the DOM. In some places, we are using data-test, but I think these fields only have data-* attributes so as to be used in Cypress, so data-cy makes more sense, conveys more info, than data-test.