Skip to content

kylefeng28/bedside-pharmacy

master
Switch branches/tags
Code

Latest commit

 

Git stats

Files

Permalink
Failed to load latest commit information.
Type
Name
Latest commit message
Commit time
 
 
 
 
 
 
 
 
 
 

UNC Bedside SICU Pocket Pharmacy App

COMP 523 Software Engineering Lab Spring 2019

Website

Getting started

Installing the tools

First, install all necessary tools:

  • Node.js
  • Expo: for easy testing on your phone
    • Register for an Expo account (optional, but recommended)
    • Install the Expo cli tool: $ npm install -g expo-cli
    • Download the Expo app for your phone as well

These aren't required, but will make your life easier. Try to find plugins for your favorite editor for these things:

  • TypeScript support: compilation errors
  • TSLint: TypeScript linting
  • EditorConfig: for consistent spacing between editors

Setting up the project

Clone this repo, and install dependencies needed:

$ cd react-native
$ npm install

Running the project

Expo: (make sure you have expo-cli installed!)

npm start

The first time you run this, it should ask you to login to your Expo account. The command should start a dev server, and you can then scan the QR code with your phone to see changes appear on your phone.

See the scripts section of package.json to see what these commands do.

Directory structure

  • react-native: React Native code
    • package.json: contains a list of dependencies and scripts used by the project
    • App.ts (not src/App.tsx) is the entry point for used by Expo
    • src: contains all the React Native source files
    • __tests__: contains automated Jest tests
  • parser: Google Apps Script parser code
    • Parser.gs
    • appsscript.json: manifest file

Running tests

To run the automated Jest tests:

npm test

Currently, the tests include:

  • Search algorithm

Writing tests

The automated tests are written in Jest, and are located in the __tests__ directory, and must end in the extension .test.ts. Note that these are TypeScript files, since our project primarily uses TypeScript. If you use a .test.js extension, Jest will try to use Babel and fail, since we haven't set it up.