ppau / project-m Goto Github PK

Acceptance Criteria:

Given an user on the Confirm page
When checks the confirmation box
And clicks the continue button
Then the user can go to the payment page

Given an user on the Confirm page
When the user does not check the confirmation box
And clicks the 'Continue' button
Then the user remain on the Confirm page

Given an user checked the details on the Confirm page
When the user clicks ‘go back’ button
Then the user returns to the Details page

Given an user clicks 'go back' button on the Confirm page
When goes back to the Details page
Then the user's information is remain

appropriate validations on the front & back ends...

Should cover basic membership details for the core membership system (pirate party specific stuff will come later)

Acceptance Criteria:

• When I submit the form, my details should be persisted in the database
• Since the form is generic, the membership details should include: email, name, address, date of birth, phone number
• When I submit the form, a member-sign-up event should be logged
• I should be able to register on my phone
• When I submit the form, the data should be sanitised

Deployment info:

• Prod will be a server TBD
• Pre-prod will be on heroku
• ci will probably be snap-ci

YYYY-MM-DD HH:MM:SS [error_type] [severity] [action] message goes here JSON_field

Severity integers or enums matching to: VERBOSE, DEBUG, INFO, WARN, ERROR, CRITICAL

JSON field is useful for when there's a stack trace or something necessary that should be logged

To edit the info, people include their last name & date of birth - after which they can see the pre-filled form.

nginx & postgres. requires some metrics

Payment processing with stripe

Requirement from Brendan:

• once the payment amount and type is decided, generate a pending invoice.
• If the payment failed, update the invoice with pending status, and let the user try again. He prefer to not have any 'rejected' state.
• If the payment success, update the invoice with paid status.
• presumably, the state before the payment is attempted is considered pending

Payment Process changes:

• InvoiceController need to remove some useless render, and this raise an issue of error code define. As Create Invoice is happened after charge card, we need to figure out what kind of error message and http code corresponding to different cases. CHECKED
• Payment Validation: we need to add both front end and bank end validation for the amount, to let it anytime not blank and anytime no less than 1. CHECKED
• New design imported, If the user click "I don't want to contribute", then we need to hide the whole membership contribute section, and process the user to the next stage. We still need to create a stub invoice for it. CHECKED
• Remove Go back button on the payment page. CHECKED

I should be able to buy using the paypal option, my sale should go through. The money go into the account,

Talk to claire for account information.

The database should be updated within 2 minutes for paymentStatus to be PAID.

• Make asterisks red - DONE
• Add hover styles - DONE
• Fix spacing - DONE
• Make “whatever you want" bold - DONE
• Style declaration checkbox - DONE
• Restyle payment contribution box - DONE
• Fix mobile styles - DONE
• Add "(optional)" in italics next to optional fields. - DONE
• Note that the progress bar has changed slightly since the original design: text and circles are smaller to reduce vertical space at the top. Also, the text in the progress bar is a bit de-centred at the moment. - DONE
• Add ticks. - DONE
• Style modal. - DONE
• Replace Stripe image. -DONE
• Change position of payment messages. - DONE
• Red label and border for payment contribution validation. - DONE
• Make text for error and info boxes smaller. - DONE

Acceptance Criteria:

Given an user in the Membership Type page
When check the Permanent Resident box
Then the user can view 'You are eligible for a Permanent Resident Membership' information in the iFrame

Given an user select Permanent Resident Type
When in the Details page
Then the user can see the correct subheadings and the references to voting
And the labels and inputs will remain the same

Given an user select Permanent Resident Type
When in the Confirm page
Then the user can see the correct declaration text
And the "Check your details" part remains the same

Given an user select Permanent Resident Type
When the user in the Pay What You Wang page
Then the user can see 'Permanent Resident Membership' in the info box

Requires a new domain object: invoice.

A member can have multiple invoices.
Invoices should contain total amount, payment date, payment type, and payment reference, and status.

For transfer/cheque payment options, the app should generate a payment reference and that should be provided to the user to include in their transfer or on the cheque for simpler reconciliation.

Possible statuses include: pending, paid, waived and cancelled. For the scope of this card, we only need pending and paid.

https://hackpad-attachments.imgix.net/hackpad.com_HiGXPZ7XiG0_p.108516_1425982366276_Screen%20Shot%202015-03-10%20at%2010.11.22.png?fit=max&w=882

at some point in the sign up flow

should probably include at the minimum:

• timestamp

see https://github.com/winstonjs/winston#custom_log_format for winston lib

Styles this form and (others)
Include date picker

90 days notice before expiry.

Acceptance Criteria:

Given an user in the Membership Type page
When select 'International citizen or have a Temporary visa' type
Then the user can see the correct membership information in the iFrame

Given an user select 'International citizen or Temporary visa' Type
When in the Details page
Then the subheadings and references to voting will change accordingly
And the labels and inputs will remain the same

Given an user select 'International citizen or Temporary visa' Type
When in the Confirm page
Then the user can see the correct declaration text
And the "Check your details" part remains the same

Given an user select 'International citizen or Temporary visa' Type
When the user in the Pay What You Wang page
Then the user can see 'International Membership' in the info box

phase 1: list of members (includes audited flag), admin authentication, export of list

aec roles check - auditor only sees non-audited members

Must log all access to members in database

Scope of this card - fully polished user flow for full member registration.

Example criteria of 1 of the 4 options (Full, supporter, Permanent Resident, international)

Acceptance Criteria:

Given an user in the Membership Type page
When check the Permanent Resident box
Then the user can view 'You are eligible for a Permanent Resident Membership' information in the iFrame

Given an user select Permanent Resident Type
When in the Details page
Then the user can see the correct subheadings and the references to voting
And the labels and inputs will remain the same

Given an user select Permanent Resident Type
When in the Confirm page
Then the user can see the correct declaration text
And the "Check your details" part remains the same

Users did not respond well to it in user testing and also the current statements do not cater for all scenarios.

Using InVision

Add Reference number:

• Reference number need to represent the membership type for user pay by cheque or direct deposit. e.g. F1(Full membership with user id 1)
• Reference number remain the transaction id for user pay be credit card or paypal.

need https, nodejs v4.2.4, postgresql 9.3

Create user journey from beginning to end, make sure it flows.

we will use waffle.io