When a SQL database is full (i.e. there's no free space in which to store new data), and you try and add more data, then:
- If autogrow is off, you'll get an error
- If autogrow is on and there's enough available hard drive space, the database will "grow" by grabbing more hard drive space
- If autogrow is on and there is not enough hard drive space, you'll get a different error (and, sooner or later, panicked IT staff).
If you're trying to "fill" a database up to but not over the point of requiring more disk space, well, that's going to be very hard to calibrate.
If you're trying to test situations when the database needs to grow but there's insufficient hard drive space, I'd suggest altering the database growth factor. Running something like
ALTER DATABASE MyDB
modify file MyDb_FileXX (NAME = MyDBFileXXLogicalName, FILEGROWTH = 100TB)
would set a database (even a small one) to try and grow by 100 terrabytes when it ran out of space, and odds are that would trigger the condition you may be looking for.