this disclosure describes how applications and their deployment can be tested , managed ; and how any change to any part of this process can be done in a visual and more intuitive way . this disclosure also describes how an application architectural model can be mapped across environments during each deployment stage in an intuitive and graphical way . fig1 is a schematic diagram of a deployment resource architecture system 100 in accordance with embodiments of the present disclosure . the system 100 includes an interface 102 that provides a user with a graphical representation of a resource architecture 104 , the deployment stages 106 , and an interface 108 to view and edit the resource architecture based on the development stage . the interface 102 can be available to any pertinent user of a development system , such as an application architect 110 , a release manager 112 , an environment manager 114 , a quality assurance engineer ( not shown ), etc . each user may be interested in a different stage of development . the interface 102 provides a way to view and / or edit the resource architecture for the stage pertinent to the user , and also a way to track versions and resource architecture changes that may have occurred between stages . the system 100 may also include a repository 120 for storing resource architecture versions . the interface 102 can communicate with the repository 120 to store resource architecture information and to retrieve stored resource architectures . fig2 is a schematic diagram of a deployment resource architecture testing system 200 in accordance with embodiments of the present disclosure . the testing system 200 includes example hardware and software modules used in the testing of resource architectures for an application deployment for a deployment stage . for example , a release manager 252 may wish to promote a resource architecture from a first stage to a second stage . the release manager 252 can use the interface 102 to implement a promote code 232 . execution of promote code 232 engages the promotion evaluator module 204 , implemented at least partially in hardware . the promotion evaluator 204 can retrieve a test advancing the resource architecture from a first stage to a second stage ( 206 ). tests can be stored in a test repository 208 . tests for a stage can be configured during promotion between stages or can be preconfigured to run when selecting a promotion button . preconfiguring a test can associate the test with the development stage and with the resource architecture ( stored in an environment repository 202 ). the deployed environment for the stage 212 can be tested based on a predefined test taken from the test repository 208 . the test executor module 214 can execute the test using the resource architecture and the application 216 . in some embodiments , the application 216 can be run using data collected from running a virtualization of the application using resources configured in the resource architecture ( 218 ). virtualization services can be provided through a virtual service repository 210 . if a resource architecture fails a test , the resource architecture cannot be promoted to the next stage ( 224 ). an indication of the failure can be displayed on the user interface . additionally , if possible , location or source of the test failure can be displayed to the user using the interface . if the test passes , the resource architecture can be promoted to the next stage ( 222 ). an indication of a passed test will be displayed . fig3 is an example screenshot of a graphical user interface for building a resource architecture in accordance with embodiments of the present disclosure . the application architectural view 300 provides a canvas 312 for building the resource architecture . the view 300 also includes a palette of available resources 302 . the palette of available resources 302 can be shown as a drop down menu of resource choices . in the example shown in view 300 , the resources 302 include clients 304 , services 306 , data protocol handlers , 308 , database resources 310 , and others . the user can select available applications and show its architectural model 322 in a graphical way . the architectural model 322 can include containers that represent the individual resources that make up the system to be tested . in the example shown in view 300 , the architectural model 322 includes a web client 314 , a web service 316 , data protocol handler 318 , and a database 320 . in some embodiments , the user can build an architectural model . each resource can be “ dragged and dropped ” on the canvas 312 . after dragging and dropping a resource , the resource can be functionally linked to another resource . for example , the web client resource 314 can be functionally linked to the web service resource 316 by an arrow 330 . in some embodiments , for predefined resource configurations , the web client resource can ping the web services resource to verify compatibility and functionality . in the view 300 shown , the arrow with a check mark 330 indicates a functional linkage between resources . in some embodiments , the resources are undefined . after a user has constructed the architecture model 322 , the user can define the resources . linking the resources at that point can cause each resource to ping a subsequent resource to verify functionality and compatibility . the user is also able to make adjustments to predefined architecture models 322 by selecting resource components from a palette 302 and dragging the resource onto the canvas 312 . in some embodiments , the system automatically connects the new resource components . resources can also be removed from the architectural model 312 . the resources can be pre - configured , edited , or a new one can be created . if any of the resource components experiences any problems during functional verification , the user interface can provide a visual feedback of the problem and where along the architectural diagram it occurred . for example , in view 300 a warning is indicated by an arrow with an exclamation point 332 between the web services resource 316 and the data protocol handler 318 . in view 300 , the user interface indicates an error by an arrow with an error indicator 334 . arrow 334 shows an error between data protocol handler resource 318 and database resource 320 . in some embodiments , arrow colors can be selected to provide further visual cues as to the functionality of resources . a user can store an architecture model 322 in an environment repository , as shown in fig1 . fig4 is an example screenshot of a deployment view 400 of the graphical user interface for visualizing deployment stages for an application in accordance with embodiments of the present disclosure . the deployment view 400 shows stages that the application must be promoted to before the application is ready to be used in a real world scenario . stages are shown as graphical containers that can either be removed , or added as needed by the project . example stages include development stage 402 , qa stage 404 , pre - production 406 , and production 408 . each stage tile can include specific high - level information about that particular stage including its status , and the number of servers allocated to it . the view 400 can show whether an application has passed promotion from one stage to another . for example , there is an arrow with a check box 410 between development stage 402 and qa stage 404 . the arrow with a check mark 410 indicates a verified promotion between stages . in some cases , when a promotion between stages is being analyzed , an arrow with a clock 412 can be used to signal a pending promotion . other indicators can also be used to provide a visualization of the promotion of the application across stages . a promote button 422 is greyed out in the development stage because the application has already passed promotion analysis . a promotion button in the qa stage 424 is not greyed out , because promotion analysis is still pending . fig5 a is an example screenshot of a deployment view 500 of a graphical user interface visualizing a development stage resource architecture in accordance with embodiments of the present disclosure . the user can reveal the application architectural model 501 , the servers 502 , 512 , and 522 , and linkages 530 and 532 indicating how the application resources map across the servers in a graphical way by clicking on a button , or such , on any of the stage tile . as shown in fig5 a , each server shows a resource hosted by the server . for example , for the development stage , server 502 includes a web client resource 504 and a web service resource 506 . the server 512 includes a data protocol handler resource 514 . server 522 includes a database resource 524 . since each stage is independent of the others , each stage can be edited by a user to suit the need of that particular stage . some of the things a user might want to do is to change the number of servers a particular stage utilizes , and / or add resource tools such as a recorder to virtualize a service , or add a virtualized service ( in place of a resource ) in the application architecture displayed . fig5 b is an example screenshot of a deployment stage 550 of a graphical user interface for augmenting a resource architecture with additional servers in accordance with embodiments of the present disclosure . servers 552 can be added by opening a list or palette of servers 554 that are already pre - configured or create a new one , and drag it onto the canvas 556 in the desired order . the application resources will automatically be placed within the closest servers , or the user can manually select and drag each resource and place within the desired server . throughout this process the connections between application resources remain intact . fig5 c is an example screenshot of a graphical user interface for augmenting a resource architecture with additional resources in accordance with embodiments of the present disclosure . adding resource tools is also a matter of opening a list or a palette 562 of available resource tools ( e . g ., recorder 564 and virtual service 566 ), and dragging the resource onto the canvas 568 where the resource tools are automatically connected to the application architectural model . fig5 d is an example screenshot of a graphical user interface for augmenting a resource architecture with a recording resource 572 in accordance with embodiments of the present disclosure . for example , if the user wants to virtualize a database in stage 1 , the user can expose the servers and applications detail view and drag a recorder 572 resource onto the canvas , and drop it between the database 524 and the items before it . the links between the recorder icon 574 , the database resource 524 and the other item ( such as a web service ) can be connected automatically and is ready to record . all of the basic functionalities of the resource tools are available within the graphical user interface view , so as to not require navigating to another view . the recorder and other resource tools ( virtualized service ) are presented in a graphical interface so as to visually show how all these elements work together and provide the user a clear and instant verification of their application architecture , environment , and stages within one view . fig6 is an example screenshot of a deployment view 600 graphical user interface for testing a deployment resource architecture in accordance with embodiments of the present disclosure . deployment view 600 shows an error in promotion between the data protocol hander resource 514 in server 512 and the database resource 524 in server 522 . the linkage 602 can include an icon representing the error ( and in some cases , the linkage 602 can change colors to provide further visual cues as to the error ). in addition , the error can be shown as an icon 604 between the development stage 402 and the qa stage 404 . fig7 is a process flow diagram 700 for defining a stage - specific resource architecture in accordance with embodiments of the present disclosure . a graphical user interface can be provided to a user , such as an architect ( 702 ). a set of resources can be displayed to the user ( 704 ). the set of resources ( or palette of resources ) can be a drop down menu of resources for defining the resource architecture model . a selection of a resource can be received ( 706 ). the selection can be in the form of a drag and drop of a resource form the palette onto the modelling canvas . in some instances , the resources are predefined and preconfigured . in some instances , the resources require configuration . the interface can receive a functional linkage between resources ( 708 ). for example , a user can draw an arrow between resources . for predefined resources , linkages can be formed automatically . the interface can verify the functionality in the linkages between resources in the resource architecture model ( 710 ). for preconfigured resources , the linkage can be verified through an automatic ping between the resource providers to verify functionality . for unconfigured resources , the linkage verification can be performed by defining and configuring each resource , and affirmatively verifying each linkage in the resource architecture model . fig8 is a process flow diagram 800 for augmenting a resource architecture with an additional resource or service in accordance with embodiments of the present disclosure . a graphical user interface can be provided that provides a visualization of a deployment stage for the application ( 802 ). a server context can be provided by a palette or set of available servers ( 804 ). a server context can be a container that represents a server that can host one or more resources . the user interface can receive a selection of a new server ( 806 ). for example , a new server can be dragged and dropped on the a canvas . the interface can receive an indication to associate a resource with the new server ( 808 ). for example , the resource located in a first server can be dragged and dropped into the new server . the new resource architecture model can be stored as a new model ( 810 ). in some embodiments , the new model can be associated with a different deployment stage than its parent model . in some embodiments , a new resource can be dragged into an existing server or an be dragged into a new server . fig9 is a process flow diagram 900 for augmenting a resource architecture with resource tool in accordance with embodiments of the present disclosure . a graphical user interface can be provided that provides a visualization of a deployment stage for the application ( 902 ). a resource tool can be provided by a palette or set of available servers ( 904 ). the user interface can receive a selection of a resource tool ( 906 ). for example , a resource tool can be dragged and dropped on the a canvas . the interface can receive an indication to associate a resource with the resource architecture model ( 908 ). the execution or testing of the resource architecture model can using the resource tool can yield data , such as virtualization data or recorded data . the data can be used to further augment , edit , or otherwise improve the resource architecture model ( 910 ). fig1 is a process flow diagram for testing a resource architecture in accordance with embodiments of the present disclosure . a user interface can be provided for visualizing a resource architecture model and deployment stages ( 1002 ). an interface is provided for promoting or advancing the resource architecture model to a next stage ( 1004 ). providing a list of tests to run on the resource architecture model and the application to determine whether the resource architecture model can be promoted to the next deployment stage ( 1006 ). the test ( s ) can then be executed ( 1008 ). if the test passes , then the next stage can be made available for viewing and for interacting with a resource architecture model ( 1012 ). a pass indicator is displayed in the interface ( 1014 ). if the test does not pass , then a failure indicator is shown in the graphical user interface ( 1016 ). a location of the failure is displayed in the resource architecture model and between the stages ( 1018 ).