It most likely won't save to the server because of errors in another class as the syntax looks like it should save, however, you will most likely have failures when you attempt to run this unit test anyway. The main reason for that is the fact that you are attempting to access a record already in the system. That is a very poor practice in general because:
You never want to depend on records being in the system for a unit test. These tests would fail in any system that doesn't have this record in the system.
You won't even be able to access this data the way your class is set up currently with any API version after 24.0. For this to even work, ou would need to set the class up to access the data:
Without knowing what your trigger does, I would also be wary of your assert statement. You are asserting that the value you set on the record and updated is the same. Unless you are validating that a trigger did NOT update that value, that test isn't very valid and may not provide you with much. Remember, just because a piece of code can provide you code coverage, you still want to strive for valid tests to fully verify your code is functioning properly.
Finally, you should be able to see what the problem with your class is by viewing the Problems perspective of your IDE. In the Menu bar it is under Window > Show View > Problems.