add end to end test with leak check

[proppy]

We should have a sketch like this that we run manually (and then automatically #168) for every commit that checks that:

• get/set functions are working
• we don't leak

void setup() {
  Serial.begin(9600);

  // connect to wifi.
  WiFi.begin(WIFI_SSID, WIFI_PASSWORD);
  Serial.print("connecting");
  while (WiFi.status() != WL_CONNECTED) {
    Serial.print(".");
    delay(500);
  }
  Serial.println();
  Serial.print("connected: ");
  Serial.println(WiFi.localIP());

  Firebase.begin(FIREBASE_HOST, FIREBASE_AUTH);  
}

int n = 0;
void loop() {
  Serial.println("loop");
  Firebase.setInt("data", n++);
  if (Firebase.failed()) {
    Serial.println(Firebase.error());
  }
  int data = Firebase.getInt("data");
  if (Firebase.failed()) {
    Serial.println(Firebase.error());
  }
  Serial.print("data: ");
  Serial.println(data);
  Serial.print("heap: ");
  Serial.println(ESP.getFreeHeap());
  delay(1000);
}

[ed7coyne]

This is going to be tricky as we don't have a way to run sketches, only to compile them.

A couple options I see:

1. It may not be too hard to create a script that scrapes github for new commits, then downloads them, compiles, pushes and runs them on a local ESP board testing for some serial responses. I think you mentioned wanting something like this at some point.

2. We could try to create a test like this up a couple levels at Firebase.h though using mocked http client, Maybe at the FirebaseArduino level if we added some constructors to feed it mocks. That would test most of our code and assuming we can depend on the ESP code to not leak we may be close to ok.

[proppy]

@ed7coyne yes, we could run flash the sketch from a raspberry pi and grep the serial output.
.

[ed7coyne]

That seems a larger scoped project than this issue. Should we create a "Create hardware continuous testing environment for sketches" issue?
I think we want that for all examples to provide some assurance they continue to work as expected.

[proppy]

Yes, I think it makes sense to split the issue it two, but it's still good to have a the sketch that we can run manually (as described here).

[ed7coyne]

Ah, that is the confusion then. I got caught up on this issue saying "... that we run automatically for every commit"

I will create a separate issue to track the hardware continuous testing.

[ed7coyne]

created #168 , As you said though this is valuable before that work as well. Maybe create a regression test suite that we run manually before a new release (when we get our Arduino library setup).

[proppy]

Updated the description