Hey, @mo8it sorry school has been super busy lately, didn't get much free time.

fn main() {}

#[cfg(test)]
mod test {

    use std::io::prelude::*;
    use std::fs::File;

    #[test]
    fn can_you_read_in_rust() {
        // the user enters the name of the file to open
        // the unwrap will be missing for the File::open
        let mut file = File::open("ferris.txt").unwrap();
        let mut content = String::new();

        // the user will fill in the read_to_string method
        file.read_to_string(&mut content).unwrap();

        assert_eq!(content.len(), 10);
    }

    #[test]
    fn can_you_write_in_rust() {
        let msg = "hello world!";

        // here the user will enter the path of the file
        let path = "ferris.txt";

        // the user will fill the create method
        let mut file = File::create(path).unwrap();

        // the unwrap will be missing here
        file.write_all(msg.as_bytes()).unwrap();
    }

    #[test]
    fn can_you_append_in_rust() {
        todo!()
    }


}

I did have a question, how would we verify that a file called ferris.txt would exist when testing read or how do we verify that the user created a file. The obvious thing is when the test start create the necessary file and in the assert check if the file exists for the writing test.

I was wondering if there were better, more elegant or more idiomatic ways to deal with this.

Stdio, Read, Write and Files #482

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions