//if we wanted to write integration tests, I would probably make the run.sh file run headless, then write a pure golang function that hit http routes and returned results depending on expected conditions WITHOUT using the "testing" package. This would just overall make it easier I think
if we wanted to write integration tests, I would probably make the run.sh file run headless, then write a pure golang function that hit http routes and returned results depending on expected conditions WITHOUT using the "testing" package. This would just overall make it easier I think
// if we wanted to write integration tests I would probably make the run . sh file run headless then write a pure golang function that hit http routes and returned results depending on expected conditions WITHOUT using the " testing " package . This would just overall make it easier I think
func TestConvert64(t *testing.T) {
	inputs := "823982"
	returnVal, returnError := convert64(inputs)
	fmt.Println(returnVal)
	fmt.Println(returnError)
	if returnVal < 0 || len(returnError) != 0 {
	  t.Errorf("found an error in unit test!")
	}else{
	  fmt.Println("good return passes")
	}
}
func TestConvert64 ( t * testing . T ) { inputs := " " returnVal , returnError := convert64 ( inputs ) fmt . Println ( returnVal ) fmt . Println ( returnError ) if returnVal < 0 || len ( returnError ) != 0 { t . Errorf ( " " ) } else { fmt . Println ( " " ) } }
if we wanted to write integration tests, I would probably make the run.sh file run headless, then write a pure golang function that hit http routes and returned results depending on expected conditions WITHOUT using the "testing" package.
if we wanted to write integration tests I would probably make the run . sh file run headless then write a pure golang function that hit http routes and returned results depending on expected conditions WITHOUT using the " testing " package .