Skip to content

Milestone1

Pre-release
Pre-release
Compare
Choose a tag to compare
@Dossar Dossar released this 14 Apr 00:43
· 290 commits to master since this release
v0.1.0
054d59f

README files are provided in the zipped archives as well, but here are quick links for this version of Racket-QA.

Running and Testing this Version

We were able to meet all of our First Milestones:

  1. Bottle-Racket is able to convert Problem Sets 1, 2, 3, and 5 with the following changes in mind:
    1. ps3a's print test will be changed to not do a print.
    2. ps5b's test file was to be modified since the procedures in 2.57 and 2.58 have the same name, resulting in duplicate definitions.
  2. Test-Capture is able to do three things now:
    1. Generate test-running scripts for a properly formatted test area
    2. Configure a mailing list to send test results to, using the QA-Email API
    3. Run the generated test-running scripts and send the test results to the specified mailing list
  3. Racket-Doc currently is able to do the following:
    1. Extract user-specified attributes from .rkt files, and save them to file.
    2. Creates fully navigable web pages on a local host, with hard-coded data.
  4. QA-Email currently has the following complete:
    1. A UI and file database for managing and storing mailing lists is functional.
    2. Is able to send a test email to see if the mailing list is sending out emails to the right people.
    3. Is able to send a test results text file to a mailing list. Test-Capture uses this API.

Concerning the Second Milestones and what is still being worked on:

  1. Bottle-Racket and Test-Capture's code will be formatted with Racket-Doc's specifications. Racket-Doc will be tested to see if it displays properly formatted source code from this project component.
  2. An example test suite and area file will be provided that is not a bottlenose case. It will still be properly formatted, but will show we aren't limited to just Bottlenose tests.
  3. Racket-Doc will be able successfully port the extracted data to the web pages. Right now the web pages contain hard-coded data. Also, It will use user-specified files (currently it reads from "Test.rkt" and writes to "OutputDoc.rkt), and will support Linux, OSX, and Windows (currently tested on Linux only).
  4. Scheduler will be created and tested with capability to send emails automatically after the scheduled test run-up.
Assets 2
Loading