Nope. It's for testing conditions that affect how the program is assembled. You can test variable addresses, the value of the PC, symbols used for settings, things like that.
You can for example define a PAL/NTSC symbol that you check whenever the program needs to assemble something different for each of these versions, so you can generate either a PAL or NTSC ROM just by changing the value of this symbol.
What you want to do (make conditional branches more readable) can kinda be accomplished with macros. ASM6's macro system isn't the most advanced, but you should be able to do something like this:
Code:
lda OBJ_Dir_Bits,X
and #$01
IFEQ
;"if equal" code here
ELSE
;"if not equal" code here
ENDIF
Using these macros:
Code:
.macro IFEQ
bne +Else
.endm
.macro ELSE
jmp +End
+Else:
.endm
.macro ENDIF
+End:
.endm
There are probably better "IF" implementations out there, but I'm not sure how far you can get with ASM6.